Back to showcase
Live
TailMux
Run every tailnet at once. Route by hostname.
TailMux keeps work, personal, and lab networks reachable at once, sending each hostname only to the profile that owns it.
Why it was born
TailMux started with a common developer problem: work and personal infrastructure lived on separate tailnets, while the official client could keep only one active at a time.
Rather than adding another VPN route or a VM, it preserves the hostname until routing can select the one profile that owns it.
Takeaways
- Routing by hostname avoids ambiguous IP and kernel-route decisions.
- Isolation is a hard system rule: requests never fall back to another profile.
- A local-first CLI and menu-bar app keep the workflow scriptable and visible.
Highlights
- Concurrent, profile-owned Tailscale sessions powered by embedded tsnet.
- PAC, HTTP proxy, SOCKS5, SSH, and loopback service tunnels.
- Built-in diagnostics for DNS, peers, DERP paths, and fetch timing.
Want the full roadmap?
We can share deeper documentation, specs, and timelines for this project on request.