Tailscale is...
… more than meets the eye.
I installed Tailscale expecting a nicer VPN. I came away rethinking how I stand up infrastructure.
The moment it clicked
Phone, laptop, server, router, even the AppleTV, each on the network in a few minutes. Install the client, sign in with my identity provider, done. No firewall rules, no concentrator, no certificate authority to babysit. Every device reaches every other by name, and who can reach what is one JSON file instead of a pile of per-box iptables rules. The network stopped being a ticket I file and became a thing I edit.
Infrastructure stops gating you
Once connecting a machine takes a minute, you connect more of them. A new database, a build box, a GPU I’ll use for a week: each joins the same way and is instantly addressable by name. ssh inference-01 just works, authenticated against my identity provider, no keys to rotate. Standing up a service used to mean a detour of IPs, ports, bastions, and security groups, and every step was a place to stall. When that cost drops to near zero, you stop rationing infrastructure and just build.
The network as the sandbox
Here is where it meets what I keep coming back to: identity and trust boundaries for the agentic era. We box in a process at the machine, with containers and seccomp, but none of that says what the thing can reach. An agent that can hit the open internet, or wander into a database it was never meant to touch, is a problem no local sandbox solves.
Tailscale moves the boundary to the network. Give each agent its own identity and the ACL becomes the sandbox: this agent reaches the repo and the test database and nothing else. Default-deny, one edge granted at a time, and every node knows which agent, and which human it is acting for, is on the other end. Drop a swarm of agents into an ephemeral tailnet and they collaborate freely with each other while the ACL walls the cluster off from everything else.
What the dev platforms actually sell
The quieter payoff: none of this touches the public internet. I used to reach for platforms like PlanetScale, Neon, or Fly because provisioning feels instant. Click, and a service exists at an endpoint you can hit. That immediacy is what the premium buys, and it ships with a public URL whether you want one or not.
Tailscale gives you the same immediacy on raw compute. Rent a box from Hetzner or DigitalOcean, drop it on the tailnet, and the moment it exists it is reachable by name, no dashboard and no public endpoint. Run Forgejo on a tailnet-only address and it is as accessible as GitHub for teammates and invisible to everyone else. Instant provisioning was always the pitch. Tailscale hands you the connectivity half directly, so the compute underneath can be the cheapest thing that runs Linux.
Why it stuck with me
Connecting a machine, scoping who can reach it, keeping it off the internet: the slow, manual, risky parts become fast, declarative, and safe by default. Connecting costs nothing, so you build faster. The network is the sandbox, so agents get real boundaries without a wall of container config. And private-by-default stops being a sacrifice.
More than meets the eye, indeed.