Is Tailscale free? Free tier limits explained
Tailscale's Personal plan is free for noncommercial use, with six users and unlimited user devices. See tagged resource limits and when Headscale wins.
Is Tailscale free? Yes, on the Personal plan
Tailscale is free on the Personal plan for non-commercial use. The free tier has no expiry date and it includes most of the product. It limits how many people can join your network, not how many machines you connect. Checked on 10 November 2026, Tailscale's pricing page gives Personal six users, unlimited user devices, 50 tagged resources, and access to nearly every feature.
Two words first. A tailnet is your private network: one account, one user list, one policy file. A seat is one person inside that tailnet. Tailscale bills per seat, so the meter runs on people. User counts and eligibility decide whether your setup is free.
Every figure below is a published number with the date it was checked. Prices and allowances move, so confirm them on the pricing page before you plan a budget around them. The structure moves much more slowly, and the structure is the useful part: people and tagged infrastructure are counted, while the paid tiers sell capabilities rather than a bigger device allowance. WireGuard, the tunnel protocol underneath, is the same on every plan, and what Tailscale adds on top of plain WireGuard explains that split.
What counts as a user, and what counts as a device
Every machine in a tailnet is owned by something. Log in with your own identity and the machine is owned by you. Tailscale calls that a user device, and the pricing FAQ is blunt about it: "User devices are free and unlimited." Your laptop, your phone, your desktop and your tablet are one seat between them, not four.
Register a machine with a tag instead and it is owned by the tag. Tailscale calls that a tagged resource, and tagged resources are what the plan counts. Servers and routers are meant to be tagged, because a shared machine should not belong to whoever happened to run the login command on it. As of 10 November 2026 the Personal plan includes 50 tagged resources, and the pricing page lists extra ones at 1 US dollar per month each. The same page says Tailscale is "currently not enforcing the hard limits or overages" of tagged resources, ephemeral resources, ACL groups and multiple tailnets, and that it will begin introducing those limits over the next few months, with email notifications. Plan around the published numbers anyway, because they are the ones that will apply. A VPS doing a job for everybody belongs in this category, whether it is a subnet router advertising a private range or an exit node carrying outbound traffic.
Tag a server at the moment it joins, so it never sits in the tailnet as a machine owned by you:
curl -fsSL https://tailscale.com/install.sh | sh
sudo tailscale up --advertise-tags=tag:servertailscale statustailscale status lists the node with the owner it registered under. The tag must already exist in your tailnet policy file under tagOwners, because a tag is an ownership grant and a node cannot claim one that nobody granted. If the tag is not in the policy, the node cannot take it.
This is why the free plan surprises people in both directions. A homelab with thirty machines all signed in as you is one seat, and it is free. A four person team where everyone signs in uses four seats of six, but commercial teams do not qualify for Personal merely by staying below six users. Twelve people is not free at any device count, because the cap counts people.
Ephemeral resources are the third category. A node that registers with an ephemeral auth key, such as a continuous integration runner or a Kubernetes pod, is automatically removed after a short period of inactivity and draws from a monthly pool of minutes instead of holding a resource slot. As of 10 November 2026, Personal and Standard have 1,000 of those minutes per month and Premium has 10,000. A node that stays up past four hours stops counting as ephemeral and becomes an ordinary tagged resource.
One more billing detail: an invited user does not take a seat until they use the tailnet. The pricing FAQ states that a user "does not occupy a seat until they first log in to the admin console or when they first authenticate a device". You can send invitations early without paying for people who never arrive.
What the paid plans cost
The data behind this chart
[
{
"plan": "Personal",
"usd_per_user_month": 0
},
{
"plan": "Standard",
"usd_per_user_month": 8
},
{
"plan": "Premium",
"usd_per_user_month": 18
}
]Personal is free. Standard is 8 US dollars per user per month and Premium is 18, both as published on 10 November 2026. Enterprise is quoted by sales with custom user counts and limits. Standard and Premium remove the user cap, so a personal tailnet needs a paid plan for a seventh user, while commercial teams need one regardless of size. Turning those list prices into a real monthly bill means adding seats and tagged resources together, which a worked breakdown of a household and a five person team does for both cases.
Which features sit behind a paid tier
These are capability gates. Adding machines does not push you up a tier. Writing a more complicated access policy can, once Tailscale enforces the limits it publishes.
Access control lists (ACLs, the rules that decide which user may reach which machine) show this, with one caveat. The policy file itself is on every plan. The number of groups each plan publishes for it differs, but as of 10 November 2026 that number is not an enforced gate. Tailscale's pricing page says "we are currently not enforcing the hard limits or overages of ACL groups, multiple tailnets, tagged resources, and ephemeral resources," and that it plans to introduce those limits over the next few months.
The data behind this chart
[
{
"plan": "Personal",
"acl_groups": 3
},
{
"plan": "Standard",
"acl_groups": 10
},
{
"plan": "Premium",
"acl_groups": 300
}
]Personal lists 3 groups, Standard 10, and Premium 300. A group is a named set of users, so the published figure is really a ceiling on how finely you can divide people. Three groups covers "me", "family" and "guests". It does not cover a company with departments. Going past the published number does not lock you out today, but a policy that depends on staying above it should be planned with an upgrade in mind for when enforcement starts.
The other gates, checked on 10 November 2026 against the pricing page and Tailscale's feature documentation:
- Bringing your own identity provider (IdP), which means single sign-on (SSO) with any OIDC provider you already run, is on every plan, Personal included. Tailscale dropped its paid-plan restriction in April 2024 and says "SSO is once again available for free for everyone." The custom OIDC setup asks for proof that you own the domain and a provider that meets its technical requirements, not for a plan. What Standard adds on the identity side is SCIM, which provisions users and groups from that provider automatically.
- Device approval and basic device posture checks (operating system and Tailscale version) are on every plan. Posture integrations with mobile device management (MDM) and endpoint security tools start at Standard.
- Advanced user roles, such as billing admin, IT admin and auditor, start at Standard.
- Network flow logs start at Premium, as does advanced Tailscale SSH. Basic Tailscale SSH is on every plan, and the pricing comparison lists it at up to 5 hosts.
SSH session recording is the case worth reading carefully, because it proves these gates are set per feature and not by tier order, and that they move. Tailscale's session recording documentation lists the recorder-based feature for the Personal and Enterprise plans, but as of 10 November 2026 it marks that feature deprecated: Tailscale no longer offers it through tsrecorder, support for existing users ends in August 2027, and the docs point to Tailscale PAM instead. The pricing page groups SSH, Kubernetes and database recording under that separately purchased Privileged Access Management extension. Check the current page before you build a compliance requirement on top of it.
Why a free tailnet says "Reached use limit"
The admin console shows "Reached use limit" when something stops the tailnet from admitting a user, and the plan's user cap is only one possible cause. Tailscale's message reference, checked on 10 November 2026, lists three causes: adding more users than the plan permits, which mainly happens on Personal with its six free users; an account that was not properly updated after a plan change; and an organization policy that may limit or prevent access to the tailnet. On Personal the usual cause is the seventh person, because the plan counts people, and the documented fixes are to upgrade or to remove users you no longer need. Standard, Premium and Enterprise have no user limits, so on a paid plan the message likely points to an account configuration problem, and Tailscale's documented fix is to contact its support. If you sign in with a custom or private domain, ask your IT administrator whether Tailscale authentication is restricted for that domain. None of these causes is about how many laptops and phones are connected, so counting devices when you see this message wastes time. Open the admin console and count human accounts first.
Do you need a paid plan for a custom DERP relay?
DERP (Designated Encrypted Relay for Packets) is Tailscale's relay network. When two nodes cannot open a direct connection through NAT (network address translation) and no peer relay is available, their encrypted traffic falls back to a DERP server. Running your own DERP relay is configuration in the tailnet policy file, and Tailscale's documentation on custom DERP servers lists no plan restriction as of 10 November 2026. The same page still marks custom DERP servers as alpha.
Be precise about what a custom relay changes, because this is where relaying gets confused with self-hosting. A custom DERP server moves the fallback data path onto a machine you own. The control path does not move. Tailscale's coordination server still holds your node keys, your policy file and your user list. It never holds the private keys that decrypt your traffic, so what an attacker actually gains by taking over that coordination server is a narrower question than it first sounds. If you want that part on your own hardware, a relay is the wrong tool. You need a different control plane.
When does a self-hosted Headscale control plane make sense?
Headscale, the open source Tailscale control server replaces the coordination server with one you run on a VPS (virtual private server). The Tailscale clients do not change. They point at your server instead of Tailscale's, so there are no seats to buy and no user cap.
Start with the money, because the gap is smaller than people expect. One Standard seat is 8 US dollars per month. A small VPS that can run a control plane costs about what one or two seats cost. So the sum does not change sign until you are paying for several people, and it never changes sign for a solo homelab, which was free already. Self-hosting to save money on a five device network does not work out.
The real trade is control against work. Headscale puts your user list and your policy file on a machine you own, in a country you chose, with no vendor account in the path. Per the project documentation for the current release, 0.29.7, checked on 10 November 2026, it supports ACLs and grants, tags, subnet routers, exit nodes, MagicDNS, Taildrop, Tailscale SSH, node registration over OpenID Connect (OIDC), and an embedded DERP server. That release's feature list leaves Serve and Funnel unchecked, but the gap for publishing a service with Serve is narrower than the checkbox suggests. The project's tracking issue explains: "Since the serve feature already works for HTTP, the missing piece mostly involves getting and using a TLS certificate for the right domain." So Serve over plain HTTP already works with Headscale, and what the stable release lacks is HTTPS certificate integration. The changelog for the next release, 0.30.0, says tailscale cert and HTTPS with tailscale serve now work, and the development branch marks Serve as supported; 0.30.0 had not shipped as of 10 November 2026. Funnel, which publishes a service to the public internet, is still unsupported on the development branch, so it stays on Tailscale's own control plane for now. Network flow logs are absent too, OIDC groups cannot be used inside ACL rules, and the project is scoped to a single tailnet by design. Version 0.29.7 is a security release published on 30 October 2026; the project recommends upgrading to it and Tailscale v1.104.4 or newer, especially when using Tailscale SSH.
Here is the work you take on:
- You own the availability of the control plane. Existing tunnels keep passing traffic for a while, because the peers already hold each other's keys. Everything that needs coordination stops: new nodes cannot register, expiring keys cannot be renewed, and policy changes never reach the nodes.
- You own the upgrades. Headscale implements a protocol that Tailscale's clients keep changing, so your upgrade schedule follows their client releases rather than your calendar.
- You own the database and its backups. Lose that state and every node must register again.
- You own TLS (transport layer security) on the server's public endpoint, because clients reach the control server over HTTPS.
That is the honest bill. Take it when the reason is control or a user count that per-seat pricing handles badly. Do not take it to save eight dollars.
A self-hosted NetBird server is the other self-hostable answer. It ships its own control plane, its own identity handling and its own web interface, and it is built as a product rather than as a reimplementation of somebody else's control server. Both options leave you running a service that your network depends on. Decide that you want to run one, then pick.
FAQ
Is the Tailscale free plan a trial?
No. Personal is a free tier with no expiry. Checked on 10 November 2026 it carries six users, unlimited user devices and 50 tagged resources, and it includes nearly all of the feature set, including single sign-on with your own OIDC identity provider. What it does not carry are the capabilities the paid tiers sell, such as a higher published ACL group allowance, SCIM provisioning, advanced user roles and network flow logs. Confirm today's numbers on Tailscale's pricing page, because allowances get revised.
How many devices can I add on the Tailscale free plan?
Your own devices are unlimited. Tailscale's pricing FAQ says user devices, meaning any node that is not tagged, are free and unlimited. What gets counted is tagged resources, the servers and routers you register with a tag, and Personal included 50 of those on 10 November 2026, a limit Tailscale says it is not yet enforcing. Older guides quoting a 20 device or 100 device cap describe previous pricing models that still apply to customers who retain those legacy plans. Moving to a new plan is a one-way change; you cannot return to your previous legacy plan.
Why does my tailnet say "Reached use limit"?
On Personal the usual cause is a seventh person, because the plan counts people rather than machines. Tailscale also lists an account that was not properly updated after a plan change, and an organization policy that limits or prevents access, as causes. On a paid plan, which has no user cap, contact Tailscale Support. If you sign in with a custom or private domain, ask your IT administrator whether Tailscale authentication is restricted. Count human accounts in the admin console first. Untagged laptops and phones are not the cause.
Is Headscale cheaper than paying for Tailscale?
Only above a few paid seats. A VPS able to run Headscale costs roughly what one or two Standard seats cost per month, so a small tailnet saves nothing and a solo tailnet was free to begin with. Headscale pays off when you want the control plane on hardware you own, or when your user count makes per-seat pricing awkward. The price is operational: upgrades that follow Tailscale client releases, database backups, a TLS certificate you renew, and being the only person who can fix an outage.