CreateOS Sandbox vs Orkestr
Pick orkestr if your agent code, files and snapshots must stay on EU-owned hardware run by an EU company with no US parent. Pick CreateOS Sandbox if you need sandboxes larger than 4 vCPU / 8 GB, firm per-second prices in USD, fork, or a US region as well as the EU.
orkestr labels its sandboxes beta and says published rates will land once it has metered real workloads.
Pricing at a Glance
CreateOS rates verified 17 October 2026. orkestr 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
orkestr
orkestr meters per second while a sandbox is alive at approximate rates from about EUR 0.06 per hour (1 vCPU / 1 GB) to about EUR 0.30 per hour (4 vCPU / 8 GB), with firm rates not yet published, as of 17 October 2026.
Where CreateOS Sandbox Fits Better
What CreateOS Sandbox brings to this matchup, with a plain note on where orkestr has the edge.
Sizes up to 8 vCPU / 16 GB on Enterprise and 8 vCPU / 8 GB on Pro, against orkestr's largest 4 vCPU / 8 GB.
Firm per-second rates in USD; orkestr quotes approximate EUR figures and says published rates are still to come.
Fork a paused sandbox into many copies; orkestr documents snapshot restore but no fork.
A us region alongside eu, where orkestr runs in the EU only.
Where orkestr is strong
orkestr offers data residency without caveats: EU-owned hardware and an EU operator with no US parent, a dedicated VM per sandbox, egress off by default with an HTTPS allowlist mode, and live limits exposed through an API.
Which to Pick
Pick CreateOS Sandbox if
- Workloads need more than 4 vCPU / 8 GB.
- Finance needs a firm published rate before approval.
- You serve users in the US as well as the EU.
Pick orkestr if
- Your data must stay on EU hardware run by an EU legal entity with no US parent.
- You want outbound traffic off until you allow it.
- You want to pick Germany, Finland or France per sandbox.
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 | orkestr |
|---|---|---|
| Isolation | Firecracker micro-VM with its own guest kernel, root filesystem and network identity | Dedicated hardware-virtualised VM per sandbox with its own kernel and rootfs (hypervisor not named) |
| Pause and resume | Saves disk, memory and CPU state; vCPU stops billing while paused, memory and storage still bill | Pause between turns with memory; snapshot retention 7 days Free, 30 days pay-as-you-go |
| 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 | Off; restricted HTTPS hostname allowlist, or open on paid tiers |
| Inbound access | Closed by default; opt-in public HTTPS URL, plus API-authenticated shell and port tunnels | Public preview URL per HTTP port, paid tiers only |
| Largest size | 8 vCPU / 16 GB on Enterprise (Pro 8 vCPU / 8 GB, Beginner 4 / 4, Free 1 / 1) | 4 vCPU / 8 GB on paid tiers; Free is 1 vCPU / 1 GB |
| Concurrency | Free 1, Beginner 5, Pro 20, Enterprise 30; paused sandboxes count toward the cap | Concurrent RAM budget: Free 2 GB, pay-as-you-go 32 GB, Enterprise 128 GB; paused do not count |
| Session length | No lifetime cap; optional idle auto-pause from 60 s to 24 h, off by default | Countdown 10 s to 24 h per call, extendable; Free caps continuous running at 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 second while alive; approximate EUR 0.06 to 0.30 per hour by size |
| Self-host or BYOC | Enterprise only, onboarded by our team; not open source | No (managed only) |
Common Questions
Where does orkestr host sandboxes?
In the EU only: Falkenstein in Germany, Helsinki in Finland and Roubaix in France, on orkestr's own machines, selectable per sandbox. CreateOS Sandbox runs in two managed regions, eu and us, chosen with the region field at create time.
Is outbound traffic allowed from an orkestr sandbox?
Not by default; orkestr starts with egress off, offers a restricted HTTPS hostname allowlist, and allows open egress on paid tiers with verified billing. CreateOS Sandbox starts open, then denies everything not on your list once you add any rule.
What is the largest orkestr sandbox?
Large: 4 vCPU and 8 GB RAM on paid tiers, with Free limited to 1 vCPU / 1 GB. CreateOS Sandbox goes to 8 vCPU / 8 GB on Pro and 8 vCPU / 16 GB on Enterprise.
Sources
Checked 17 October 2026.
See CreateOS Sandbox for yourself
Book a demo, or explore the Sandbox and its pricing.