---
summary: Publish your public SSH key once in the ScaiGit console; it works on every
  instance you use within a minute.
title: SSH keys
path: guides/ssh-keys
status: published
---

# SSH keys

You publish your public SSH key once, in the ScaiGit console, and ScaiGit
adds it to your account on every instance you use. Withdraw it there and it
disappears everywhere.

## Publish a key

1. If you have no key yet, create one: `ssh-keygen -t ed25519`. This writes
   `~/.ssh/id_ed25519` (private, keep it to yourself) and
   `~/.ssh/id_ed25519.pub` (public).
2. Open <https://scaigit.scailabs.ai/console/>, sign in with ScaiKey and go to
   **My SSH keys**.
3. Give the key a title, paste the single line from the `.pub` file, and save.
4. After a minute at most, test it against your instance:

   ```bash
   ssh -T git@<organisation>.scaigit.scailabs.ai
   ```

   The answer greets you by your user name.

## Rules for keys

- **Public keys only.** A pasted private key is refused, with an explanation.
- **Ed25519 or ECDSA recommended;** RSA must be at least 2048 bits; DSA is
  not accepted.
- **One person per key.** A key someone else has already published is
  refused, because the forge links each key to exactly one account.
- Up to **20 keys** per person.

## Keys you add yourself

You can still add a key directly in an instance's web interface under
**Settings → SSH / GPG keys**. ScaiGit leaves such keys alone. Keys published
through the console are marked as managed and should be changed in the
console only.

## Keys for machines

For a build server or a script that needs one repository, use a deploy key
instead of a personal key: a repository administrator adds it under the
repository's **Settings → Deploy keys**, read-only or with write access.
