Skip to content

User settings

Manage your account profile, SSH keys, and API access credentials.

Access settings at app.spheron.ai > Settings

Profile

Update account information and preferences.

Profile Settings

Available fields:
  • Full Name: Editable
  • Email Address: Must be changed through your OAuth provider (GitHub/Google)
  • Company: Optional organization name

Click Save Changes to apply updates.

SSH keys

Manage SSH keys for secure instance access.

SSH Keys Management

Key information displayed:
  • Name and fingerprint
  • Public key (with copy function)
  • Delete action

Adding SSH keys

  1. Click + Add SSH Key
  2. Enter a key name
  3. Paste public key content (from ~/.ssh/id_*.pub)
  4. Click Save
Generate SSH keys:
# Linux/Mac
ssh-keygen -t ed25519 -C "your_email@example.com"
cat ~/.ssh/id_ed25519.pub
 
# Windows PowerShell
ssh-keygen -t ed25519 -C "your_email@example.com"
type $env:USERPROFILE\.ssh\id_ed25519.pub

See SSH Connection Guide for detailed setup.

Security: Only upload public keys (.pub files). Never share private keys.

API keys

Generate and manage API keys for programmatic access.

API Keys Management

Managing keys

Current key:
  • View masked key (sai_pk_s•••••••••4ZPl0Gvw)
  • Copy to clipboard
  • Check expiration date
  • Revoke if compromised
Generate new key:
  • Click + Generate New Key
  • Use separate keys for different projects or environments
  • Generate a new key before the current one expires

API capabilities

With an API key, you can:

  • Deploy and manage GPU instances
  • Check GPU availability and pricing
  • Manage SSH keys programmatically
  • View account balance
  • Monitor usage and billing

See the API Reference for complete endpoint documentation and usage examples.

Security: Store API keys in environment variables. Never commit them to version control.

Security best practices

API keys:
  • Store in environment variables; never hardcode them
  • Revoke immediately if compromised
  • Rotate every 90 days
  • Generate separate keys per environment
  • Never commit to version control
SSH keys:
  • Add keys only from controlled devices
  • Remove keys from lost or compromised devices
  • Use passphrases on private keys
  • Delete unused keys regularly
Monitoring:
  • Review active keys periodically
  • Remove unrecognized keys immediately
  • Check key expiration dates

See Security best practices for comprehensive guidelines.

Frequently asked questions

Q: Why can't I change my email?

A: Email is managed through your OAuth provider (GitHub/Google). Update it there first.

Q: How many SSH keys can I add?

A: There is no limit. Add keys for different devices or team members as needed.

Q: What happens when my API key expires?

A: Applications using that key fail. Generate a new key before expiration.

Q: Can I have multiple active API keys?

A: One active API key at a time. Generate a new key to replace the existing one.

Q: Where do I find my SSH public key?

A: Linux/Mac: cat ~/.ssh/id_ed25519.pub Windows: type $env:USERPROFILE\.ssh\id_ed25519.pub

Q: How do I rotate API keys safely?

A: Generate a new key, update your applications, test them, then revoke the old key.

What's next