Tailscale and alternatives — private network between your devices

Tailscale connects your own devices in a private network, without running a VPN server and usually without opening ports. This guide covers how it works, how to set it up and the alternatives.

Tailscale and alternatives — private network between your devices

Tailscale and alternatives — private network between your devices

Tailscale connects your own devices in a private network, without running a VPN server and usually without opening ports. This guide covers how it works, how to set it up and the alternatives.

Who this guide is for: Home users and IT professionals who want to reach their own devices securely from outside the home without opening ports or maintaining a traditional VPN server.

Tailscale is different from a normal VPN. It connects your own devices with each other in a private network without you having to manage a VPN server, and usually without opening ports in your router. In most cases traffic runs directly between devices; if that fails, Tailscale falls back to a relay.

What you gain, and what it costs

You gain easy, secure access to your own devices from anywhere without port forwarding, dynamic DNS, or a self-managed VPN server. For many people, this is the fastest route to “I can reach my NAS or home server again” without becoming a network administrator.

The cost is reliance on a coordination service and one more trust layer in your network design. Tailscale says it can’t read your content, but it does receive metadata about devices and connections, and more advanced setups still require you to understand routes, exit nodes, and ACLs.

When this is overkill

If you never need to reach your devices from outside home, you do not need this. And if you want maximum autonomy and are willing to maintain your own WireGuard or Headscale setup, Tailscale may be too convenience-oriented for your requirements. Its strongest fit is for people who do want remote access but do not want open ports and server maintenance.


The problem Tailscale solves

Say you have a NAS, a server or a Raspberry Pi at home. You want access to it when you’re away. Traditional options:

  • Port forwarding on your router: Works, but exposes your service to the internet, where crawlers such as Shodan read and index what open services reveal about themselves.
  • Running a VPN server (WireGuard/OpenVPN): Secure, but the server needs an address the internet can reach and an open port (not possible at home behind CG-NAT), you have to maintain the server yourself, and configuration is non-trivial.
  • Tailscale: Usually no open ports, no own server, also behind CG-NAT (shared IP addresses at some internet providers).

How Tailscale works

Tailscale builds a WireGuard mesh between your devices. Each device gets a stable IP address in the 100.x.y.z range that stays the same wherever the device goes. Devices try to connect directly to each other peer-to-peer. If that is not possible, Tailscale falls back to a relay connection.

For coordination (which devices exist, who may connect to what) Tailscale uses its own control server, which is closed source. Tailscale says it can’t read the content of your traffic, which is end-to-end encrypted. The server does get metadata: according to the privacy policy device names, IP addresses, public keys, access times and connection logs with traffic statistics.

Works behind CG-NAT too: Direct connections also work behind CG-NAT in many cases. When they can’t be made (hard NAT, a firewall), traffic runs through Tailscale’s DERP relay servers, or a peer relay in your own network if you set one up. A relay can’t decrypt your traffic, but the connection is usually slower.


Specifications

Property Value
Technology WireGuard mesh
IP range 100.64.0.0/10 (the shared CGNAT range from RFC 6598, not exclusive to Tailscale)
Free tier Yes — Personal plan with limits, non-commercial use
Paid Standard, Premium and Enterprise plans
Platforms Windows, macOS, Linux, Android, iOS, tvOS, Chromebook, FreeBSD
Subnet router Yes — a device running Tailscale gives access to its network
Exit node Yes — route traffic via a specific device
Open-source client Yes (GUI closed on Windows, macOS, iOS)
Control server Tailscale cloud (or self-hosted via Headscale)

Subnet routing — your entire home network accessible

If you set up Tailscale on a device at home (Raspberry Pi, NAS, server) and activate subnet routing, devices on that subnet become accessible via Tailscale — even devices without Tailscale installed. You advertise the routes on that device and approve them in the admin console.

Example: your NAS at 192.168.1.100 is reachable at that same address from your laptop at the office, via the Tailscale connection. A Linux laptop first needs sudo tailscale set --accept-routes; Windows, macOS, iOS and Android accept routes by default.


Exit node — VPN for all your traffic

