SSHive's SSH terminal is the part of the app you will open most. On the Mac it draws with xterm.js and its WebGL renderer, the engine behind VS Code's terminal, so a
tail -f that floods the screen still scrolls smoothly. Each profile keeps the host, port and user, the authentication (password, private key, or a key loaded in the macOS SSH agent), a startup command such as
cd /var/www && tmux attach, its tunnels, and a colour, tags and a folder so a long server list stays readable. Rather than retyping your servers,
import your ~/.ssh/config from the sidebar.
Behind a bastion, a profile's Jump Chain (Pro) lists up to 5 hops in order, each one a saved profile with its own credentials, and SSHive opens the whole chain for you; the
jump host guide walks through it. If the connection drops, SSHive reconnects on its own in the same tab and brings the profile's
tunnels back with it.
Passwords and key passphrases are encrypted with a key held in the macOS Keychain and saved in a file that only your user account can read; a profile never holds them in clear text. An optional setting, Require Touch ID before decrypting passwords, is off by default. On iPhone and iPad, the same profiles open in the
native SSH client for iOS once iCloud sync, a Pro option, is turned on.