Tailscale vs ZeroTier for Reaching a Homelab Remotely: WireGuard Mesh or a Virtual Layer 2 Network
Priya Sen
November 18, 2026
You have a home server with a few services worth reaching from outside: a media library, a NAS share, Home Assistant, an SSH session you need while traveling. You don’t want to forward ports. You’ve narrowed it down to two overlay networks that promise to make that machine reachable from your laptop and phone as if they shared a desk. Tailscale and ZeroTier both do that, and both have a free tier that covers a typical household. They are built on different ideas, though. Tailscale gives you a routed IP mesh on top of WireGuard. ZeroTier gives you something closer to a virtual Ethernet switch. That one difference explains most of what follows.
A WireGuard mesh versus a virtual Ethernet switch
Tailscale uses WireGuard for the data path. Every device gets a WireGuard key and a stable address in the 100.64.0.0/10 range. A coordination server hands out public keys and policy, and the devices then build encrypted tunnels directly to each other. What you get is a layer 3 network. Devices exchange IP packets, and Tailscale decides which IPs each node can reach and how to route to subnets behind it. If you already know WireGuard, the trade-off between running it by hand and letting Tailscale coordinate it is covered in our piece on Tailscale versus plain WireGuard.
ZeroTier does not use WireGuard. It runs its own peer-to-peer protocol and presents each joined network to the operating system as a virtual Ethernet interface. Members of a ZeroTier network sit on the same emulated layer 2 segment. They have MAC addresses, and the network can carry Ethernet frames, ARP, and broadcast and multicast traffic, all within limits the controller sets. You can still assign IP ranges and routes, and most people use ZeroTier purely for IP traffic. The layer 2 foundation shows up in a few specific places, though: bridging, LAN discovery protocols, and old games that find each other by broadcast.
Who runs the control plane, and can you take it home
Both companies host the control plane (the part that knows which devices belong to which network and what policy applies) for you by default. With Tailscale, the clients are open source, but the hosted coordination server is not. The self-hosting route is Headscale, an independent, BSD-licensed project that reimplements the coordination server. Its README describes a deliberately narrow scope: a single tailnet, aimed at personal use and small organizations. The official Tailscale clients can point at a Headscale server, so you keep the polished apps while owning the device database, the upgrades and the backups. We cover that trade-off in detail in Headscale versus Tailscale for a household.
ZeroTier’s story is more complicated and has changed over time. ZeroTier One was GPL-licensed until version 1.4.2, when it moved to the Business Source License 1.1. The BSL is source-available, not open source in the OSI sense. With release 1.16.0 in August 2025, ZeroTier split its licensing again. According to the release notes, the core and service code moved to the Mozilla Public License, while the network controller moved to a separate commercial source-available license. Building the controller from source now requires an explicit non-free build flag. ZeroTier has said the controller remains free for personal and non-commercial use. Its pricing page lists “self-hosted and air-gapped” deployment as an Enterprise feature.
The practical takeaway: a self-hosted Tailscale-compatible control plane is a well-trodden path with a permissive license. A self-hosted ZeroTier controller is still possible for home use, but read the current license text before you build anything around it, especially if the homelab overlaps with paid work. ZeroTier has also deprecated private root servers, called “moons.” Its docs now say they are no longer recommended for new deployments, so don’t plan around them for a fully independent setup either.
What the free plans actually allow in late 2026
Both free tiers are for non-commercial use and have changed before, so check the pricing pages. As listed at the time of writing:
- Tailscale Personal (free): up to 6 users, unlimited user devices, up to 50 tagged resources such as servers, and up to 3 ACL groups. Tailscale SSH on the free plan is limited to a small number of hosts.
- ZeroTier Personal (free): 10 devices on one network with one network admin, and community support only. The paid Essential plan raises this to 10 networks with 10 devices included and per-device pricing after that.
For a household, this is the most important practical difference between the two. Ten devices fills up quickly once you count phones, laptops, a tablet, a NAS, a mini PC and a travel router, while Tailscale caps users rather than devices. ZeroTier can soften this: one bridge or router on your LAN can expose the whole home network without every device joining.

