Cloud worker Compute
Per-minute pricing for cloud DevBoxes.
Six tiers across Linux and Windows. From $0.06/hr. Billed only while running, paid from your wallet.
Linux DevBoxes
Lightweight Ubuntu DevBoxes. Per-minute billed.
Windows VMs
Full Windows 11 VMs (KVM/QEMU). Per-minute billed.
How we compare
Linux tiers run ~30% less than the closest GitHub Codespaces machines.
| Workload | ClusterCode | Competitor | Their price | You save |
|---|---|---|---|---|
| 2 vCPU · 4 GB Linux | $0.12/hr | GitHub Codespaces 2-core (2 vCPU / 8 GB) | $0.18/hr | 33% |
| 4 vCPU · 8 GB Linux | $0.24/hr | GitHub Codespaces 4-core (4 vCPU / 16 GB) | $0.36/hr | 33% |
| 4 vCPU · 8 GB Windows | $0.24/hr | Amazon WorkSpaces Performance bundle (~4 vCPU / 8 GB) | $0.38/hr | 37% |
Competitor prices verified 2026-06-09. Linked above. WorkSpaces hourly is an amortisation of the AlwaysOn Performance bundle at 160 h/mo; the published bundle is monthly, not hourly.
Your sessions travel with you
Cloud workers are disposable. Your work isn’t.
Because compute is billed only while running, you’ll stop DevBoxes constantly — and land on a different worker next time. So your agents’ logins, sessions, and settings sync off-host, encrypted with your own per-user key before they leave the machine, and hydrate into your next launch automatically. Your code stays in git and on the machine that made it — we never store your workspace. No worker is a home base you have to get back to.
Claude, Codex, and Copilot logins follow you to every worker — authenticate once.
Every new container picks up your history. Running containers aren’t live-synced while they work.
On by default, opt out to start fresh, or delete your stored data anytime. Recoverable for 14 days.
Frequently Asked Questions
When am I billed?
Only while a Cloud worker DevBox is running. Stopped DevBoxes cost $0 — no idle compute charges, no per-GB storage fees. Billing is per-minute, drawn from your wallet balance.
How does Cloud worker compute relate to my Starter or Pro plan?
Cloud worker compute is wallet-billed on all paid plans. Your plan includes a monthly compute allowance ($2/mo on Starter, $6/mo on Pro, included with Enterprise per-user); usage beyond that draws from your wallet top-ups. Cloud workers require a paid plan — among paid plans, your tier controls features and seats, not Cloud worker pricing or access.
Can I switch tiers after launching a DevBox?
Tier is set per-DevBox at launch. To change tiers, stop the existing DevBox and launch a new one with the tier you want. DevBox state and volumes can be migrated via the existing "from DevBox" image flow.
Why are Windows tiers more expensive than Linux tiers?
Each Windows DevBox is a full Windows 11 VM running under KVM/QEMU, not a lightweight Linux DevBox. That means SPLA licensing, virtualisation overhead (~0.5 vCPU and ~0.5 GB per VM), and lower density per machine — roughly half as many Windows VMs per host as Linux DevBoxes. We pass the cost through; Windows is still cheaper than AWS or Azure equivalents.
Does my work survive stopping a DevBox or losing a worker?
Your agent identity does. On cloud workers your agent sessions and config sync off-host continuously — all encrypted with your own per-user key before it leaves the machine. Your next launch hydrates automatically on whichever worker has room, so you pick up where you left off even if the original worker is gone. Your code lives in git and on the machine that made it — we never store your workspace files, on any worker — so commit and push as usual. Every new container restores your history; a running container isn't live-synced while it works. It's on by default and you can opt out (new containers then start fresh) or delete your stored data anytime from settings.
Try it before you pay for it.
7 days of full Pro access. Launch a Cloud worker DevBox in 60 seconds. No card.
Start your free trial →Cloud worker compute is for development workloads and is subject to our Acceptable Use Policy.