Launch a GPU session
Once you have credits, click Launch GPU-Native Desktop and choose a GPU profile — your Linux desktop opens in the browser.
GPU profiles
| Profile | GPUs | Burn rate | Good for |
|---|---|---|---|
| Small | 1 | 1× | Notebooks, analysis, light viz |
| Medium | 2 | 2× | Multi-GPU experiments, bigger models |
| Large | 4 | 4× | Training, large simulations |
| Max | 8 | 8× | Heavy multi-GPU workloads |
Usage is billed as wall-clock minutes × GPU count, including idle time while the tab is open. A Max session burns 8× faster than a Small one. Pick the smallest profile that fits your workload.
Launching
Pick a GPU profile
The profile picker on the launch page lists Small, Medium, Large, and Max with a burn-rate hint. Pick what your workload needs.
Click 'Launch GPU-Native Desktop'
The button triggers a session claim. If enough GPUs are free, the desktop starts immediately. If not, you're queued — the page shows your position and the reason.
Your desktop opens in the browser
A full XFCE Linux desktop streams into the tab. See Your desktop & tools.
Resuming a saved desktop
If you previously detached or your session was paused, the launch page shows a "Your desktop is saved" resume panel. You can re-launch it (with the same GPU profile) or start fresh.
If GPUs are busy: the queue
When not enough GPUs are free the request joins a fair queue instead of failing:
- The queue is FIFO but schedulability-aware — a large request that can't run yet doesn't block smaller requests that can.
- Your position and reason are shown ("insufficient free GPUs for requested profile").
- Your session starts automatically when GPUs free up.
You can leave the queue at any time.
Billing during a session
While your session is active, the browser sends periodic heartbeats. Each heartbeat deducts elapsed minutes × GPU count from your balance. You see the running timer in the page footer.
When your balance runs out:
- Grace period (~2 hours) — the desktop stays up with billing paused so you can top up.
- Grace expires — the desktop is shut down and GPUs released, but your files are saved.
- Top up and relaunch — your persistent volume is remounted and you continue from where you left off.
Detach vs. End session
| Action | What happens |
|---|---|
| Detach (disconnect button in the control bar) | Returns to the home page. Desktop keeps running. Minutes keep counting. |
| End session (power button in control bar) | Stops the desktop immediately, releases GPUs, stops billing, saves your files. |
| Close the tab | Same as End session — the session is released. |
Detaching returns you to the launch page but the GPU session remains active and credits continue to tick down. Only End session (or closing the tab) stops the clock.
Next: learn what's waiting for you in the desktop with Your desktop & tools.
Prefer a terminal over a browser? See SSH-only sessions for headless GPU access without the X desktop. Agents can claim SSH sessions autonomously via x402.