Every agent. Every machine. One cockpit.

dev-mux is a control plane — mission control — for running and monitoring fleets of AI coding agents like Claude Code across your own machines: a hosted hub on your tailnet, while your code stays on your machines. It gives you one live cockpit over every terminal, agent, repo, and machine: persistent sessions that never drop, a real-time map of your fleet, and access from a browser, with an iOS app and Even Realities G2 glasses in testing (not yet generally available). You bring the compute; dev-mux never runs your workloads or stores your code.

dev-mux is built on SSH + tmux, not a replacement for them. tmux gives you a persistent session on one machine; SSH gets you into that machine. dev-mux adds the fleet layer on top: one cockpit across every machine at once, a live status map, automatic reconnect, and a browser cockpit (iOS and G2 glasses surfaces are in testing) — so you're not manually SSHing into a dozen boxes and juggling terminal tabs.

No. Your agents run on your own machines (spokes). The hub is a thin relay that brokers terminal access — it never executes your workloads or stores your code.

A spoke is one of your repos running an agent on a machine you control — a laptop, a cloud VM, a Raspberry Pi. You self-host and self-administer them; add as many spokes as you need and the hub keeps a live map of all of them.

No — that's the point. Your sessions live in tmux on the hub and the cockpit reconnects automatically, so they stay persistent across dropped connections, sleeps, and network changes. Close the lid, switch networks, come back hours later: your agents are right where you left them.

Today it's tuned for Claude Code, but the transport is agent-agnostic — it's SSH + tmux underneath, so any terminal-driven agent runner fits the same seam.

Each tenant gets an isolated hub (a hard boundary, not shared state). Hubs are private to your tailnet by default, you hold your own keys, and your spokes stay self-hosted and self-administered — your code and credentials never leave your perimeter.

No. Everything moves over your own Tailscale (WireGuard) tailnet, encrypted end-to-end between your UIs, hub, and spokes — no one on the network path, dev-mux included, can read your traffic in transit. Your code stays on your self-hosted spokes and is never stored by us, and your hub is a single-tenant instance isolated to your own tailnet. For a guarantee that reaches all the way down to the host itself, Custom hosting runs the hub inside your own perimeter. SOC 2 and SOC 1 attestation are on our roadmap shortly after launch.

Yes. Your spokes are always self-hosted on Solo and Team; the hub itself is managed for you. If you need the hub inside your own perimeter too — self-hosted or on-prem, air-gapped networks, your own compliance boundary — that ships on the Custom plan. It's set up with you rather than sold self-serve, so tell us what you need and we'll scope it.

Open the Tailscale setup guide. It shows the current admin-console steps for defining the hub tag, creating a scoped OAuth client, and copying your credentials and tailnet DNS name into dev-mux.

dev-mux runs over your own tailnet. Solo use fits Tailscale's free Personal plan. A commercial team of around five needs Tailscale's Standard plan (about $8/user/mo) — that's paid to Tailscale, not to us, and your managed hub joins as a single device.