CreateOS Sandbox vs Runtime
Pick Runtime if you are in or near US East and want low per-unit prices, memory-preserving pause, live forks and SSO, SCIM and audit log at no extra cost. Pick CreateOS Sandbox if you need an EU region, a vendor that holds its own SOC 2 Type II and ISO 27001 certification, or SDKs in Rust or C#.
Pricing at a Glance
CreateOS rates verified 17 October 2026. Runtime pricing as published on 17 October 2026. Rates billed per GB rather than per GiB, or as bundled sizes, are quoted as published rather than converted.
CreateOS Sandbox
- Compute
- $0.0362 /vCPU-hr
- Memory
- $0.0116 /GiB-hr
Runtime
- Compute
- $0.0250 /vCPU-hr
- Memory
- $0.0075 /GiB-hr
Runtime charges $0.025 per active vCPU-hour and $0.0075 per reserved GiB-hour of memory with no plan fee, paused sandboxes and snapshots at $0.08 per GB per 30-day month, and egress at $0.02 per GB after 100 GiB per month, as of 17 October 2026.
Where CreateOS Sandbox Fits Better
What CreateOS Sandbox brings to this matchup, with a plain note on where Runtime has the edge.
Two regions, eu and us; Runtime runs in Virginia only.
Runtime cites its data centre's certifications rather than its own. CreateOS is SOC 2 Type II and ISO 27001 certified, with reports available under NDA.
SDKs for Rust and C# (pre-1.0), alongside TypeScript, Go, Python and Java.
Where Runtime is strong
Runtime publishes low per-unit prices, $0.025 per active vCPU-hour, with memory-preserving pause, live forks of running sandboxes and SSO, SCIM and audit log included free. Compatibility imports let E2B, Daytona, Vercel Sandbox or Blaxel code switch by changing one import.
Which to Pick
Pick CreateOS Sandbox if
- Your users or data must stay in the EU.
- Your vendor review needs the provider's own SOC 2 Type II report.
- Your stack uses Rust or C#.
Pick Runtime if
- You run in US East and want $0.025 per active vCPU-hour.
- You are migrating from E2B, Daytona, Vercel Sandbox or Blaxel and want a one-import switch.
- You need to fork a running sandbox with its processes.
Head-to-Head Comparison
Every dimension side by side, checked on 17 October 2026 against each vendor's own docs and pricing pages. "Not published" means we could not find it on the vendor's pages, not that the feature is missing.
| Dimension | CreateOS Sandbox | Runtime |
|---|---|---|
| Isolation | Firecracker micro-VM with its own guest kernel | Firecracker micro-VM with its own kernel, on dedicated servers (vendor-stated) |
| Pause and resume | Saves disk, memory and CPU state; vCPU billing stops, memory and storage still bill | Keeps memory and processes; idle auto-pause after 60 s by default |
| Fork | Forks a paused sandbox into many independent copies | 1 to 10 running copies with files, memory and processes |
| Outbound network default | Open with no rules; deny-by-default once any host, IP, CIDR or wildcard rule exists, enforced on the host outside the VM | Open for paid sandboxes with a kept top-up; free usage limited to ports 80 and 443; allow and deny lists |
| Inbound access | Closed by default; opt-in HTTPS URL | Private preview URLs with a rotatable token; public TCP ports with a kept top-up |
| Largest size | 8 vCPU / 16 GB on Enterprise; 8 vCPU / 8 GB on Pro | 16 vCPU / 64 GiB / 400 GiB paid; 2 vCPU / 4 GiB on free usage |
| Concurrency | 1 / 5 / 20 / 30 by plan (Free to Enterprise); paused sandboxes count | 4 on free usage; 100 paid; 200 with auto top-up |
| Session length | No cap; optional idle auto-pause from 60 s to 24 h, off by default | No fixed maximum published |
| Billing | Per second: $0.03616363/vCPU-hr, $0.01159025/GiB-hr, $0.0001584/GB-hr storage; no egress fees, 50 GiB bandwidth budget per sandbox | $0.025 per active vCPU-hour, $0.0075 per reserved GiB-hour; egress $0.02/GB after 100 GiB per month |
| SDKs and interfaces | TypeScript, Go, Python, Rust, C#, Java (all but TypeScript pre-1.0), CLI, MCP, REST | JavaScript, Python, Go, Ruby and Java SDKs, CLI, MCP, REST |
Common Questions
Where does Runtime run its sandboxes?
In one region, Virginia in the United States, on dedicated servers. CreateOS Sandbox offers two managed regions, eu and us, chosen with a field at create time, which matters if your users or data need to stay in Europe.
Does Runtime hold its own SOC 2 report?
Runtime states that its data centre holds SOC 1, 2 and 3 Type 2 and ISO 27001, and that its subprocessors are certified; it does not state a SOC 2 report for Runtime itself. CreateOS is SOC 2 Type II and ISO 27001 certified, with reports available under NDA.
Can existing E2B code run on Runtime?
Runtime says yes: it ships compatibility imports for E2B, Daytona, Vercel Sandbox, Blaxel and Morph, so code can switch by changing one import. CreateOS Sandbox has its own SDKs and does not claim drop-in compatibility with other sandbox SDKs.
How do Runtime prices compare with CreateOS Sandbox?
Runtime lists $0.025 per active vCPU-hour and $0.0075 per reserved GiB-hour of memory, with a 50-millicore idle floor and no plan fee. CreateOS lists $0.03616363 per vCPU-hour and $0.01159025 per GiB-hour, per second while running. On published rates Runtime is cheaper.
Sources
Checked 17 October 2026.
See CreateOS Sandbox for yourself
Book a demo, or explore the Sandbox and its pricing.