Pricing
Fixed monthly plans, with compute included. All prices in USD.
Every plan includes all five machine sizes, the HTTP API, SSH, browser terminals, and outbound internet. No automatic overage charges.
Builder
$5 / month
For individual projects and testing.
- 250 compute-unit hours/month
- 1,000 starts per month
- Up to 1-hour sessions · 10-minute idle timeout
- Up to 5 containers within 28 concurrent units
- All five sizes · SSH, browser terminal, internet
Pro
$180 / month
For regular development and agent workloads.
- 9,000 compute-unit hours/month
- 10,000 starts per month
- Up to 24-hour sessions · 30-minute idle timeout
- Up to 100 containers within 128 concurrent units
- All five sizes · SSH, browser terminal, internet
Scale
$999 / month
For parallel workloads and sustained compute.
- 50,000 compute-unit hours/month
- 100,000 starts per month
- Up to 72-hour sessions · 60-minute idle timeout
- Up to 500 containers within 640 concurrent units
- All five sizes · SSH, browser terminal, internet
Billed monthly until canceled. Applicable taxes and the total are shown before payment. Google sign-in and an active subscription are required for paid access. Have a free trial promo code? Choose its plan and enter the code after sign-in; a valid code needs no credit card and creates no automatic charges.
What does a compute-unit hour buy?
One unit-hour runs a Lite machine for one hour. Larger sizes use more units. Running and provisioning time, including idle time, counts toward your allowance.
| Machine | vCPU | RAM | Units per hour |
|---|---|---|---|
| Lite | 1/16 | 256 MiB | 1 |
| Small | ½ | 4 GiB | 6 |
| Medium | 1 | 6 GiB | 10 |
| Large | 2 | 8 GiB | 16 |
| XL | 4 | 12 GiB | 28 |
Example: Ten 30-minute Small sessions use 30 unit-hours and ten starts. Builder includes 250 unit-hours for $5/month, equivalent to about 41 hours of Small runtime spread across sessions of up to one hour. Mixed sizes share the same allowance.
Both concurrency limits apply: Builder can run up to five Lite machines, four Small machines, or one XL at once, subject to remaining compute. A start reserves runtime; stopping releases unused runtime after reconciliation.
Full machine and platform limits →Before you subscribe
What happens when I reach a limit?
Starts and compute allowances reset at the beginning of each UTC month, without rollover. Starts are rejected when account limits are reached; running sessions end at their allocated deadline or the month boundary. There are no automatic overage charges or paid top-ups. Failed starts count toward the start allowance. Changing plans does not reset usage.
Can I change plans or cancel?
Manage your subscription from your billing controls. Upgrades require payment through Stripe; downgrades and cancellation take effect at renewal. Lower limits may stop containers. Canceling stops future renewals; see the Terms of Service for billing and refund terms.
Do files persist when a workspace stops?
Container files are ephemeral and lost after stop. Export outputs before the session ends. Keep inputs and backups outside the container. See file transfer and container lifecycle.
Is there an SLA or priority support?
Self-service plans include no uptime SLA, guaranteed support response time, or automatic service credits. Review the trust center and service status, or contact Andrew about your requirements before subscribing.