Alternatives
Products that do what TailMux does
Multiple Tailscale tailnets at once, no switching + no VM
- 1
- 2
- 3
- 4VV
2021 · github.com
- 5RD
2015 · lc.cx
- 6
- 7TR
2020 · github.com
- 8TO
2015 · github.com
- 9RA
RunKit is a browser based tmux manager that works great on a phone over Tailscale. I created it to be able to run several AI agents in parallel, after trying out several existing tools. There's no database (state is read live from tmux). Right now, its the first thing I install on any server, and from there on RunKit becomes the management cock-pit for that server. Also, for running several agents in parallel, RunKit has been a lifesaver. It shows the status of all running agent on the left panel, and sends you a notification anytime an agent is stuck. Please try it out, and let me know if…
Jul 2026 · github.com
- 10AB
2023 · github.com
- 11RS
2022 · github.com
- 12TL
I'm Dustin Kirkland, author of Byobu[1]. I built Trustmux[2] to solve a personal problem: secure, encrypted access to my tmux[3] and Byobu sessions from my phone, without the pain of other mobile shell approaches. I run long-lived shells, Claude, and other sessions in the background on my workstation, and I needed to check in from mobile — securely, with real TLS certificates and Tailscale-backed privacy, not some insecure workaround. Why not SSH / Mosh / Claude Mobile? - SSH/Mosh: Synchronous connection state is brutal on mobile. Latency, network handoffs between WiFi and…
Jun 2026 · trustmux.dev
- 13LV
Hello HN! We've been working on a new hypervisor https://kwarantine.xyz that can run strongly isolated containers. This is still a WIP, but we wanted to give the community an idea about our approach, its benefits, and various use cases it unlocks. Today, VMs are used to host containers, and make up for the lack of strong security as well as kernel isolation in containers. This work adds this missing security piece in containers. We plan on launching a free private beta soon. Meanwhile, we'd deeply appreciate any feedback, and happy to answer any questions here or on our slack…
2021
- 14WA
2023 · github.com
- 15NA
Hi, over the past few months I've been working on this project: Numax is a small Rust runtime that does three things: it runs WebAssembly modules in a sandbox, has a built-in local key-value store, and syncs everything across nodes with CRDTs and gossip. Basically, you write a wasm module, run it on two machines, and they converge (I hope !). It's a decentralized system... I hope someone finds it interesting! There's a whitepaper I've put a lot into, and I think the code isn't bad either! I believe there's still room in this world for software that's fun and well made, and while building…
Jun 2026 · github.com
- 16HD
Hey everyone! One of the problems I ran into is that a large part of the VM-provider ecosystem is currently paid closed-source SAAS products with varying degrees of reliability. I wanted an OSS distributed microVM orchestrator and I couldn't find one. Hyper is a distributed FirecrackerVM orchestrator written in Elixir (BEAM), with gRPC support for non-BEAM clients. Hyper is: - Distributed -- it's designed to run across a cluster of bare metal machines, and will automatically connect to other Hyper nodes. - Fast -- it builds COW layers to enable fast, localized COW forking. Cold boots happen…
Jul 2026 · github.com
- 17IB
Hi HN, I'd like to share a small Go utility I wrote called prxy. The idea was born out of my frustration with accessing my self-hosted services when I'm on the go. I use WireGuard to connect to my homelab, but I really dislike sending all my computer's traffic through my home network — it slows things down and is inconvenient. I wanted proper application-level split-tunneling. A tool I love, wireproxy, got me most of the way there by creating an HTTP proxy from a WireGuard peer. This is perfect for apps that let you configure a proxy. The problem was the other 10%: apps that don't. Think of…
2025 · github.com
- 18I2
2017 · github.com
- 19WB
I needed a web terminal I could drop into K8s sidecars and internal tools without pulling in heavy dependencies or running a separate service. Existing options were either too opinionated about the shell or had fragile session handling around reconnects. WooTTY wraps any binary -- bash, ssh, or custom tools -- and serves a browser terminal over HTTP. Sessions survive reconnects via output replay. There's a Resume/Watch distinction so multiple people can attach to the same session without stepping on each other.
Mar 2026 · github.com
- 20CV
I built a chained VPN lab to support multi-user traffic isolation using only raw Linux tools. Each user gets: - A WireGuard tunnel - A dedicated namespace (wg-$user) bridged via veth - NAT and routing table override - A second namespace (ovpn-$user) running OpenVPN - Final egress through tun1 The entire setup is controlled with bash scripts and PostgreSQL — no Docker, no containers, no Python, just raw netns, iptables, ip rule and shell. Built for GDPR-compliant VPN infra with real isolation per collaborator. Code and README:…
2025 · github.com
- 21HA
Hey HN. I'm an engineering student at Waterloo building stateful AI agents, and I kept hitting the same wall: whenever my Python scripts crashed or dropped a connection, the underlying Puppeteer or Ollama processes would just sit there orphaned, eating RAM until the node OOM-killed itself. Standard load balancers break sticky sessions, and passive HTTP timeouts are too slow for cleanup. I couldn't find a good local process pool that actually cleaned up dead stateful sessions reliably, so I built Herd in Go. It uses a persistent stream (gRPC/Unix sockets) strictly as a dead-man's switch.…
Mar 2026
- 22RA
Hey HN, There’s been a lot of interest recently in meta-harnesses, loops, and multi-agent orchestration. Obviously, there are already a lot of good tools: Conductor, cmux, the native Codex / Claude Code apps, etc. For my own use cases, I’ve felt that the orchestration layer tends to feel overengineered. I mostly wanted a simple local harness (i.e Pi) for running and tracking CLI agents with the ability to hop in (via tmux). Relaymux is my opinionated attempt at that. A few design principles: - The frontend is just Telegram / iMessage / CLI. If I want more visibility, I hop…
Jun 2026 · github.com
- 23CC
Hey HN, I built ctx because I was tired of the mental overhead of managing multiple client environments. Every context switch meant: change AWS profile, switch kubeconfig, start the right SSH tunnels, set the right env vars, remember which VPN i need to connect to. Miss one step and you're deploying to the wrong environment. The problem: Existing tools are siloed. kubectx handles Kubernetes. aws-vault handles AWS. direnv needs .envrc files everywhere. SSH tunnel managers don't know about your cloud context. Nothing ties them together. ctx does one thing: Atomic context switches across all of…
Jan 2026 · github.com
- 24NV
May 2026 · github.com
Ranked by how close each launch is in meaning, then by votes. Refine with a description →