Ferrix vs RMUX
Ferrix
github.com
RMUX
rmux.ioSide by side
| Figure | Ferrix | RMUX |
|---|---|---|
| Price from | — | Free |
| Free plan | — | Yes |
| Free trial | — | — |
| Open source | — | — |
| Web | — | Yes |
| Windows | — | Yes |
| macOS | Yes | Yes |
| Linux | Yes | Yes |
| API | — | Yes |
| Self-hosted | — | Yes |
| Plans published | 0 | 1 |
| Spec score · Terminal Multiplexers | 7.6 (#14) | 8.3 (#4) |
| Installation | The README says to install from source or Cargo for now and marks the Homebrew tap and crates.io installation as coming soon. | Install options include package managers, prebuilt installers, and Cargo; the docs say quick installers verify SHA256. |
| License | Ferrix is dual-licensed under MIT or Apache-2.0. | RMUX is dual-licensed under MIT or Apache License 2.0. |
| Purpose | Ferrix is a Rust terminal multiplexer inspired by GNU Screen and tmux. | RMUX is a local terminal multiplexer for persistent, scriptable terminal sessions and terminal automation. |
| Security | The README lists TLS 1.3, bcrypt password hashing, configurable rate limiting, role-based permissions, and read-only session locking. | During Web Share, shells and PTYs stay on the local daemon while the browser decrypts encrypted terminal updates locally; tunnels carry encrypted frames. |
Plans
In their own words
RMUX
RMUX is a local terminal multiplexer that keeps shells under a daemon on the user’s machine. Version 0.10.0 provides 90 tmux-compatible commands for persistent sessions that can be detached and reattached. Its automation SDKs let programs work with typed session, window, and pane handles, send keyboard and mouse input, wait for output, capture structured snapshots, and receive pane events. Official SDKs are available for Rust, Python, and TypeScript; the Python and TypeScript SDKs require the RMUX binary to be installed first.
Web Share creates browser links to a pane or session while its shell stays local. Links can allow read-write operation or read-only viewing, with separate pairing PINs enabled by default. The browser decrypts terminal updates locally. Sharing can use private Tailscale access, public SSH tunnel presets, or a user-provided ingress URL. RMUX says tunnels can see handshake metadata and encrypted frames, but not keystrokes, PINs, raw tokens, or terminal cells. The Web Share frontend can be self-hosted. RMUX is dual-licensed under MIT or Apache-2.0 and is available through package managers, prebuilt installers, or Cargo.