Bind a local port and the SSH tunnel opens the moment something touches it — through a chain of jump hosts if you need one — then tears itself down once the port goes idle.
Tunnels that open themselves
Connect lazily on first access and idle out on a timer you set. The listener never goes away, so nothing in your workflow has to know a tunnel was ever closed.
Jump-host chains
Reach a destination several SSH hops away by describing the chain once. Each hop is authenticated on its own terms.
Flexible authentication
SSH agent, private keys with passphrases, or passwords — stored encrypted at rest, never in a plaintext config file beside the app.
Host-key verification
Trust on first use with an explicit prompt, and a changed host key is refused rather than shrugged at. The check that protects the tunnel is not optional.
Live monitoring
Per-tunnel state, byte rates and connection counts, in a card view or a sortable list — so a tunnel that is quietly failing looks different from one that is quietly idle.
Nothing leaves the machine
No telemetry, no account, no update beacon. The only network traffic Jump Hippo makes is the SSH you asked it for.
