Tailscale fast user switching vs simultaneous tailnets: what actually changes

Fast user switching lets the Tailscale client remember several accounts and flip between them; only one tailnet is ever active, and flipping tears down every connection on the one you leave. Simultaneous tailnets — what TailMux does — keeps every tailnet live at once and routes each request by hostname, so nothing is ever torn down. If your question is “can both networks work at the same time?”, fast user switching is a no and TailMux is a yes. Here's the difference in practice.

What fast user switching actually does#

Credit where due: fast user switching solves re-authentication, and solves it well. You sign into work, sign into personal, and thereafter flip between them from the menu bar or with tailscale switch — no logging out, no browser auth dance each time. If you use one tailnet in the morning and another at night, it's exactly the right tool.

But the name is the spec. It is switching: the client tears down the active tailnet and brings up the other. Both accounts are stored in parallel; precisely one is ever connected. (On macOS it's stricter still — one network extension, one live account, as users discover when they try to open Tailscale twice.)

What a switch tears down#

The cost of switching isn't the three seconds it takes. It's everything that was alive on the tailnet you left:

• Interactive SSH sessions — the route under them vanishes; the sessions freeze and drop.
• RDP and screen-sharing sessions — gone the same way.
• Mounted network shares — an SMB mount on the old tailnet is now a beachball waiting to happen.
• Long transfers and syncs — a backup to the NAS or an rsync to a work host dies mid-stream.
• Anything always-on — a database tunnel, a monitoring check, a watch process: nothing can be permanently connected to a tailnet you keep switching away from.

So every cross-tailnet task becomes a ritual: save state, switch, do the thing, switch back, restore state. Two tailnets in the same minute is exactly what it can't do — which is why “connect to multiple tailnets simultaneously” remains a long-open request (#183).

What “simultaneous” means#

TailMux runs one isolated profile per tailnet — each an embedded Tailscale node with its own identity and node key — and all of them are up at once. A loopback router matches each request's hostname suffix and dials only the profile that owns it. Nothing is ever activated or deactivated; “which tailnet?” is answered per connection, not per machine. (How that works and what it deliberately doesn't do: the architecture explainer.)

Two consequences with no switching equivalent:

• Sessions survive indefinitely. tailmux ssh admin@host.work.ts.net stays up while you browse nas.home-lab.ts.net, because reaching one tailnet no longer means leaving the other.
• Always-on becomes possible. A Service Tunnel keeps db.internal.example:5432 on a fixed 127.0.0.1 port through the work profile permanently — an object that cannot exist under switching, where the work tailnet is regularly off.

1fast user switching          TailMux2---------------------        -----------------------3[work]  -- live              [work]     -- live4[personal] (stored)          [personal] -- live5                             [home-lab] -- live6flip -> only one active      router picks by hostname

Side by side#

When fast user switching is genuinely enough#

Be honest about the boundary. If you use exactly one tailnet at a time — work by day, homelab by night — switching is built in, free, and correct; simultaneous buys you nothing. The moment your workflows overlap — a session that must survive, a tunnel that must stay up, two networks in the same minute — switching becomes the thing you're working around, and simultaneous is the actual feature you were searching for.

Where to go next#

The cross-platform decision guide explains when a shared endpoint, VM, manual proxy, or switching is the better fit: connect to multiple Tailscale tailnets simultaneously.

The work-and-personal version of this question has its own page: two Tailscale accounts on one machine. Ready to set it up: macOS guide · Linux guide · routing limitations · download.