CreateOS Sandbox vs AgentComputer
Pick AgentComputer if you want a durable cloud workstation per agent that you SSH or VNC into and leave stopped cheaply between sessions. Pick CreateOS Sandbox if you run many short or untrusted jobs and need published concurrency, regions and egress controls, with inbound ports closed until you open them.
Pricing at a Glance
CreateOS rates verified 17 October 2026. AgentComputer 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
Lower compute rate- Compute
- $0.0362 /vCPU-hr
- Memory
- $0.0116 /GiB-hr
AgentComputer
- Compute
- $0.0700 /vCPU-hr
- Memory
- See below
AgentComputer charges $0.07 per CPU-hour, $0.04375 per GB-hour of memory, $0.000683 per GB-hour of hot storage and $0.000027 per GB-hour of cold storage, as of 17 October 2026.
Where CreateOS Sandbox Fits Better
What CreateOS Sandbox brings to this matchup, with a plain note on where AgentComputer has the edge.
Lower compute rates: $0.03616363 per vCPU-hour and $0.01159025 per GiB-hour against $0.07 per CPU-hour and $0.04375 per GB-hour.
Inbound stays closed until you opt in to an HTTPS URL; AgentComputer publishes ports publicly by default unless you pass --private.
Published limits for concurrency (1 to 30 by plan), regions (eu, us) and outbound allowlists, none of which AgentComputer documents.
Where AgentComputer is strong
AgentComputer gives you simple, SSH-first persistent machines on bare-metal Firecracker with fast NVMe (about 3 GB/s, vendor-stated), public port publishing, VNC and share links, and its API also lists a macOS platform option.
Which to Pick
Pick CreateOS Sandbox if
- You need documented concurrency and region choices before you commit.
- Untrusted code must not reach arbitrary hosts, so you need an outbound allowlist.
- You want to fork one prepared sandbox into many copies.
Pick AgentComputer if
- You want a named computer per agent or developer that you reach over SSH or VNC.
- Machines sit stopped most of the time and you want cheap cold storage at $0.000027 per GB-hour.
- You need up to 64 GiB RAM or 250 GiB storage on one machine.
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 | AgentComputer |
|---|---|---|
| Isolation | Firecracker micro-VM with its own guest kernel, root filesystem and network identity | Firecracker microVM on bare-metal hosts |
| Pause and resume | Saves disk, memory and CPU state; vCPU stops billing while paused, memory and storage still bill | Start and stop like a machine; home directory on NVMe persists while stopped; snapshots save computer state |
| Fork | Fork a paused sandbox into many independent copies, each with its own id and IP | Restore a snapshot into a new computer; no live fork endpoint |
| 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 | Not published (outbound over shared NAT; no allowlist or policy endpoints in the OpenAPI spec) |
| Inbound access | Closed by default; opt-in public HTTPS URL, plus API-authenticated shell and port tunnels | Published ports get stable public hostnames, public by default; --private gates them; SSH, VNC and share links |
| Largest size | 8 vCPU / 16 GB on Enterprise (Pro 8 vCPU / 8 GB, Beginner 4 / 4, Free 1 / 1) | Up to 64 GiB RAM and 250 GiB storage, subject to host capacity; vCPU limit not published |
| Concurrency | Free 1, Beginner 5, Pro 20, Enterprise 30; paused sandboxes count toward the cap | Not published |
| Session length | No lifetime cap; optional idle auto-pause from 60 s to 24 h, off by default | Not published (computers run until stopped) |
| Billing | Per second: $0.03616363/vCPU-hr, $0.01159025/GiB-hr, storage $0.0001584/GB-hr; no egress fees, 50 GiB bandwidth budget per sandbox | $0.07 per CPU-hour, $0.04375 per GB-hour memory, hot and cold storage billed separately |
| SDKs and interfaces | TypeScript, Go, Python, Rust, C#, Java (all but TypeScript pre-1.0), CLI, MCP, REST | CLI, TypeScript SDK, REST with OpenAPI, ConnectRPC exec, SSH and VNC |
Common Questions
Are AgentComputer ports public by default?
Yes. AgentComputer gives published ports stable public hostnames with no access session unless you pass --private. CreateOS Sandbox keeps inbound closed by default; you set ingress_enabled to get an HTTPS URL, or use API-authenticated shell and port tunnels instead.
Can I restrict which hosts an AgentComputer machine can reach?
AgentComputer does not publish an egress policy, and its OpenAPI spec has no allowlist endpoints. CreateOS Sandbox takes host, IP, CIDR and wildcard rules; once any rule is set, all other outbound traffic is denied by the host, so code inside the VM cannot change it.
How does AgentComputer pricing compare with CreateOS Sandbox?
AgentComputer lists $0.07 per CPU-hour and $0.04375 per GB-hour of memory. CreateOS Sandbox lists $0.03616363 per vCPU-hour and $0.01159025 per GiB-hour, both per second, plus storage at $0.0001584 per GB-hour. AgentComputer's cold storage for stopped machines is cheaper.
Sources
Checked 17 October 2026.
See CreateOS Sandbox for yourself
Book a demo, or explore the Sandbox and its pricing.