SSH Web Terminals & Server Management

Sometimes you want SSH access from a browser — on a tablet, an iPad, a Chromebook, or just to avoid the friction of "where's my SSH key on this device." This category covers the browser-based and self-hosted options.

Browser SSH clients with saved-server bookmarks

• ★ Termix — modern web SSH client with saved servers, tags, multi-tab, key management. Single Docker image. The default in 2026 for "self-hosted SSH manager."
  • https://github.com/LukeGus/Termix
• Sshwifty — minimal SSH/Telnet web client; Go-based; one binary or container.
  • https://github.com/nirui/sshwifty
• Shellngn — commercial; free tier for personal use.

Browser as a terminal (no saved-server UX)

• ★ Wetty — terminal-on-the-web; runs ssh or local shell over WebSockets. Old reliable.
  • https://github.com/butlerx/wetty
• ★ ttyd — share your terminal session over the web. Single binary.
  • https://github.com/tsl0922/ttyd
• GoTTY — older; the predecessor to ttyd.
  • https://github.com/sorenisanerd/gotty (maintained fork)
• WebSSH2 — Node.js SSH-over-WebSocket; simpler than Termix.
  • https://github.com/billchurch/WebSSH2
• Cockpit Terminal — bundled with Cockpit; browser terminal as part of the server admin UI.

Desktop SSH managers (not browser, but worth noting)

• ★ XPipe — desktop app; manages SSH connections, files, scripts across many servers. Cross-platform.
  • https://github.com/xpipe-io/xpipe
• Termius — commercial; cross-device sync; popular.
• Royal TS / Royal TSX — commercial; widely used in enterprise.
• Tabby (formerly Terminus) — cross-platform terminal + SSH.
  • https://github.com/Eugeny/tabby

Modern terminal apps with SSH built in

• Ghostty — fast modern terminal; combine with ~/.ssh/config aliases.
• WezTerm — ditto; has built-in SSH multiplexing.
• iTerm2 — Mac; built-in SSH integration with badges / triggers.

Bastion / identity-aware SSH (if "saved servers" is the main need)

For team / enterprise use, see SSH & Bastion — Teleport, Tailscale SSH, smallstep — these are usually the right answer for shared servers.

Patterns to adopt

• ★ Don't expose web SSH to the public internet. Put Termix / Wetty / ttyd behind Tailscale or Cloudflare Access. A web shell is a remote shell — treat it accordingly.
• TOTP / OIDC in front of any web SSH (Authelia, Authentik, Pomerium).
• Per-user SSH keys stored in the manager, not shared accounts.
• SSH certificates > long-lived authorized_keys even for web clients; see SSH & Bastion.
• Audit logs on the manager — at minimum log who connected to what.

Pick this if…

• Default self-hosted SSH manager (browser): Termix.
• Just need a terminal in a browser: ttyd or Wetty.
• Desktop, multi-server visualization: XPipe.
• Team / enterprise / compliance: Teleport (see SSH & Bastion).
• You already use Tailscale: Tailscale SSH covers most use cases without a web UI at all.