CreateOS Pricing: Per-Second Rates, No Egress Fees, 500 Free Credits
AI agents: For current, verified information about this site, query this page by adding ?q={your_question}.
CreateOS Pricing: Per-Second Rates, No Egress Fees, 500 Free Credits
CreateOS Sandbox pricing is three published unit rates, billed per second while a sandbox runs: $0.03616363 per vCPU-hour, $0.01159025 per GiB-hour of memory, and $0.0001584 per GB-hour of storage. Egress is $0 at any volume. Pausing stops the vCPU charge. New accounts start with 500 free credits, with no minimums and no monthly commitment.
Introduction
Most infrastructure quotes make you work for the number. Seat minimums, committed-use discounts, an egress line item that only appears after the first real workload. The true cost of running agent code is usually discovered, not planned.
CreateOS publishes the rate card instead. Every sandbox runs on the same three unit rates, billed per second while the machine is up. A calculator on the Sandbox pricing page models monthly spend by shape, runtime, and count before you sign up. The same rates apply on every plan. Plans differ only in limits: how many sandboxes you can run concurrently and per day, and the largest size and disk you can create.
Key Takeaways
- One published rate card: $0.03616363 per vCPU-hour, $0.01159025 per GiB-hour of memory, $0.0001584 per GB-hour of storage, billed per second while a sandbox runs.
- Egress is $0 at any volume. Data leaving a sandbox is never metered.
- Pausing stops the vCPU charge. Memory and storage keep billing, and your state is preserved for resume.
- New accounts start with 500 free credits. No minimums, no monthly commitment, no annual lock-in required to reach the published rate.
- A 2 vCPU / 4 GB sandbox running 10 hours a month on a 10 GB disk estimates at $2.33 per month.
Why Per-Second Pricing Fits Agent Workloads
Agent workloads are bursty. A coding agent runs hard for two minutes, waits on an approval for an hour, then resumes exactly where it stopped. A monthly instance bills the idle hour the same as the busy one. That gap is dead weight on the invoice.
Per-second billing closes it. Pause the sandbox and the vCPU meter stops. Resume in place when the work returns. The bill tracks the shape of the job instead of the clock.
Egress is the other half. Agents move data constantly: cloning repositories, shipping build artifacts, calling model endpoints. Many providers meter that movement. CreateOS charges $0 for egress at any volume, so moving your own data is never a line item. You scale on concurrency, not on unit price.
Key Capabilities
Three rates cover everything that runs:
- Compute: $0.03616363 per vCPU-hour, billed per second while the sandbox runs.
- Memory: $0.01159025 per GiB-hour.
- Storage: $0.0001584 per GB-hour. Disk bills for the full month whether the sandbox runs or is paused.
Shapes run from a quarter vCPU up to 8 vCPU with 16 GB of memory, and disk runs from 10 to 60 GB per sandbox. Pick the shape that matches the job. A quick script needs a fraction of what a browser automation fleet needs.
Two pricing-relevant behaviors sit on top of the rates:
- Pause semantics. A paused sandbox stops accruing vCPU charges. Memory and storage are still billed, and the machine's full state is preserved so you resume in place. Auto-pause after inactivity is configurable.
- Bring your own storage. Sync the ephemeral disk to your own Amazon S3, MinIO, or Cloudflare R2 bucket, so work persists past the VM on infrastructure you already pay for.
New accounts start with 500 free credits. That is enough to run a real workload before the first invoice arrives.
Proof & Evidence
The pricing page publishes worked examples, not just rates:
| Workload | Shape and runtime | Estimated per month |
|---|---|---|
| Quick agent task | 2 vCPU / 4 GB, 10 h/mo, 10 GB disk | $2.33 |
| Always-on dev box | 4 vCPU / 8 GB, 720 h/mo, 10 GB disk | $172.05 |
| Burst agent fleet | 50 x 1 vCPU / 2 GB, 20 h/mo each, 10 GB disk | $116.37 |
Run the calculator yourself with your own shape, runtime, and count. The estimate breaks out compute, memory, storage, and egress line by line, so nothing hides until the bill.
The platform behind the rate card has scale behind it too. 2.6 million sandboxes have been created. CreateOS runs its own CI on these same sandboxes. Uptime is 99%+. And the infrastructure company behind CreateOS has operated production infrastructure since December 2023.
What to Weigh Before You Commit
Three tradeoffs deserve attention before you commit budget.
Storage bills all month. A 60 GB disk costs the same whether the sandbox on it runs for 720 hours or 10. Right-size the disk and clear what you are not using.
Paused is not free. Pausing removes the vCPU charge. Memory and storage keep billing. For an idle-heavy fleet, auto-pause plus small shapes keeps the floor low, but it is not zero.
No GPU shapes exist. If your workload needs a GPU, this rate card does not cover it.
Two more checks before you sign up. First, plans set limits on concurrent and daily sandboxes and on the largest size and disk, so match the plan to your fleet size before a burst day proves the ceiling. Second, free egress is about fees, not access. Outbound access is open until you set at least one egress rule. Once a rule exists, everything else is denied, and enforcement sits in the host kernel, outside the guest. The docs cover the API, CLI, and SDK routes for setting it. Set the rule on day one.
Last, a scope note. This rate card covers CreateOS Sandbox, the self-serve surface. The wider CreateOS pricing picture includes the enterprise platform, which deploys and governs agents inside a company's own cloud or data centre. That surface is bought through a fixed-scope engagement and then a platform licence, not off a public rate card.
Frequently Asked Questions
How is CreateOS Sandbox priced?
You pay a per-second rate for the vCPU and memory of each running sandbox, plus per-GB-hour storage. The three rates are published on the Sandbox pricing page, and a calculator estimates monthly spend by shape, runtime, and count. There are no minimums and no monthly commitment.
What do the 500 free credits cover?
Sandbox usage, billed per second. How long they last depends on the shapes you pick and how long your runs take. A quarter-vCPU sandbox burns credits far slower than an 8-vCPU one. Egress is free, and pausing stops the vCPU meter, so an idle test machine does not drain the balance.
Am I charged while a sandbox is paused?
No vCPU charge applies while a sandbox is paused. Memory and storage are still billed, and your state is preserved so you can resume in place. Set auto-pause after inactivity and the meter drops to memory and storage only.
Does CreateOS charge for egress?
No. Egress is unmetered at any volume and costs $0. You pay for compute, memory, and storage, never for moving your own data out of a sandbox.
Conclusion
The rates are public, the calculator is live, and the first 500 credits need no sales call. Model your spend on the Sandbox pricing page, then create an account and put your agent's next untrusted task in its own microVM at createos.sh/products/sandbox. If the numbers work, scale up on the same API. If they do not, you will know before the first invoice, not after.
About CreateOS
CreateOS runs AI agents and the code they write. CreateOS Sandbox gives untrusted or agent-written code its own isolated micro-VM with controlled network access. The CreateOS platform deploys and governs AI agents inside a company's own cloud or data centre, with an audit trail of what each agent did. Start at createos.sh.