Features ›

SSH and terminals

A shell on the server, in a tab next to its files and its database, signed in with the credential the library already holds.

Terminals

An SSH connection opens as a terminal tab. It signs in with the connection's credential (a password, a key, or keyboard-interactive prompts answered in a dialog), and the status bar shows who you are and where.

  • Tabs for the terminal, the server's files and its database, side by side
  • Terminal settings of its own in Settings
  • The session survives switching tabs
An SSH terminal tab: a directory listing of the web root and uptime, signed in as admin on the web server

Tunnels

Define a bastion host once and attach it to any database or file server that has to go through it. The tunnel is used everywhere that connection is: the schema tree, queries, transfers, and its own Test button. The bastion's host key is pinned separately from the server behind it.

Host keys

Every SSH, SFTP and tunnel connection checks the server's host key. Keys already in your ~/.ssh/known_hosts are trusted without asking; anything else asks, and a key that has changed since you trusted it is stopped, not accepted. Old algorithms (ssh-dss, SHA-1 RSA and key exchange) are never offered.

Commands from automation, only if you say so

Scripts and AI agents can run a command on a server through Hydra only when you switch that on for the connection, or approve a request for an hour. Every command, its exit status and who ran it go in the Automation Log, and the full output stays on this Mac.

More about automation →

Try it on your own servers

Fourteen days, everything unlocked, no account required.

Download for macOS