CreateOS Sandbox vs Isorun
Isorun and CreateOS Sandbox overlap closely: microVMs with their own kernel, memory-preserving pause, fork and host-enforced egress rules. Pick Isorun for its out-of-guest credential proxy, ready-made egress profiles, $0.025 per vCPU-hour rate and unbilled hibernation. Pick CreateOS if you need SDKs beyond TypeScript or a compliance attestation you can show today.
Isorun labels the service public beta; it launched publicly on 16 June 2026.
Pricing at a Glance
CreateOS rates verified 17 October 2026. Isorun 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
Isorun
- Compute
- $0.0250 /vCPU-hr
- Memory
- $0.0150 /GiB-hr
Isorun charges per second at $0.025 per vCPU-hour plus $0.015 per GiB-hour of RAM (1 vCPU + 1 GiB = $0.040/hour), with egress and platform fees included and no runtime billing for hibernated sandboxes, as of 17 October 2026.
Where CreateOS Sandbox Fits Better
What CreateOS Sandbox brings to this matchup, with a plain note on where Isorun has the edge.
SDKs in Python, Go, Rust, C# and Java as well as TypeScript (non-TypeScript pre-1.0). Isorun publishes a TypeScript SDK only.
Compliance in hand: CreateOS is SOC 2 Type II and ISO 27001 certified, with reports available under NDA. Isorun lists SOC 2 Type II as coming soon.
Idle handling keeps state: optional auto-pause saves the sandbox, and nothing is destroyed for being idle. Isorun's idle timer destroys a sandbox after 300 seconds by default.
Lower memory rate: $0.01159025 per GiB-hour against Isorun's $0.015.
Where Isorun is strong
Isorun treats agent security as a product feature: host-enforced egress allowlists with named profiles such as claude-code and openai, a credential proxy outside the guest so API keys never enter the VM, per-endpoint method and path rules, and a tamper-evident audit log, alongside fork and hibernate.
Which to Pick
Pick CreateOS Sandbox if
- Your agent backend is Python, Go, Rust, C# or Java.
- Your buyer's security review needs SOC 2 Type II or ISO 27001 now.
- You want idle sandboxes paused rather than destroyed by default.
Pick Isorun if
- Agent code calls third-party APIs and keys must never enter the VM.
- You work in TypeScript and want the lower vCPU rate of the two.
- You want hibernated sandboxes to cost nothing in runtime.
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 | Isorun |
|---|---|---|
| Isolation | Firecracker micro-VM with its own guest kernel | MicroVM with its own guest kernel (KVM) |
| Pause and resume | Saves disk, memory and CPU state; vCPU billing stops while paused, memory and storage still bill | Hibernate keeps filesystem, memory and processes; outbound TCP resets on resume |
| Fork | Fork a paused sandbox into many independent copies | fork(n) clones a running sandbox, memory included, into N children |
| 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 by default; host-enforced allow/deny by CIDR, IP, hostname (SNI) or wildcard; named profiles |
| Inbound access | Closed by default; opt-in HTTPS URL | sandbox.url(port) HTTPS URL; docs conflict on whether it needs the API key |
| Largest size | 8 vCPU / 16 GB on Enterprise; 8 / 8 on Pro, 4 / 4 on Beginner, 1 / 1 on Free | Shapes up to 8 vCPU + 16 GiB listed; hard maximum not published |
| Concurrency | 1 / 5 / 20 / 30 by plan (Free to Enterprise); paused sandboxes count | Account limits apply (429 when hit); numbers not published |
| Session length | No cap; optional idle auto-pause from 60 s to 24 h, off by default | Idle auto-destroy after 300 s by default, 0 disables; no maximum lifetime published |
| Billing | Per second: $0.03616363 per vCPU-hour, $0.01159025 per GiB-hour, storage $0.0001584 per GB-hour; no egress fees (50 GiB bandwidth budget per sandbox) | Per second: $0.025 per vCPU-hour, $0.015 per GiB-hour; egress included |
| SDKs and interfaces | TypeScript, Go, Python, Rust, C#, Java (all but TypeScript pre-1.0), CLI, MCP, REST | TypeScript SDK (Node 20+), REST API, MCP server, WebSocket terminal |
Common Questions
Is Isorun's egress default-deny?
Its network-filtering doc says the default policy is unrestricted, though the homepage says default-deny. Treat it as open until you apply a rule or profile. CreateOS behaves the same way: open with no rules, and deny-by-default once any rule exists.
Can Isorun fork a running sandbox?
Yes. sandbox.fork(n) clones a running sandbox into N children that inherit filesystem and memory, while active outbound sessions reset. CreateOS requires the source to be paused, then forks its snapshot into independent sandboxes that each get their own id and IP.
Which costs less to run, Isorun or CreateOS?
On vCPU, Isorun: $0.025 per vCPU-hour against $0.03616363. On memory, CreateOS: $0.01159025 per GiB-hour against $0.015. Isorun also does not bill runtime for hibernated sandboxes, while CreateOS keeps billing memory and storage for paused ones.
Is Isorun still in beta?
Yes. Isorun labels itself public beta, launched publicly on 16 June 2026, and lists SOC 2 Type II as coming soon. CreateOS is SOC 2 Type II and ISO 27001 certified, with reports available under NDA.
Sources
Checked 17 October 2026.
See CreateOS Sandbox for yourself
Book a demo, or explore the Sandbox and its pricing.