Getting started
This guide takes you from account creation to a deployed and verified GPU instance in about 10 minutes.
Already have an account? Jump to Quick Start for fast deployment.
Prerequisites
Before deploying, complete these setup steps:
- A Spheron AI account (created in Step 1 below)
- An SSH key pair (generated in Step 3 below)
- Credits added to your account (added in Step 2 below)
Step 1: Create your account
Sign up
- Visit app.spheron.ai
- Click Sign Up
- Choose a sign-up method:
- Google account
- GitHub account (recommended for developers)
- Email and password
- Complete email verification if using email signup
Navigate the dashboard
Once logged in, the sidebar groups every page under three headings:
Compute- Deploy GPUs: Browse the GPU catalog and launch a GPU instance
- Deploy CPU: Launch a CPU-only node for work that never touches a GPU
- Create Volume: Provision persistent storage
- Reserved GPUs: Request long-term reserved capacity
- Instances: Manage active deployments
- Volumes: Manage persistent volumes
- Billing: Add credits, view balance, and track usage
- Team: Invite members and set roles
- Settings: Profile, SSH keys, API keys, alerts, and notifications
A theme switch at the bottom of the sidebar toggles between light and dark mode. Your choice is remembered across sessions.
Step 2: Add billing
Add credits
- Open Billing from the sidebar under Account
- Choose a payment method:
- Credit/Debit Card
- Stables (USDC/USDT)
- Add initial credits (minimum $15, maximum $5,000 per transaction)
Pricing: Pay-per-second billing with no hidden fees. See Billing for detailed pricing.
Step 3: Set up SSH access
SSH keys are required to access your GPU instances securely.
Generate SSH key
On Linux/Mac:# Generate new SSH key
ssh-keygen -t ed25519 -C "your_email@example.com"
# Press Enter to save to default location
# Set a passphrase (optional but recommended)
# Display your public key
cat ~/.ssh/id_ed25519.pub# Generate new SSH key
ssh-keygen -t ed25519 -C "your_email@example.com"
# Display your public key
type $env:USERPROFILE\.ssh\id_ed25519.pubUpload SSH key to Spheron
- Go to User Settings
- Navigate to the SSH Keys section
- Click Add SSH Key
- Paste your public key (the one ending in
.pub) - Give it a memorable name (e.g., "My Laptop")
- Click Save
Step 4: Deploy your first instance
Navigate to deploy
- Click Deploy GPUs in the left sidebar under Compute
- Browse the GPU catalog
Your search, sort, provider, and region filters persist in the address bar. Refreshing keeps the view you were looking at, and copying the link opens the same filtered catalog for a teammate.
Select your GPU
For a first deployment, use:
- GPU: RTX 4090 (24 GB VRAM)
- Cost: ~$0.52/hour
- Good for: Learning, testing, small models
Click on the RTX 4090 to proceed.
Configure instance
- Region: Choose the region closest to you for lower latency
- Operating System: Select Ubuntu 22.04 LTS for the most stable GPU driver support
- Storage: Keep the default (usually sufficient)
- SSH Key: Select the key you uploaded earlier
- Startup Script (optional): Leave blank for now. See Startup Scripts for advanced automation.
Review and deploy
- Check the Order Summary on the right:
- Hourly cost
- Current balance
- Instance configuration
- Click Deploy Instance
- Wait 30-60 seconds for provisioning
Step 5: Connect to your instance
Get connection details
Once deployed, the instance dashboard shows:
- IP address
- Username (usually
root,ubuntu, or provider-specific) - SSH connection command
Connect via SSH
ssh root@<your-instance-ip>If using a custom SSH key location:
ssh -i ~/.ssh/id_ed25519 root@<your-instance-ip>On first connection, type yes to accept the host fingerprint. Enter your SSH key passphrase if you set one.
Step 6: Verify your setup
Once connected, verify everything is working.
Check GPU
nvidia-smiExpected output shows GPU model (RTX 4090), memory (24 GB), driver version, and GPU utilization.
Check CUDA
nvcc --versionThe output shows the CUDA compiler version.
Check system
# Check CPU and memory
htop
# Check disk space
df -h
# Check OS version
cat /etc/os-releaseTest GPU access
# Simple GPU test
python3 -c "import torch; print(f'CUDA available: {torch.cuda.is_available()}')"PyTorch does not need to be pre-installed. Install it when needed for your workload.
Troubleshooting
Issue: Cannot connect via SSH
Symptoms: Connection refused or timeout when running ssh
Diagnosis: Verify the SSH key is loaded:
ssh-add -lResolution: If the key is not listed, add it:
ssh-add ~/.ssh/id_ed25519Additional checks:
- Verify you uploaded the correct public key
- Check that firewall rules allow SSH (port 22)
- Try with an explicit key path:
ssh -i ~/.ssh/id_ed25519 <user>@<ip>
Issue: GPU not detected
Symptoms: nvidia-smi returns an error
Diagnosis: Drivers may still be loading after provisioning
Resolution: Wait 30 seconds and run nvidia-smi again. If the error persists, reboot the instance with sudo reboot.
Issue: Instance deployment failed
Symptoms: Deployment status shows "failed"
Resolution:
- Check that your account balance has sufficient credits
- Try a different region (some may be at capacity)
- Contact support if the issue persists
Stop or terminate your instance
When you are finished for now but will come back to the same environment, stop the instance:
- Go to the instance dashboard
- Click Stop
- Review the quoted stopped rate and confirm
The GPU stops billing, the disk and everything on it is preserved, and starting it again returns the same public IP. Stopping is available on Spheron AI and Spheron ES. See Instance lifecycle for the full support matrix.
When you are finished entirely, terminate the instance:
- Go to the instance dashboard
- Click Terminate or Delete
- The instance stops and all data is permanently deleted
What's next
- Quick Start: Condensed deployment flow for users already set up
- CPU Nodes: Deploy CPU-only compute for non-GPU workloads
- Instance Lifecycle: Stop, start, and restart an instance
- SSH Connection Guide: Advanced SSH setup and troubleshooting
- Jupyter Notebook: Browser-based development via SSH tunnel
- VS Code Remote: Remote development directly on the instance
- Security Best Practices: Keep your account secure