PiVPN vs Tailscale (2026): The Question Is Whether You Can Open a Port

PiVPN gives you a classic VPN server on a Raspberry Pi and needs an inbound port. Tailscale needs none, and works behind CGNAT where PiVPN cannot. That single constraint decides most of these setups before any feature comparison starts.

By Eric GerardFounder · VPNSmith - Self-host VPN & GDPR VPS specialist

Updated 6 min read6 min

Affiliate links: we may earn a commission, at no extra cost to you. Method

Compare the costsRead the guide

fig. 01 / self-host-vpnCONTROLcoordination onlyNODE A100.64.0.1NODE B100.64.0.2NODE C100.64.0.3WireGuard p2pkeys, ACL
fig. 01 / self-host-vpn

Search for this comparison and you will find long feature tables. Most of them bury the one fact that decides the outcome for the majority of people, and it has nothing to do with features: can you open an inbound port on your internet connection?

fig. 01 / self-host-vpnCONTROLcoordination onlyNODE A100.64.0.1NODE B100.64.0.2NODE C100.64.0.3WireGuard p2pkeys, ACL
fig. 01 / self-host-vpn

If yes, both tools work and the choice is about what you want. If no, the comparison is over before it starts.

One exception: behind CGNAT you can still keep PiVPN by running it on a small VPS with its own public IPv4, such as a Contabo Cloud VPS 4 (affiliate link) from €5.50 a month on a 24-month term, with the Pi at home joining it as a client (details below). If you would rather have a US host with a 30-day money-back guarantee, Ultahost VPS Basic is 5.52 $ a month on a 24-month term (1 GB RAM, dedicated IPv4, read on 21 October 2026), enough for a WireGuard server for a few devices. Another option: HostPapa Unmanaged VPS Lite (affiliate link) is 2.95 $ a month on a 3-year term, then the regular rate (1 core, 1 GB RAM, 25 GB NVMe, root SSH access, 30-day money-back guarantee, read on 28 October 2026).

The constraint that settles it

PiVPN builds a server. Clients dial in from outside, which requires a port reachable from the internet, which requires a public address of your own.

Tailscale never accepts an inbound connection. Both ends make outbound connections and a coordination server introduces them. Nothing on your router needs to change.

So the first question is not "which is better" but what does your ISP give you? If your router's WAN address falls between 100.64.0.0 and 100.127.255.255, you are behind carrier-grade NAT: there is no port to forward, and PiVPN cannot be reached from outside no matter how it is configured.

Close-up of a green Raspberry Pi board with three aluminium heatsinks, the GPIO pin header running along the left edge and the HDMI and USB ports in the foreground
A Raspberry Pi board with heatsinks fitted, GPIO header along the left edge. The same hardware runs either tool, what differs is whether anything outside has to reach it.

Two different shapes of network

Beyond reachability, the two build genuinely different things.

PiVPN is hub-and-spoke. Everything goes through the Pi. That is exactly what you want when the point is to be at home from elsewhere: browse from your home IP, reach the printer, use a service that only trusts your home address.

Tailscale is a mesh. Your laptop talks to your phone directly, whether or not the Pi is on. Nothing funnels through one box, so nothing breaks when that box reboots, and nothing routes through your home connection unless you ask it to.

Neither shape is better. They answer different sentences: "I want to be on my home network" versus "I want my machines to reach each other."

What each one costs you

PiVPNTailscale
Inbound port requiredyesno
Works behind CGNATnoyes
Third party involvednonecoordination server (Tailscale Inc.)
Setup beyond the installstatic IP or DDNS, port forwarding, config per clientlog in on each device
Adding a devicecopy a config fileone command
If the Pi is offlineeverything stopspeer-to-peer links keep working
Exit through your home connectionnaturalpossible, needs enabling

The third option when the port cannot be opened

Behind CGNAT the table above reads as if Tailscale were the only choice. There is a third one that keeps the PiVPN shape: move the WireGuard server off the Pi and onto a small VPS with its own public IPv4. The VPS has a port reachable from anywhere, your phone and laptop dial into it exactly as they would into PiVPN, and the Pi at home connects to it as one more client with PersistentKeepalive = 25, so your home LAN stays reachable through it. You keep a classic hub you fully control, no coordination server holds your device list, and CGNAT stops mattering because nothing has to reach your home connection from outside.

Before deciding, check whether you are actually behind CGNAT. Our free WireGuard port checker compares your router's WAN address with your public IP and tells you in a few seconds; if the two differ, or the WAN address sits in 100.64.0.0/10, no PiVPN setting will help. The relay layout is written up step by step in WireGuard behind CGNAT, and the configs for the VPS, the Pi and each phone come out of the WireGuard config generator in a minute, keys generated in your browser. The generator is free with no account, up to 250 devices, and its ZIP export holds every client .conf and its QR code as a PNG, handy to set up a whole office or family in one go.

Generate your WireGuard configs here

Type your server address, choose the number of devices, then scan each QR code from the app.

