Adding an SSH Key

Register a public SSH key with the portal so it's available to drop into new servers at order time and to deploy onto existing ones. Keys are tied to your user, not to a specific organization, so they follow you across every team you belong to.

If you don't have an SSH key yet - that is, no .pub file on your computer - go through Generating SSH Keys first, then come back here.

You should already have:

• A public key on your clipboard, or somewhere you can copy from. It's the long single line that starts with ssh-ed25519, ssh-rsa, or ecdsa-sha2-… and ends with a comment like your email address.
• A name in mind for the key. Something that identifies the device - "Work MacBook", "Home desktop", "CI runner". You'll see this name when picking keys at order time, so make it specific enough to tell apart from anything else you might add later.

If you only have the private key handy (a file like id_ed25519 with no extension), stop - that's not what goes into the portal. See Generating SSH Keys for how to print the public half.

1. In the sidebar, find your profile button at the bottom - it shows your avatar, name, and email.

2. Click your profile button. A small menu opens upward.

3. Click SSH Keys and the SSH Keys page will open.

If you've never added a key, the page shows an empty state with a short prompt and the Add SSH key button. If you have, your existing keys are listed in a stack of cards, each showing the key's name, algorithm, and a short fingerprint hint so two keys are easy to tell apart.

1. Click Add SSH key in the top right of the page.

2. A dialog opens with two fields: Name and Public key.

1. Name - type a label that identifies the device this key lives on. Examples: "Work MacBook", "Home desktop 2026", "CI runner - GitHub Actions". You'll see this name later when picking which keys to install on a new server.

2. Public key - paste the key content. It must be the public key (one long line starting with ssh-ed25519, ssh-rsa, or similar - including the trailing comment), not the private key.

   1. Paste the whole line on one row. Don't add line breaks.
   2. If the portal can't parse what you've pasted, you'll see a red "Invalid public key" message under the field. Most often this means you accidentally pasted the private key (it would span many lines and start with -----BEGIN), or the line got broken on whitespace.

3. Click Add key at the bottom of the dialog. The button stays disabled until both fields are valid.

The dialog closes and your new key shows up in the list. You'll see a green "SSH key added." confirmation at the top of the page.

• The key is available immediately when you order a new resource - at the SSH keys step of the order flow, your new key appears in the list and is selected by default along with your other keys.
• Existing servers do not get the new key automatically. Adding a key here only affects new provisions. To put it onto an existing server, paste the public key into that server's ~/.ssh/authorized_keys file by hand (over an existing SSH connection), or reinstall the OS with your new key(s) selected.

1. Hover the row of the key you want to change. Two small icons appear on the right - a pencil (edit) and a trash can (delete).

2. To rename or replace the key content, click the pencil. The same dialog opens, pre-filled with the current values. Edit and click Save.

3. To remove the key, click the trash can. A small confirm dialog opens. Slide the slider to confirm.

Removing a key from your account does not remove it from servers it's already deployed to - those servers still trust the key until you go in and edit their ~/.ssh/authorized_keys directly. If you're rotating a key because the private half may have leaked, you need to do both: delete here, and clean up every server that had it installed.