A Tailscale alternative that denies by default
Firezone and Tailscale are two products built on WireGuard, and they have two different models of access. Firezone publishes this page, so read it as one side of the comparison. It also says where Tailscale is the better choice.
A mesh starts connected
In a mesh VPN, each device is a peer. A new network usually permits all peers to connect, and rules then remove access.
Firezone starts closed
A Client asks the policy engine before it connects. If no Policy matches, there is no tunnel.
A Policy opens one Resource
The Engineering Group has a Policy for the Git server, so traffic goes through the Gateway to that server.
All other Resources stay closed
The Gateway is in the same network as the billing database, but the Client gets no route to it.
Why teams look for a Tailscale alternative
Tailscale made WireGuard easy to use. Many teams start with it, and many teams stay with it. The teams that look for a Tailscale alternative usually have one of these reasons:
- Access model. They want access that is closed until a rule opens it, and rules that name a team and an app.
- Open source. They want to read the code of the full product, not only the code of the client.
- Shape of the network. Most of their traffic goes from people to company systems, not from device to device.
- Company fit. They want groups from the identity provider, device checks, and logs for an audit in one product.
If none of these reasons is true for you, Tailscale is possibly the correct tool. The section on fit says when.
What Firezone and Tailscale have in common
The two products have the same base, and you get these properties from each of them:
- WireGuard encryption. Traffic is encrypted from end to end, and the vendor cannot read it.
- Direct connections. NAT traversal makes a direct path between two endpoints where the networks permit it.
- Relays as a fallback. If a direct path is not possible, a relay forwards the encrypted packets.
- No open inbound ports. You do not put a VPN server on a public IP address.
- Sign-in with your identity provider. Users do not get a second password.
- A hosted control plane. The vendor runs the coordination service, and you run the endpoints.
Where the two products are different
Deny by default
A new Firezone account permits nothing. A user can reach a Resource only after an admin writes a Policy that joins one Group to one Resource. A new Tailscale network starts with a policy file that permits all devices to connect, and an admin then edits that file to remove access.
The two models can get to the same result. The difference is the state that you have when a person forgets a rule. In Firezone, a forgotten rule means no access.
Resources, not only devices
Tailscale is a mesh VPN. Each device runs the client and becomes a peer. To reach a host that cannot run the client, you set up a subnet router that advertises a route.
Firezone has Resources. A Resource is a DNS name, an IP address, a CIDR range, or a set of devices. A Gateway in your network carries the traffic, and the hosts behind it need no software. For access from device to device, Firezone has Device Pools, which connect two Clients directly.
Rules for a DNS name
Firezone can make a rule for one DNS name, with wildcards. Each DNS Resource gets its own address on the device. For that reason, two apps that share one server can have two different Policies. The article How DNS works in Firezone explains the design.
Open source from end to end
The Firezone Clients, the Gateway, and the control plane are open source in one repository. The core of the Tailscale client is open source, but the Tailscale coordination server is not. Read why companies select open source for security products.
Which one fits your team
These lists are a summary. Try the two products with your own network before you decide.
Tailscale is a good fit when
- You connect your own devices, a homelab, or a small group of people who trust each other.
- Most of your traffic goes from device to device.
- You want its additional features, such as an SSH server in the client, or a way to publish a local service to the internet.
- Your users are frequently on networks that block UDP. Tailscale relays use HTTPS. Firezone relays use UDP.
Firezone is a good fit when
- You give teams access to company systems, and each team must reach only its own apps.
- You want access that is closed until a Policy opens it.
- You want rules for DNS names, and separate rules for apps that share an address.
- You want load balancing and failover between Gateways with no additional setup.
- You want to read the source code of the full product.
How to move from Tailscale to Firezone
Firezone can run on a device at the same time as a different VPN, when the two products route to different addresses. You can move one system at a time.
- Start a free account. The Starter plan needs no credit card. Follow the quickstart.
- Put a Gateway next to each subnet router. A Gateway is one Linux binary. It runs as a Docker container or a systemd unit. See Deploy Gateways.
- Change each advertised route into a Resource. Start with the same CIDR range. Then add a smaller Resource for each app, and remove the wide range.
- Change each rule into a Policy. Use the groups from your identity provider.
- Move one team. Install the Firezone Client for one team. When that team works, move the next team.
Firezone vs Tailscale, side by side
This table compares the design of the two products. It does not list each feature.
| Tailscale | Firezone | |
|---|---|---|
| Encryption protocol | WireGuard | WireGuard |
| Access in a new account | All devices can connect, until you edit the policy file | No access, until you add a Policy |
| Main model | A mesh of devices | People and Groups that connect to Resources |
| Hosts that cannot run the client | YesThrough a subnet router | YesThrough a Gateway |
| Direct access from device to device | YesThe default | YesWith Device Pools |
| A separate rule for each DNS name | PartialRoutes by domain with app connectors | YesEach DNS Resource has its own Policy |
| Open source | PartialThe core of the client | YesClients, Gateways, and control plane |
| Relay when a direct path fails | YesOver HTTPS | YesOver UDP |
| SSH server in the client | Yes | NoCarries your SSH traffic as it is |
Firezone made this table from the public documentation of each product on 2026-11-20. Products change. Read the documentation of each product before you decide.
Common questions
Is Firezone a mesh VPN like Tailscale?
Not by default. Firezone connects a Client to a Gateway, and the Gateway reaches the Resource. For direct access between two devices, you add a Device Pool. A Device Pool connects two Clients with no Gateway.
Is Firezone open source?
Yes. The Clients, the Gateway, and the control plane are open source. Firezone hosts the control plane for you, and you run the Gateways. Firezone does not give documentation or support for a control plane that you host.
Can I run Firezone and Tailscale at the same time?
Yes, when the two products route to different addresses. Many teams run the two products together while they move one system at a time.
Does Firezone have exit nodes?
Firezone has the Internet Resource, which does the same job. It sends all other internet traffic of a Client through the nearest Gateway that you run. It is in the paid plans. See full-tunnel VPN.
Does Firezone have a free plan?
Yes. The Starter plan is free for small teams, and it needs no credit card. See the pricing page for the limits of each plan.
Does Firezone traffic go through Firezone servers?
Not by default. Traffic goes directly between the Client and your Gateway. If the networks prevent a direct path, a Firezone relay forwards the encrypted packets. Firezone cannot decrypt them.