You can set up a Tailscale device as an “exit node”. All your internet traffic then runs through that device. Useful when you have a secure home network and you’re on public Wi-Fi — you browse via your home connection.

This is comparable to a traditional VPN, but via your own hardware. It is opt-in: the device has to offer itself as an exit node, an admin has to allow it, and each device that wants to use it has to select it. The steps are in the Tailscale review.


Alternatives

Headscale — self-hosted Tailscale control server

Tailscale’s control server coordinates the network. Headscale is an open-source, self-hosted implementation of that control server. You run it on your own VPS or server, and Tailscale clients connect to your server instead of Tailscale’s cloud.

Advantage: The control server no longer runs at Tailscale. Full control over who has access. Disadvantage: You must manage, update and secure a server. More work. It is a community project for a single network, not part of Tailscale’s supported product. The clients remain Tailscale’s, and Headscale’s example configuration still uses Tailscale’s DERP relays unless you change that.

When to choose Headscale: If you don’t want Tailscale (the company) running your control server. If relays shouldn’t run there either, configure your own DERP server.

ZeroTier — alternative mesh protocol

ZeroTier is a comparable mesh VPN technology with its own protocol, built around a virtual Ethernet layer. It has apps for Windows, macOS, iOS, Android and Linux, Docker images, community-maintained FreeBSD and OpenWrt packages, and a library (libzt) to build it into your own app. ZeroTier lists embedded processor support under its Enterprise plan.

Tailscale ZeroTier Headscale
Protocol WireGuard ZeroTier own WireGuard
Control server Tailscale cloud ZeroTier cloud (own controller possible, non-commercial licence) Self-hosted
Free tier Unlimited user devices, up to 6 users on Personal (non-commercial) 10 devices, 1 network (non-commercial) Self-hosted
Setup (our assessment) Very easy Easy Complex
Open-source Client (GUI closed on Windows, macOS, iOS) Client Server; uses Tailscale’s clients

WireGuard manual — maximum control

WireGuard configured directly without Tailscale or ZeroTier. You manage the keys, configuration files and server yourself. No dependency on external services.

When: If you already have a VPS or home server, and are willing to manage configuration manually. More work than Tailscale, but fully open-source and fully self-managed.


When to use what?

Situation Recommendation
Make home network accessible, simple Tailscale free tier
No dependency on external control server Headscale on own VPS
Home network as VPN exit node Tailscale exit node
Maximum control, no external services WireGuard manual
You specifically want a virtual Ethernet network ZeroTier

Installation in 3 steps (Tailscale)

This assumes a fresh setup. Already have a tailnet (your private Tailscale network)? Skip step 1 and log in with the same account on the new device.

  1. Go to tailscale.com and choose Get Started. Tailscale has no email sign-up and no passwords of its own: you log in through an identity provider such as Apple, Google, GitHub or Microsoft. At home, choose Personal use.
  2. Install Tailscale on each device: from the download page or the app store on Windows, macOS, iOS and Android, and log in with the same account. On Linux: curl -fsSL https://tailscale.com/install.sh | sh, or the manual route on Tailscale’s packages site if you’d rather not pipe a script into your shell.
  3. On Linux, also run sudo tailscale up, open the URL it prints and log in. The device then appears on the Machines page of the admin console.

All devices in your tailnet can reach each other at their 100.x.y.z address: a new tailnet’s default policy allows all communication between them. You can restrict that with access rules.

Device keys expire after a set period, and the device then has to log in again. For a server you only reach remotely, you can choose Disable key expiry in the device’s menu on the Machines page. Tailscale warns that this reduces security, so use it only on trusted devices.


Caveats

Tailscale as a company: Tailscale’s control server coordinates your network. It gets metadata (see above), not the content of traffic, according to Tailscale. If that is a concern: Headscale.

Free tier limitations: Tailscale’s Personal plan is generous for home use: unlimited user devices, up to 6 users, up to 3 ACL groups and up to 50 tagged resources, for non-commercial use only (check current limits at tailscale.com/pricing). For teams and businesses there are paid plans.

Next step

Decide first

Alternatives