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.Documentation Index
Fetch the complete documentation index at: https://runcrate.ai/docs/llms.txt
Use this file to discover all available pages before exploring further.
Generating a Key Pair
If you do not already have an SSH key pair, generate one:- Private key —
~/.ssh/id_ed25519(keep this secret) - Public key —
~/.ssh/id_ed25519.pub(upload this to Runcrate)
Copying Your Public Key
Adding to Runcrate
Managing SSH Keys
The SSH Keys tab shows all keys in the current workspace:| 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 workspace.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. |