GoTerm

Security

Who holds the key to your servers

GoTerm keeps the passwords and private keys that open your servers. Here is how they’re protected, where the key that opens them lives, what GoTerm’s gateway sees while you work, and how you cut GoTerm off.

You choose where the key lives

Every saved password and private key is sealed to your workspace’s own key. Keep it on GoTerm’s server, on your own laptops, or in your own cloud key. On your laptops or in your cloud key, a copy of GoTerm’s database or key file opens none of your secrets, and nor does a backup made after the move.

  • GoTerm’s server

    Every plan

    Kept apart from your data, so a copy of the database alone opens nothing. Always on, nothing to set up.

  • Your own laptops

    Personal, Teams and Business

    Made on an owner’s or admin’s laptop, and opened only by the laptops you choose or your recovery code. GoTerm never sees it.

  • Your own cloud key

    Business, or $10 a month on Teams

    Bring your own key from AWS KMS or Google Cloud KMS. Disable it in your console, and within 5 minutes GoTerm can’t open your saved secrets; open connections end within the hour.

Protected at rest, wherever the key lives. Recordings, two-factor and Private access keys stay under GoTerm’s own key.

Where your key livesConnect your AWS or Google Cloud key

How a saved key is stored

  1. 1

    Your secret

    A password or a private key you save.

  2. 2

    Sealed with its own key

    AES-256-GCM, with a new key every time it’s saved.

  3. 3

    That key sealed again

    To your workspace’s own key, on GoTerm’s server, your laptops or your own cloud key.

  4. 4

    Stored

    Only the sealed result is in the database.

Session output stays in the gateway’s memory so you can catch up. A recorded session is stored too, sealed under a key of its own on GoTerm’s server.

What GoTerm’s gateway sees, and when

GoTerm’s gateway connects to your servers for you. To do that it has to use your secrets, and your terminal passes through it. This is all it touches.

  • A saved secret, to connect

    The gateway opens a saved password or key in its memory to sign in to your server, then drops it. The key that opened it may stay in memory for up to 5 minutes, so the next connection doesn’t ask again. Neither is ever written to disk, a log or an error message.

  • Your terminal, as it passes

    What you type and what your server prints pass through the gateway, as with any SSH gateway. It keeps recent output in its memory so you can catch up, never on disk, and keeps a copy only when your workspace records the session.

  • On Free, nothing

    The desktop app on Free connects straight from your computer. Your hosts and keys stay on it, and GoTerm’s servers never see them.

Your saved secrets are protected at rest, and where the key lives decides who can open them.

Cut GoTerm off

With the key on your laptops or in your own cloud key, GoTerm needs you to open a saved secret, and you can stop answering.

  • With your own cloud key

    Disable the key in your AWS or Google Cloud console. Within 5 minutes GoTerm can’t open your saved secrets, and open connections end within the hour. Enable it again and everything works as before.

    Your own cloud key
  • With the key on your laptops

    A saved secret opens only when one of the laptops you chose answers, and what it opened stays in GoTerm’s memory for 5 minutes at most. Turn them all off and, after that, a new connection waits up to 2 minutes for a laptop, then stops; work already open keeps running. A lost laptop is removed, and the key replaced from one you still have.

    Where your key lives

Wherever the key lives, the workspace’s owner can also end everything open at once, or lock the workspace until they lift the lock. These, and every change to where the key lives, are in the audit log, with who made them.

Who can reach what

The rest of what guards your servers, from the first sign-in to the last keystroke.

  • A key for every secret

    Each saved password and private key is sealed with AES-256-GCM under a key of its own. A copy of the database alone opens nothing.

  • Open only for a moment

    A secret is decrypted in memory only when it’s used: as it’s saved, when the gateway connects with it, and when your own key is sealed for a desktop you confirmed. It never goes into logs, error messages or a teammate’s view.

  • Saved means hidden

    Once saved, a password or key isn’t shown in the browser again. A key GoTerm makes for you can be downloaded once, as it’s made. After that, only your own keys leave the server, sealed for each desktop you confirmed. A team’s keys never do.

  • Read-only that holds

    When you share a session read-only, the gateway drops the viewer’s keystrokes. It’s enforced on the server, not hidden in the page.

  • Every device confirmed

    A new browser or desktop has to be confirmed before it’s trusted. Remove one and its sessions end at once.

  • Host keys pinned

    GoTerm remembers each server’s host key. If it changes, the connection stops and you decide what happens next.

  • Narrow by design

    The gateway opens SSH connections to your servers and nothing else, with rate limits and a record of every refused connection.

  • No CDN in the middle

    Your workspace talks to GoTerm directly over TLS. Terminal traffic never passes through a CDN that could read it.

  • Two-factor sign-in

    A code from an authenticator app comes right after the password, before anything else. Owners and admins always need one.

  • Only from where you allow

    Open your workspace only from your office’s addresses, or, on a server of your own, only to your team’s own devices over WireGuard.

  • Team passwords stay put

    A team’s saved password goes only to the servers it already signs in to, known by their host keys. A look-alike gets nothing.

  • Recordings sealed too

    A recorded session is sealed under a key of its own on GoTerm’s server, and only the people allowed to watch it can play it.

Security and sign-in

A record of who did what

The audit log records sessions, files, sharing, sign-ins and errors, with who, on which device and from where. Recordings keep what a session’s screen showed, sealed, for the people allowed to watch them.

Audit log and recordings

Where your workspace runs

In the region you choose when you sign up: the US or Asia-Pacific, named in your workspace’s address. That server holds your hosts, Vault, audit log and recordings. Business, or the add-on, gives you a server of your own there, apart from every other customer’s.

Who runs GoTerm

GoTerm is run by Goterm.net and built by Kafka.id. Our terms of service and privacy policy say what we promise and what we keep.

GoTerm at goterm.net isn’t related to the open-source projects named goterm on GitHub.

Report a security problem

Found a weakness in GoTerm? Email hello@goterm.net with what you found and how to see it again, and give us time to fix it before you publish. To test GoTerm’s security on purpose, write to us first: our terms of service ask for our agreement in writing. Our security.txt names the same address.

Email a report

Questions about security

Can GoTerm see my passwords?

Your saved passwords and keys are sealed at rest, and the gateway opens one in its memory only to connect with it. It’s never written to a log or shown again. With the key on your laptops or in your own cloud key, a copy of GoTerm’s database and key file made after the move opens none of them. On Free, the desktop app connects straight from your computer, and GoTerm never sees your hosts or keys.

What if GoTerm’s database is stolen?

Every password and key saved in your Vault is sealed. With the key on GoTerm’s server, the database alone opens none of them, because the key is kept apart from it. With the key on your laptops or in your own cloud key, even the database and GoTerm’s key file together open none of your Vault’s passwords and keys, and nor does a backup made after the move.

Can I cut GoTerm off from my secrets?

Yes, with your own AWS KMS or Google Cloud KMS key: disable it in your console, and within 5 minutes GoTerm can’t open your saved secrets; open connections end within the hour. With the key on your laptops, new connections fail once none of them is on, after 5 minutes at most, while work already open keeps running. Wherever the key lives, the owner can end everything open at once, or lock the workspace.

What if we lose every laptop that holds the key?

An owner types the recovery code you saved when the key was made into the desktop app on a laptop. Without a laptop and without the code, nobody can open the saved secrets, GoTerm included: you start over, which deletes them, and save them again.

Who is behind GoTerm?

Goterm.net runs GoTerm, and Kafka.id builds it. GoTerm at goterm.net isn’t related to the open-source projects named goterm on GitHub.