Pricing
Open the documented Lisar page for the next relevant step or background.
VPN profile ownership and routing for small teams
Review documented small-team VPN use cases, profile ownership, routing options, compatibility review, and current operational limits.
VPN routing for business travel and remote teams
Lisar business routing is designed for teams and frequent travelers who need controlled VPN profiles for company access, travel scenarios, or predictable routing behavior across countries.
Business use cases may include team access, executive travel, router-based office setup, or custom entry and exit behavior.
Custom Exit for eligible plans and business requests
Custom Exit is available according to plan eligibility and custom review. It can help businesses define more specific exit routing behavior when a standard personal VPN profile is not enough.
Custom Exit should be reviewed before deployment when the setup involves company access, routers, or specific network requirements.
Custom Exit VPNRouters
Router setupCompatible routers and customer-provided virtual routers
Some business scenarios involve compatible routers, network devices or customer-provided virtualized routers. Lisar can review these scenarios before setup to confirm whether the requested routing path is suitable.
Device compatibility depends on VPN protocol support, firmware behavior and the network environment.
Self-service vs custom review
Self-service plans are suitable for standard profile creation and supported setup paths. Custom business routing is different: it may require manual review, custom planning, and direct communication before activation.
Businesses should contact Lisar before relying on a specific router, office network or custom routing design.
What to include in a business request
To help Lisar review a business routing request, include the number of users, target setup devices, router or virtual router details, expected countries or regions, required setup method, and whether Custom Exit or DNS behavior is needed.
Do not include passwords, private keys or sensitive internal credentials in the first contact message.