TailMux icon

TailMux

TailMux is a macOS and Linux tool for accessing multiple independent Tailscale tailnets from one workstation, with hostname-suffix routing and no client session switching.

TailMux

TailMux

TailMux is a developer tool for reaching resources in multiple independent Tailscale tailnets from one Mac or Linux machine at the same time. It is built for workflows where a single workstation needs access to both work and personal tailnets, or any other separately configured tailnets, without switching the official Tailscale client account.

The product routes supported browser, command, SSH, and local TCP-tunnel connections by hostname suffix. Each profile runs its own embedded Tailscale node, so account state, sockets, logs, and node identity stay separate, and a hostname owned by one profile never falls back to another profile. TailMux is application-layer routing rather than a second system-wide VPN interface.

Features

Isolated profiles per tailnet

Each configured tailnet gets its own embedded Tailscale node inside TailMux, with separate identity, state, sockets, and node key handling.

Hostname-suffix routing

TailMux matches supported requests by hostname suffix so the name itself is the routing key, rather than an IP address selected after the fact.

Strict no-fallback isolation

A profile-owned hostname is either routed to its owner or denied. If a request does not match, TailMux does not silently retry another tailnet.

Browser PAC routing

On macOS, TailMux can install a PAC file so browser traffic for owned suffixes goes through TailMux while everything else stays direct.

CLI for access and diagnostics

The CLI includes tools for SSH, local TCP tunnels, diagnostics, status checks, and proxy-style workflows such as env and run.

Cross-platform desktop and server support

The app is available on macOS and Linux, with a menu bar app on macOS and a CLI-first workflow on Linux.

Use Cases

  • Work and personal tailnets on one workstation

    Keep a work tailnet and a personal tailnet reachable on the same Mac without repeatedly signing in and out of the official Tailscale client.

  • Browser access to multiple internal web properties

    Open a browser to internal sites whose hostnames belong to different tailnets, with PAC-based routing handling the supported suffixes on macOS.

  • Command-line and tunnel-based access

    Reach SSH hosts and local TCP services such as databases, SMB shares, or RDP endpoints through a fixed loopback port tied to a specific profile.

  • Routing validation and diagnostics

    Check which profile owns a host, whether a peer is visible, and how the path is behaving before connecting.

  • Alternative to switching, VMs, or full VPN duplication

    Use a Linux or macOS workstation as the access point for several tailnets without standing up a VM or second system-wide VPN interface.

Pros and Cons

Pros

  • Lets one Mac or Linux machine reach multiple independent tailnets at the same time.
  • Keeps profile state isolated, including sockets, logs, node keys, and session identity.
  • Routes by hostname suffix with no silent fallback to another profile.
  • Supports several practical access paths, including browser PAC routing, SSH, and local TCP tunnels.
  • Provides CLI access for routing, testing, diagnostics, and scripted workflows.

Cons

  • It only covers the supported hostname-preserving paths described in the docs, not arbitrary raw-IP selection or system-wide routing.
  • The product is built around isolated profiles and local routing, so it is not a fit for workflows that need a native second VPN interface.
  • Configuration requires non-overlapping hostname suffixes to preserve the no-fallback behavior.

FAQ

Can TailMux connect to two Tailscale networks at the same time?

TailMux is designed for simultaneous access to resources in multiple independent Tailscale tailnets on macOS and Linux. It keeps a separate profile per tailnet and routes supported hostname-based connections to the profile that owns the suffix.

Does TailMux change my existing Tailscale account or session?

No. TailMux is a separate tool that uses isolated profiles for supported connections without changing the official Tailscale client session.

What kinds of connections does TailMux support?

TailMux supports browser access through PAC routing on macOS, SSH via tailmux ssh, and fixed local TCP tunnels for clients such as database, RDP, or SMB tools. It is described as an application-layer routing tool rather than a system-wide VPN interface.

How does TailMux decide which tailnet to use?

TailMux uses a hostname suffix to choose a profile. A hostname owned by one profile never falls back to another profile, and overlapping suffixes are rejected when the configuration is saved.

How does TailMux pricing work?

The pricing page says TailMux is a one-time purchase with one year of updates included. After that year, you keep the versions released during your update period and can renew only if you want another year of updates.

Quick Facts

Category
Developer Tool
Platform
macOS and Linux
Primary workflow
Simultaneous access to multiple Tailscale tailnets from one workstation
Routing model
Hostname suffix matching with strict no-fallback isolation
Pricing
One-time purchase with one year of updates included
Source domain
tailmux.app