CreateOS Sandbox vs Ellipsis
Pick Ellipsis if you want Claude Code or Codex running against your repos as a governed team service, with budgets, scoped GitHub tokens and an audit trail. Pick CreateOS Sandbox if your own product runs agent-generated code and needs a sandbox API for exec, files and ports, sessions past one hour, and published isolation and egress details.
Pricing at a Glance
CreateOS rates verified 17 October 2026. Ellipsis 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
Ellipsis
- Compute
- $0.1419 /vCPU-hr
- Memory
- $0.0242 /GiB-hr
Ellipsis bills organization compute at $0.141912 per CPU core-hour and $0.024192 per GiB-hour while a sandbox runs, adds a 10% platform fee on credit purchases, and makes compute free on personal accounts, as of 17 October 2026.
Where CreateOS Sandbox Fits Better
What CreateOS Sandbox brings to this matchup, with a plain note on where Ellipsis has the edge.
A sandbox-level API: exec, files, managed processes, ports, pause and fork over REST and six SDKs, where Ellipsis exposes sessions rather than the sandbox.
No session cap, against an Ellipsis compute timeout of at most 1 hour.
Lower organization rates: $0.03616363 per vCPU-hour and $0.01159025 per GiB-hour against $0.141912 and $0.024192.
CreateOS is SOC 2 Type II and ISO 27001 certified, with reports available under NDA. Ellipsis states SOC 2 Type I, with Type II in progress.
Where Ellipsis is strong
Ellipsis turns a coding agent into a governed team service: agents defined in version-controlled YAML, per-session GitHub tokens that expire with the sandbox, spend limits per session and per developer, cached dependency builds and a full audit trail.
Which to Pick
Pick CreateOS Sandbox if
- You are running arbitrary agent-generated code from your own product.
- Sessions run longer than one hour.
- Your review needs the isolation technology and egress policy written down.
Pick Ellipsis if
- You want to run Claude Code or Codex in the cloud from GitHub, Slack, Linear or Sentry without building infrastructure.
- Per-session spend limits and expiring GitHub tokens are the controls you need.
- Developers will use personal accounts, where Ellipsis compute is free.
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 | Ellipsis |
|---|---|---|
| Isolation | Firecracker micro-VM with its own guest kernel, root filesystem and network identity | Not published (each session runs on its own isolated cloud machine; technology not named) |
| Pause and resume | Saves disk, memory and CPU state; vCPU stops billing while paused, memory and storage still bill | A resumed session keeps its workspace including uncommitted changes; setup-hook results are cached |
| Fork | Fork a paused sandbox into many independent copies, each with its own id and IP | Not published |
| 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 |
| Inbound access | Closed by default; opt-in public HTTPS URL, plus API-authenticated shell and port tunnels | Not published |
| Largest size | 8 vCPU / 16 GB on Enterprise (Pro 8 vCPU / 8 GB, Beginner 4 / 4, Free 1 / 1) | 32 vCPU / 64 GB memory per environment |
| Session length | No lifetime cap; optional idle auto-pause from 60 s to 24 h, off by default | compute.timeout 60 seconds to 1 hour, default 1 hour |
| 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 | Per allocated core-hour ($0.141912) and GiB-hour ($0.024192) while running; free on personal accounts |
| SDKs and interfaces | TypeScript, Go, Python, Rust, C#, Java (all but TypeScript pre-1.0), CLI, MCP, REST | Python and TypeScript session SDKs, CLI, REST, webhooks, GitHub App, Slack and Linear |
Common Questions
Can I run my own agent's code in an Ellipsis sandbox?
Not directly. Ellipsis runs Claude Code or Codex sessions you define in YAML and has no sandbox-level API for exec, files, ports or snapshots. CreateOS Sandbox is that API: your agent calls create, exec, file transfer and pause from TypeScript, Go, Python, Rust, C#, Java or REST.
What is the longest an Ellipsis session can run?
Ellipsis sets compute.timeout between 60 seconds and 1 hour, defaulting to 1 hour; its docs do not say whether that is idle or wall-clock time. CreateOS Sandbox has no lifetime cap, and idle auto-pause is off unless you set it.
Which compliance reports do Ellipsis and CreateOS hold?
Ellipsis states it is SOC 2 Type I certified with Type II in progress. CreateOS is SOC 2 Type II and ISO 27001 certified, with reports available under NDA. Ellipsis also lets you set a session data TTL from 0 hours to 1 year.
Sources
Checked 17 October 2026.
See CreateOS Sandbox for yourself
Book a demo, or explore the Sandbox and its pricing.