A real terminal, without SSH keys on laptops.
Users open a full interactive terminal in the browser and move files beside it. The gateway holds the credentials, verifies the server, applies your command policy and records everything.
What you get
Credentials stay in the gateway: a shared service account, personal accounts per user, or typed at connect and never stored. Keys and passwords rotate automatically.
Modern and legacy SSH: current algorithms by default, plus a per-host legacy compatibility mode and keyboard-interactive sign-in for older systems.
File transfer under policy: an SFTP panel next to the terminal, with size limits and every file audited by name, size and SHA-256.
Command policy: block or flag risky commands as they're typed, system-wide or per host.
Your own shell on a shared account: when a team signs in as one account, each person still gets their own history, prompt, aliases, variables and git author. Administrators set organisation and group layers, and nothing is installed on the server.
Production looks like production: tagged hosts show their colour, label, frame and banner in every terminal, and users can't change them.
A real terminal, without SSH keys on laptops.
- Credentials stay in the gateway
- Modern and legacy SSH
- File transfer under policy
- Command policy
- Your own shell on a shared account
- Production looks like production
A full interactive terminal in the browser.
Set up
- 01
Add the host and choose how it signs in
- 02
Test connection and pin the host key
- 03
Grant access, standing or by request
- 04
Users connect from their list.
FAQ
Prove it on your own systems.
A proof of concept runs inside your environment, on the systems you choose, with success criteria agreed up front.
- 01Scope call
- 02Deploy & connect your systems
- 03Review the evidence together