Pricing
Pay for what your VMs actually use.
A free Hobby tier to get a real feel for it, a metered Pro plan for teams shipping every day, and Enterprise terms for platform-scale usage.
The full breakdown
Every limit and billing dimension, plan by plan.
| Feature | Hobby | Pro | Enterprise |
|---|---|---|---|
| Compute | |||
| Concurrent VMs | 1 | Unlimited* | Custom |
| vCPU / RAM per VM | 2 vCPU / 4 GB | Unlimited* | Custom |
| Included usage credits | None | $20/mo | Custom |
| Overage billing | None | Metered: vCPU-s, RAM-GB-s, storage-GB-h, egress-GB | Custom terms |
| Dedicated hosts | Yes | ||
| Hibernated VM retention | 7 days | 90 days | 90 days |
| Collaboration | |||
| Team members | 1 (no invites) | Unlimited, +$20/mo per seat past the first | Custom |
| Shared projects & env vars | Yes | Yes | |
| Member roles | Yes | Yes | |
| AI / agents | |||
| Claude Code & Codex pre-authenticated | Yes | Yes | Yes |
| MCP servers injected at boot | Yes | Yes | Yes |
| PR previews (counts toward concurrency) | Yes | Yes | Yes |
| Linear ticket VMs | Yes | Yes | Yes |
| Agent signals, notify & sibling requests | Yes | Yes | Yes |
| Support | |||
| Support channel | Community (GitHub) | Priority | Dedicated, custom SLA |
* Pro has no hard concurrent-VM or per-VM vCPU/RAM cap. Usage past included credits is metered, not blocked.
Questions worth answering
What's a usage credit, and how is usage actually metered?
Pro includes $20/mo in usage credits. Once those run out, usage is metered per second or byte across four dimensions: vCPU-seconds, RAM-GB-seconds, storage-GB-hours, and egress-GB. You're billed for exactly what a VM used while it was running, not a flat VM-hour rate.
What happens when a VM suspends or hibernates?
Suspended VMs still hold their spot. Once a VM has been suspended for an hour or more, it hibernates: its disk moves to storage and the VM steps aside completely, so it doesn't count toward your concurrency limit while hibernated. Waking it brings back a fresh VM with that same disk.
Do preview and ticket VMs count toward my concurrency limit?
Yes. Every PR preview and every Linear ticket VM is a real VM and counts toward your plan's concurrent-VM limit like any other. There's no separate preview quota.
How long do hibernated VMs stick around?
Hobby keeps a hibernated VM's disk for 7 days before it's reaped; Pro and Enterprise keep it for 90 days. After that window the disk is deleted for good.
Can an agent run unattended in a VM?
Yes. An agent can signal that it needs your input, mark work as done, and even request a sibling VM of its own to split up work (one level deep, capped at 3 outstanding requests). We audit every one of those actions, and you get a real notification (email, or Slack if you've connected it) when a VM needs you.
Do I need to bring my own GitHub?
Connect your GitHub account once and every VM you create pushes as you, using your own token, never a shared bot account. PR previews and Linear ticket VMs (created by a webhook, not by you directly) use the GitHub App's installation token instead, since there's no human in that loop.
Is my code safe inside a VM?
Yes. Every VM is its own isolated machine, not a shared container: its own private network, its own firewall, and secrets encrypted with AES-256-GCM. Every connection between our systems and your VM is encrypted, and inbound traffic to every workspace is locked to Cloudflare's network.
Can I change plans or cancel any time?
Yes. You manage plans, billing, and team seats from your account's billing portal at any time. There's no lock-in and no sales call required to start, upgrade, or cancel.
Get started
Your next VM is one command away.
Connect a repo, and get a full-stack dev environment with Claude Code and Codex already running, before your coffee's done.