The official Tailscale client keeps one tailnet active at a time. TailMux makes work and personal tailnets reachable simultaneously on macOS and Linux, without switching accounts, running multiple system daemons, or using a VM. It runs an isolated embedded node per profile and routes by hostname, with strict no-fallback isolation. Use SSH, RDP/SMB, browsers, curl, git, and npm across tailnets at the same time.
Hey Product Hunt 👋 I'm the maker. TailMux started as a personal annoyance: I run a work tailnet and a personal one, and the official client can only be active on one at a time. Fast user switching means constantly running tailscale switch and dropping the other connection. The workarounds (two daemons, userspace SOCKS5, a whole VM) all felt clunky on macOS, so I built something that runs an isolated embedded Tailscale node per tailnet and routes traffic by hostname suffix. Both tailnets are live at the same time, with strict isolation so nothing leaks between them. It covers SSH, RDP/SMB tunnels, per-tailnet browser routing, and routing curl/git/npm. It's a one-time $5.99 license (a year of updates, keep your version forever). It's not affiliated with Tailscale — just a companion tool. It scratched my own itch and I use it daily; I'd love feedback from anyone juggling multiple tailnets. Ask me anything.
this is exactly the kind of tool that's obviously right once someone builds it - "just run tailscale switch" always felt like a workaround for a problem that shouldn't exist. how do you handle MagicDNS when both tailnets happen to have a machine with the same short hostname? does the routing-by-suffix approach sidestep that collision entirely or is it still something you have to configure around?
the fail-closed approach to ambiguous routes is the right instinct, most tools would guess and silently leak traffic down the wrong tunnel. one thing I'm curious about given it's running isolated embedded nodes per tailnet - what's the permission footprint on macOS, does it need a persistent background helper with elevated network privileges, and is it notarized/signed properly given how much trust you're asking for on the network stack
Congratulations on the launch! Managing multiple Tailscale tailnets has always been one of those small but recurring workflow frustrations, so this looks genuinely useful.
I'm curious about the networking side—how does TailMux handle overlapping IP ranges or conflicting DNS configurations when multiple tailnets are active simultaneously? Looking forward to trying it out.
Great app, I absolutely want to try it; it would be super convenient even for me, since I live on two different tailnets. If so, are there no profile limits, meaning it can support more than two tailnets?
About TailMux on Product Hunt
“Multiple Tailscale tailnets at once, no switching + no VM”
TailMux launched on Product Hunt on July 13th, 2026 and earned 116 upvotes and 11 comments, placing #12 on the daily leaderboard. The official Tailscale client keeps one tailnet active at a time. TailMux makes work and personal tailnets reachable simultaneously on macOS and Linux, without switching accounts, running multiple system daemons, or using a VM. It runs an isolated embedded node per profile and routes by hostname, with strict no-fallback isolation. Use SSH, RDP/SMB, browsers, curl, git, and npm across tailnets at the same time.
TailMux was featured in Mac (103.6k followers), Developer Tools (515.7k followers) and Security (2.8k followers) on Product Hunt. Together, these topics include over 89.7k products, making this a competitive space to launch in.
Who hunted TailMux?
TailMux was hunted by Claudio Quaglia. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how TailMux stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Claudio Quaglia
Hey Product Hunt 👋 I'm the maker. TailMux started as a personal annoyance: I run a work tailnet and a personal one, and the official client can only be active on one at a time. Fast user switching means constantly running tailscale switch and dropping the other connection.
The workarounds (two daemons, userspace SOCKS5, a whole VM) all felt clunky on macOS, so I built something that runs an isolated embedded Tailscale node per tailnet and routes traffic by hostname suffix. Both tailnets are live at the same time, with strict isolation so nothing leaks between them. It covers SSH, RDP/SMB tunnels, per-tailnet browser routing, and routing curl/git/npm.
It's a one-time $5.99 license (a year of updates, keep your version forever). It's not affiliated with Tailscale — just a companion tool. It scratched my own itch and I use it daily; I'd love feedback from anyone juggling multiple tailnets. Ask me anything.