llms.txt
# TailMux
> TailMux is a macOS and Linux tool for accessing resources in multiple independent Tailscale tailnets simultaneously. It routes supported connections by hostname suffix without repeatedly switching accounts or disconnecting the official Tailscale client.
TailMux runs isolated profile-scoped userspace networking nodes and selects the right profile for supported hostname-based connections. It does not create additional native system-wide Tailscale VPN interfaces.
TailMux at tailmux.app is a multiple-tailnet connectivity tool. It is unrelated to browser-based tmux terminal projects with similar names.
TailMux is an independent product and is not affiliated with, endorsed by, or sponsored by Tailscale Inc. Tailscale is a third-party trademark.
## Start here
- [Homepage](https://tailmux.app): product overview and architecture
- [Getting started](https://tailmux.app/docs/getting-started): install and configure profiles
- [Installation](https://tailmux.app/docs/installation): macOS, Fedora, and generic Linux installation paths
- [Download](https://tailmux.app/download): macOS app, Fedora RPMs, and Linux CLI
- [Pricing](https://tailmux.app/pricing): one-time license; localized EUR and USD pricing
- [Changelog](https://tailmux.app/changelog): public features, fixes, and release notes by version
- [Terms and Conditions](https://tailmux.app/terms): perpetual license, update entitlement, purchase, and use terms
- [Privacy Policy](https://tailmux.app/privacy): account, licensing, analytics, support, and legal-acceptance data
- [Limitations and routing model](https://tailmux.app/docs/limitations): native routing, DNS, protocol, and isolation boundaries
## Main answer
- [How to connect to multiple Tailscale tailnets simultaneously](https://tailmux.app/guides/connect-to-multiple-tailscale-tailnets): a neutral architecture guide, setup path, and limitations
## Guides
- [How to connect to multiple Tailscale tailnets at the same time on macOS (2026)](https://tailmux.app/guides/multiple-tailscale-tailnets-macos): A macOS walkthrough for TailMux: install, configure isolated profiles, use the documented browser PAC, SSH, and local TCP-tunnel paths, and understand the routing boundary.
- [Two Tailscale accounts on one machine, both live: work + personal in 2026](https://tailmux.app/guides/two-tailscale-accounts-one-machine): Understand account switching versus simultaneous application-layer access, then configure isolated TailMux profiles for work and personal tailnets without changing the official client session.
- [Tailscale fast user switching vs simultaneous tailnets: what actually changes](https://tailmux.app/guides/tailmux-vs-fast-user-switching): Compare account switching with TailMux profile routing: what each approach changes, when switching is enough, and when a workflow needs concurrent access to independent tailnets.
- [A second Tailscale tailnet on macOS: OrbStack/Lima VM vs no VM at all](https://tailmux.app/guides/tailmux-vs-orbstack-vm): The OrbStack/Lima VM recipe spends a whole Linux guest to answer a routing question. Here's the day-2 cost of the VM, a side-by-side with TailMux, and a checklist to retire the VM piece by piece.
- [Connect to two Tailscale networks on one Linux machine (every way, with commands)](https://tailmux.app/guides/multiple-tailnets-linux): Four working ways to run two Tailscale tailnets on one Linux box — a second tailscaled, network namespaces, userspace SOCKS5, a container per tailnet — with real commands and honest verdicts, then the routing-layer TailMux path.
- [Why two tailscaled daemons fight — and how routing by hostname avoids the war](https://tailmux.app/guides/tailscale-multiple-tailnets-without-vm-or-daemons): Why multiple route-owning daemons require explicit routing, DNS, firewall, and lifecycle management, and how TailMux uses profile-scoped embedded tsnet for supported hostname-based access.
- [Use Headscale and Tailscale at the same time on one machine](https://tailmux.app/guides/headscale-and-tailscale-at-the-same-time): Use a TailMux profile per documented control-plane configuration, including a Headscale homelab alongside a Tailscale-managed tailnet, with hostname-based profile selection.
## Documentation
### Getting started
- [Introduction](https://tailmux.app/docs/getting-started)
- [Installation](https://tailmux.app/docs/installation)
- [macOS app](https://tailmux.app/docs/app)
- [Fedora app](https://tailmux.app/docs/linux)
### Guides
- [Configuration](https://tailmux.app/docs/configuration)
- [Commands](https://tailmux.app/docs/commands)
- [Routing tools](https://tailmux.app/docs/routing-tools)
- [Tunnels](https://tailmux.app/docs/tunnels)
- [Publications](https://tailmux.app/docs/publications)
- [SSH](https://tailmux.app/docs/ssh)
- [Database & GUI clients](https://tailmux.app/docs/database-clients)
- [Behind a reverse proxy](https://tailmux.app/docs/reverse-proxy)
- [Diagnostics](https://tailmux.app/docs/diagnostics)
- [Limitations & routing model](https://tailmux.app/docs/limitations)
### Use cases
- [Work & personal tailnet](https://tailmux.app/docs/use-cases/work-and-personal)
- [SSH, RDP & SMB](https://tailmux.app/docs/use-cases/ssh-rdp-smb-second-tailnet)
- [curl, git & npm](https://tailmux.app/docs/use-cases/curl-git-npm-per-tailnet)
- [Browser routing](https://tailmux.app/docs/use-cases/browser-routing)
## Machine-readable representations
- HTML is the canonical search-engine representation.
- Every documentation and guide page has a noindex Markdown alternate. Append .md to its canonical path.
- Markdown alternates include a canonical Link header and are listed here for agent discovery, not in the XML sitemap.
- https://tailmux.app/llms-full.txt is a generated factual reference assembled from the same product, guide, documentation, and FAQ registries.
## Product facts
- Platforms: macOS (menu-bar app plus CLI), Fedora Linux 44+ (GTK4 desktop app plus CLI), and any other Linux distribution (CLI). There is no Windows build today.
- TailMux does not replace or modify the official Tailscale client.
- Profile choice is based on configured hostname suffixes. Unknown names and cross-profile fallback are denied.
- TailMux does not create additional native system-wide Tailscale VPN interfaces.
- Use the limitations page before assuming a protocol, route, or integration is supported.