How each one gets through NAT, and what happens when it can’t
Both tools try to build direct peer-to-peer connections, punching through home routers and carrier-grade NAT with UDP hole punching. Both need a fallback when that fails behind strict firewalls or double NAT.
Tailscale’s fallback is DERP (Designated Encrypted Relay for Packets), a network of relay servers that Tailscale operates. As a last resort, DERP forwards traffic that is already WireGuard-encrypted, so it never sees plaintext. Tailscale has also added peer relays. You designate one of your own devices with a reachable UDP port as a relay, and when a direct connection fails, clients try your peer relays before falling back to DERP. Tailscale’s documentation now recommends peer relays over running a custom DERP server in most cases. Peer relays require Tailscale 1.86 or later and a grant in your policy file allowing their use.
ZeroTier uses a set of root servers that it operates. Roots help peers find each other and can relay traffic when a direct path fails. Historically, the self-hosted answer was a moon, a private root you ran yourself. As noted above, ZeroTier now discourages new moon deployments, so in current setups you mostly rely on ZeroTier’s roots.
For both tools, the troubleshooting habit is the same. When something feels slow, check whether the connection is direct or relayed. On Tailscale, tailscale status and tailscale ping <host> show whether traffic goes direct or through a relay. On ZeroTier, zerotier-cli peers lists each peer and its path.
Reaching the rest of your LAN: subnet routers, exit nodes and managed routes
You rarely want to install a client on every device at home. Printers, cameras, smart TVs, and IPMI interfaces can’t run one. Both tools let one machine act as a gateway to the rest of the LAN.
On Tailscale, that machine is a subnet router. You advertise the home subnet from a Linux box and approve the route in the admin console:
sudo tailscale up --advertise-routes=192.168.1.0/24
On Linux you also need IP forwarding enabled. Remote clients then reach 192.168.1.x through that node. The same machine can be an exit node with --advertise-exit-node, so a phone on hotel Wi-Fi can send all of its internet traffic through your home connection.
ZeroTier covers the routed case with managed routes, set in the network configuration. You add a route for 192.168.1.0/24 via the ZeroTier address of a member that forwards traffic to the LAN, and that member needs forwarding and usually NAT or a return route on your router. To use it as a full-tunnel gateway, clients have to opt in to accepting a default route. ZeroTier also has an option Tailscale lacks entirely: a true layer 2 bridge. In ZeroTier’s documented setup, a small Linux machine puts its physical Ethernet interface and its ZeroTier interface into the same Linux bridge. On the controller, you enable “Allow Bridging” for that member and keep the ZeroTier IP pool outside the LAN’s DHCP range. Remote members then sit on the home LAN at layer 2 and can see broadcast traffic from it.
Bridging is easy to get wrong: broadcast-heavy LANs push that chatter across the internet, and overlapping address pools cause conflicts that look like random outages. If you only need a handful of IPs, routing is simpler on either product.
Names instead of numbers: MagicDNS and ZeroTier’s DNS options
Tailscale’s MagicDNS is on by default for new tailnets. Every device gets a name under your tailnet’s domain, and short hostnames such as nas resolve from any device without extra setup. You can also add global or split DNS servers in the admin console, for example sending your home domain to a Pi-hole while everything else goes to a public resolver.
ZeroTier’s built-in DNS is more limited. A network controller can push DNS server addresses and a search domain to members, but each client has to allow managed DNS, and the docs list Linux support as partial or planned. ZeroTier’s own documentation notes that pushing a DNS server doesn’t, by itself, let you reach hosts by the names set in the controller. For that, it points to ZeroNSD, a separate DNS server that answers for your network’s members.
If you want hostnames to just work on every device without extra components, Tailscale has the clear advantage.

ACLs and grants versus flow rules
Once more than one person shares the network, you will want to restrict who can reach what. Tailscale handles this with a central policy file, now built around grants with older ACL syntax still supported. It’s written in a JSON-like format and lets you express rules like “the kids’ tablets can reach Jellyfin on port 8096 and nothing else” using users, groups, and tags. The free plan’s limit of three ACL groups is enough for most households. Our guide to Tailscale ACLs for a household walks through a realistic policy.
ZeroTier uses a flow rules engine. Rules are written in a small domain-specific language and compiled by the controller. Because the network is layer 2, flow rules can match on Ethernet frame types, MAC addresses, and IP fields, and they can drop, accept, or even redirect or copy traffic to another member for inspection. That is more expressive at the packet level, and harder to read later. The pricing page now lists custom flow rules as a feature of the paid Scale tier, so check what your plan exposes before you design around them.
LAN games, discovery protocols and other broadcast traffic
This is where ZeroTier’s design pays off. Older PC games with “LAN” multiplayer usually find each other with broadcast or multicast packets. On a routed overlay like Tailscale, those packets never reach the other side. Typing an IP address may still work; automatic discovery won’t.
On a ZeroTier network, all members share a broadcast domain. Note one documented exception: ZeroTier says the iOS and Android VPN APIs don’t let it carry multicast or broadcast, so discovery from phones and tablets won’t behave like it does on a desktop.
Phones, tablets and the client experience
Both projects ship clients for Windows, macOS, Linux, iOS, and Android. On mobile, each runs as a VPN profile, which brings the usual platform constraints. Only one VPN can be active at a time on most phones, so Tailscale and a commercial VPN app (or ZeroTier and anything else) will fight over the slot.
Tailscale’s mobile apps are more polished. They offer exit node selection in the app, MagicDNS names, and support for sign-in through common identity providers. ZeroTier’s apps join a network by its 16-character network ID, after which an admin authorizes the device in the controller.
Speed without benchmarks: what actually limits throughput
Published throughput comparisons vary too much with hardware and path to be worth quoting. These factors matter more:
- Direct versus relayed. Either tool on a relayed path will be slower and have higher latency than on a direct path. Fixing NAT traversal, or adding a Tailscale peer relay you control, usually matters more than which product you picked.
- CPU on small devices. Encryption costs CPU. On a Raspberry Pi or an old NAS acting as subnet router or bridge, the processor can become the ceiling for either tool.
- Your upload bandwidth. Streaming from home is capped by your ISP’s upload speed long before either overlay becomes the bottleneck on most connections.
If performance is critical, test both on your own hardware with iperf3 over a direct path and compare. Don’t rely on someone else’s numbers from a different setup.
Matching the tool to how you reach your homelab
Lean toward Tailscale if your goal is to reach services by name from phones and laptops with as little setup as possible, if your household has more than ten devices, if you want a mature path to self-hosting through Headscale, or if you value tidy access policies tied to user identities. If you are still deciding between WireGuard-based meshes, our comparison of Netbird and Tailscale covers another option in the same family.
Lean toward ZeroTier if you need layer 2 behavior: bridging a remote site onto your LAN, LAN-only games, or discovery protocols between desktops. It also fits if you want packet-level flow rules and are comfortable with one network and ten devices on the free tier, or with a bridge that keeps the member count low. Before you build a self-hosted controller around it, read the 1.16 licensing notes so you know which terms apply.
Nothing prevents you from running both. A common pattern is Tailscale for everyday remote access to services, with a small ZeroTier network created only for the occasional LAN game night or a bridged lab segment.