Connecting to a host
Add a host
Click + New host and fill in the basics:
| Field | Notes |
|---|---|
| Name | A label for the connection (e.g. prod-db-01). |
| Host | Hostname or IP. |
| Port | Defaults to 22. |
| User | The SSH user. |
| Auth | Password or Key. |
For key auth, paste the private key (and passphrase if it has one). For password auth, enter the password. Either way the secret is written to your OS keychain, not to disk in plaintext.
Organise hosts into folders, give them colours, and mark the ones you reach for as favourites. Each host also has a Copy action that gives you a ready-to-run ssh command.
Import from ~/.ssh/config
Switching from the CLI? Use Import to pull your existing hosts — including their ProxyJump relationships — into the vault in one step.
Host-key verification
On the first connection, SSH Ache shows the server's key fingerprint and asks you to confirm it. The key is then pinned in a local known_hosts store. If a host's key ever changes, the connection is refused with a warning — the standard defence against a man-in-the-middle.
Jump hosts (ProxyJump)
Reach a host through a saved bastion in one click. Pick the jump host on the connection and SSH Ache tunnels through it. The jump host's key is verified too — it's never waved through.
Port forwarding
From an active session you can open:
- Local forward (
-L) — expose a remote service on a local port. - Remote forward (
-R) — expose a local service on a remote port. - Dynamic SOCKS5 (
-D) — a proxy you can point a browser at to route traffic through the box.
Next steps
- Terminal features — tabs, splits, broadcast input, output triggers.
- SFTP & file transfer