Six alternatives to a corporate VPN
A corporate VPN puts each remote device on the company network. Six categories of product do the same job in a different way. This guide gives the strengths and the limits of each one, and it helps you find a fit.
The VPN listens on the internet
A VPN appliance accepts connections from any address. Attackers can find it and test it.
One sign-in opens the network
After the sign-in, the laptop can reach each system that the internal firewall does not block.
The alternative asks first
With zero trust network access, a policy engine checks the user and the rules before a tunnel exists.
The tunnel reaches one app
The gateway makes only outbound connections, and it forwards traffic to the one app in the policy.
Why teams look for VPN alternatives
The corporate VPN was made for an office with servers in the same building. Most teams now have apps in several clouds and people in many places. Three problems send teams to look for VPN alternatives.
Slow backhaul
A VPN sends remote traffic through one central site. A person in Sydney who uses an app in Singapore can send each packet through an office in London. Video calls and large files show the delay first.
Broad access
A VPN connects a device to a network, not to an app. A contractor who needs one dashboard can frequently reach every server in the subnet. An attacker with one stolen password gets the same reach.
Open ports and a stream of patches
A VPN appliance must listen on the internet. Researchers and attackers find new vulnerabilities in VPN appliances each year. Each one starts a race between the patch and the exploit, and the team must be available to win it.
Alternatives that work at the network level
These three categories carry any IP traffic, so they work for databases, SSH, remote desktops, and web apps.
Zero trust network access
Zero trust network access (ZTNA) permits one user to reach one app, after a policy check. A small gateway sits near the app. All access without a policy is refused.
Strengths: narrow access, sign-in with your identity provider, and in many designs no open inbound port. Limits: most products need a client on each device, and you must decide who can use each app.
Mesh VPN
A mesh VPN puts an agent on each device. The devices connect directly to each other, and a coordination service gives out the keys.
Strengths: fast direct paths, simple setup, and good device-to-device access. Limits: each system needs an agent, or a router that forwards for it. Access rules can become hard to read as the network grows.
Bastion host
A bastion host is one hardened server with a public address. Engineers connect to it with SSH, then go from it to the internal servers.
Strengths: simple, low cost, and familiar to engineers. Limits: it is one more public listener, it suits SSH better than other protocols, and it does not help people who are not engineers.
Alternatives that work at the app level or as a bundle
Identity-aware proxy
An identity-aware proxy sits in front of a web app. It makes each visitor sign in with the identity provider before it forwards a request. The user needs only a browser.
Strengths: no client to install, access for each app, and a good fit for contractors and devices you do not manage. Limits: it is for web apps only. Databases, SSH, and other protocols need a different tool or an added client.
SASE
SASE means secure access service edge. It is a bundle of network and security services from one vendor, delivered from the cloud. The bundle usually includes ZTNA, a secure web gateway, and a cloud firewall.
Strengths: one vendor and one policy for private access and web traffic. Limits: a large project and a large contract. Traffic goes through the data centers of the vendor, so the vendor can inspect it. A team that needs only private access pays for parts it does not use.
Virtual desktops
A virtual desktop runs inside the company network, and the user sees it as a video stream. The apps and the data stay in the data center.
Strengths: strong control of data, and support for old desktop apps. Limits: high cost for each user, a slower experience, and a desktop image that someone must maintain.
Find a fit
Answer these questions to find the category that fits. The results include categories that Firezone is not in.
How to move off a VPN safely
A VPN replacement is a migration, not a switch. These steps apply to each category in this guide.
- Make a list of what people use. Read the VPN logs or the firewall logs. Most teams use far fewer systems than the VPN permits.
- Run the two tools together. Keep the VPN on while you install the new tool. Nobody loses access on the first day.
- Move one app at a time. Start with an app that has a clear owner and a small group of users.
- Write narrow rules. Give each group access to the apps it uses, and to no other apps.
- Close the listener. When the logs show no VPN traffic, turn off the VPN and close its port on the firewall.
Where Firezone fits among the alternatives
Firezone is an open source zero trust network access platform built on WireGuard. You run the Gateways, and Firezone runs the control plane. Firezone answers the three problems at the top of this guide.
- Backhaul. Traffic goes directly from the Client to a Gateway in the network that has the app. Only traffic for your Resources uses the tunnel.
- Broad access. A Policy gives one Group access to one Resource. A Resource can be one DNS name, one address, or one port range.
- Open ports. Clients and Gateways make only outbound connections. See the port reference for the full list.
Firezone also covers part of the mesh VPN category. A Device Pool lets Clients reach each other directly, for SSH or remote desktop to a workstation.
Firezone runs beside an existing VPN. Start with one CIDR Resource that mirrors the VPN, then add narrow Resources and move one app at a time.
What Firezone does not do
Firezone needs a Client on each user device, so it is not an identity-aware proxy. It does not record sessions, and it is not a secure web gateway or a full SASE bundle.
Legacy VPN, identity-aware proxy, mesh VPN, and Firezone
The table compares the legacy VPN with two alternative categories and with Firezone.
| Legacy VPN | Identity-aware proxy | Mesh VPN | Firezone | |
|---|---|---|---|---|
| Access for each app | NoAccess for each subnet | Yes | PartialAccess for each device | YesOne Policy for each Resource |
| Any protocol, not only web | Yes | NoWeb apps only | Yes | YesTCP, UDP, and ICMP |
| Works with no client on the device | No | YesA browser is sufficient | No | No |
| No inbound firewall ports | No | PartialThe proxy is public | Yes | Yes |
| Direct path to the app | NoThrough one central site | PartialThrough the proxy | Yes | YesRelays only when a direct path fails |
| Reaches systems that run no agent | Yes | Yes | PartialThrough a subnet router | YesThrough a Gateway |
| Device-to-device access | No | No | Yes | YesDevice Pools |
The table describes the usual design of each category. A specific product can be different. Read the documentation of the product before you decide.
Common questions
What can I use as an alternative to a VPN for remote access?
There are six main alternatives to a corporate VPN. They are zero trust network access, a mesh VPN, a bastion host, an identity-aware proxy, SASE, and virtual desktops. The best one depends on what people must reach and on the devices they use.
Is zero trust network access better than a VPN?
ZTNA gives narrower access, and many designs have no open inbound port. Those two points remove the largest risks of a VPN. ZTNA needs more planning, because you must decide who can use each app.
Is a mesh VPN the same as zero trust network access?
No. A mesh VPN connects devices to each other, and its rules usually name devices. ZTNA connects users to apps, and its rules name groups and apps. Some products do the two jobs.
Do I need SASE to replace a VPN?
No. SASE is a bundle that includes private access and web security. If your goal is only a VPN replacement for private apps, a ZTNA product alone is sufficient. You can add web security later.
Can I keep my VPN while I test an alternative?
Yes, and this is the safe method. Run the two tools together, move one app at a time, and turn off the VPN when its logs show no traffic. Firezone runs beside an existing VPN.