All keys are generated in your browser (Curve25519 / X25519). Nothing is sent to our servers - your config stays 100% private.

Public IPv4 or domain of the machine that will run WireGuard. No server yet? Leave it empty and add it later.

Free, no account: up to 250 clients, each .conf with its QR code, and one ZIP with every file.

Everything the device sends to the internet goes through your server.

Advanced settingsTunnel subnet, DNS, site-to-site LANs. The defaults work for most setups.

Optional. Enter the LAN subnet behind the server and/or behind a client that acts as a site gateway (a router, a Raspberry Pi, a NAS). The generator adds each LAN to the server's AllowedIPs, gives every peer the routes to the other LANs, and writes the forwarding rules on the gateways. Leave a field empty for a normal client.

What you download

  • wg0.conf

    for the server

  • client1.conf

    one per device

  • QR (sample)

    for the phone app

Illustration only: the lines and the QR code are fictional, no real key. Your real files are generated in your browser when you click.

What it costs: a few euros a month and one more server to keep updated. What changes compared with PiVPN at home: internet traffic exits from the VPS address, not your home IP, unless you route it on through the Pi, which is more setup. If the whole point was to appear to be at home, you still need a home connection that can be reached, and that brings you back to Tailscale.

Keep the commands at hand: our free Tailscale & Headscale Cheat Sheet (4-page PDF, direct download, no sign-up) gathers status and ping, exit node, subnet router, Serve and Funnel, the Headscale config, users, keys and ACLs, and the usual failure causes. Download the cheat sheet.

The honest recommendation

Start with Tailscale if you are unsure. It works everywhere, including the cases where PiVPN simply cannot, and adding a device takes seconds. For most people wanting to reach their own machines from outside, that is the whole job.

Choose PiVPN when the point is your home connection itself, appearing to be at home, or refusing any outside dependency. Both are legitimate reasons, and the second one is not paranoia: it is the difference between a network you operate and a network you subscribe to.

And if you want the mesh without the company, the middle path exists: run the control plane yourself with Headscale, compared with Tailscale here. You keep the official clients and the NAT traversal, and the part that knows about your devices stays on a machine you own.

Affiliate link

Price checked 17 Oct 2026, 24-month term

Frequently asked questions

What is the real difference between PiVPN and Tailscale?
PiVPN is an installer script: it configures WireGuard or OpenVPN on your Raspberry Pi and leaves you with a classic VPN server that clients dial into. Tailscale is a mesh network with a coordination server run by Tailscale Inc.; your devices find each other through it and then talk directly. PiVPN gives you a front door into your home network. Tailscale gives every device a private address that works from anywhere, with no front door to open.
Can I use PiVPN if my ISP puts me behind CGNAT?
No, and this is the constraint that settles most of these decisions before any feature comparison begins. PiVPN needs an inbound port reachable from the internet. Behind carrier-grade NAT you do not have a public address of your own, so there is nothing to forward a port to. Tailscale is built for exactly this case: both peers make outbound connections and are introduced by the coordination server. Check your router's WAN address first - if it starts with 100.64 to 100.127, you are behind CGNAT.
Which is more private?
PiVPN, in the strict sense: nothing leaves your control. Tailscale's data plane is also end-to-end encrypted with WireGuard, so the company cannot read your traffic, but it does hold the coordination metadata - which devices exist, when they connect, from what addresses. If your objection is to any third party knowing your network's shape, PiVPN is the honest answer. If your objection is to anyone reading your data, both are fine.
Which one is easier to set up?
Tailscale, by a wide margin, and it is not close. Install, log in, done - no port forwarding, no dynamic DNS, no certificate to distribute. PiVPN's script is well made and the install itself is quick, but the surrounding work is not: a static IP or DDNS, a port opened on the router, and a config file moved to each client by hand.
Does PiVPN still make sense in 2026?
Yes, in two situations. When you want a genuine exit point at home - browsing the internet as if you were on your home connection, for a service that only trusts your home IP - a hub-and-spoke server does that naturally. And when you refuse any dependency on an outside company, PiVPN's whole value is that there is nothing to depend on.
Can I keep PiVPN behind CGNAT by using a VPS?
Yes. Move the WireGuard server to a small VPS with its own public IPv4 and let the Pi at home connect to it as one more client with PersistentKeepalive set. Phones and laptops dial into the VPS exactly as they would into PiVPN, and the home LAN stays reachable through the Pi. You keep a classic hub you control, with no coordination server, and CGNAT stops mattering because nothing has to reach your home connection from outside. It costs a few euros a month, and internet traffic exits from the VPS address rather than your home IP unless you route it on through the Pi.
Is there a middle path?
Yes: run the coordination server yourself. Headscale is an open-source implementation of Tailscale's control plane, so you keep the mesh behaviour and the official clients while owning the part that knows about your devices. It costs more setup than Tailscale and less freedom from maintenance than PiVPN - the usual price of the middle.