SSH Keys
SSH keys provide secure, password-less access to your GPU instances. Add your public key to Runcrate, and it will be injected into any new instances you deploy.
Generating a Key Pair
If you do not already have an SSH key pair, generate one:
# Ed25519 (recommended)
ssh-keygen -t ed25519 -C "your-email@example.com"
# RSA (if Ed25519 is not supported)
ssh-keygen -t rsa -b 4096 -C "your-email@example.com"
- Private key —
~/.ssh/id_ed25519 (keep this secret)
- Public key —
~/.ssh/id_ed25519.pub (upload this to Runcrate)
Copying Your Public Key
# macOS
pbcopy < ~/.ssh/id_ed25519.pub
# Linux
cat ~/.ssh/id_ed25519.pub | xclip -selection clipboard
# Windows (PowerShell)
Get-Content ~/.ssh/id_ed25519.pub | Set-Clipboard
Adding to Runcrate
Navigate to Keys
Go to Dashboard → Keys and select the SSH Keys tab.
Click Add SSH Key
Click Add SSH Key.
Enter a Name
Give the key a recognizable name (e.g., macbook-pro, work-desktop).
Paste Your Public Key
Paste the contents of your .pub file.
Save
Click Save. The key is now available for new instance deployments.
Managing SSH Keys
The SSH Keys tab shows all keys in the current project:
| Field | Description |
|---|
| Name | The label you gave the key |
| Fingerprint | Unique identifier for the key |
| Type | Key algorithm (Ed25519, RSA, ECDSA) |
Deleting a Key
Click Delete to remove an SSH key from the project.
Deleting an SSH key from Runcrate does not remove it from currently running instances. It only prevents the key from being added to future deployments.
Supported Key Types
| Type | Recommended | Notes |
|---|
| Ed25519 | Yes | Modern, fast, secure. Best choice for most users. |
| RSA (4096-bit) | Acceptable | Widely compatible. Use 4096 bits minimum. |
| ECDSA | Acceptable | Good performance. Less common than Ed25519. |
Multiple Keys
You can add multiple SSH keys per project. All keys will be injected into new instances, allowing multiple team members or machines to connect.
