CreateOS Sandbox vs Gcore
Choose Gcore when bandwidth is the cost that hurts: VM egress is free and unlimited, and VMs and GPUs sit in 30+ regions near users. Choose CreateOS Sandbox when you need per-task machines for agent code with pause, fork and an outbound allowlist. Gcore covers far more locations; CreateOS runs in two, eu and us.
Pricing at a Glance
CreateOS rates verified 17 October 2026. Gcore pricing as published on 26 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
Gcore
Standard VMs start from EUR 8.93 per month on Gcore's plan cards (an FAQ on the same page gives a higher starting price), and an 8x H100 SXM server lists at EUR 21.82 per hour, excluding VAT and billed per minute, as of 26 October 2026.
Where CreateOS Sandbox Fits Better
What CreateOS Sandbox brings to this matchup, with a plain note on where Gcore has the edge.
Published per-resource rates, $0.03616363 per vCPU-hour and $0.01159025 per GiB-hour, billed per second; Gcore does not list per-vCPU rates on static pages.
Pause with disk, memory and CPU state, then fork; the Gcore pages checked mention neither snapshots nor fork.
Outbound allowlists by hostname, wildcard or CIDR, enforced on the host outside the VM.
Where Gcore is strong
Free, unlimited VM egress and a wide edge footprint of 30+ regions, which suits bandwidth-heavy workloads that would pay heavily for egress elsewhere.
Which to Pick
Pick CreateOS Sandbox if
- You run agent code that should start clean and be destroyed after
- You want to snapshot memory and fork for parallel runs
- You want per-vCPU and per-GiB rates you can calculate against
Pick Gcore if
- Your servers push a lot of data out and you want VM egress free
- You need VMs or H100 GPUs close to users in many regions
- You already use Gcore CDN or edge services
Head-to-Head Comparison
Every dimension side by side, checked on 26 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 | Gcore |
|---|---|---|
| Isolation | Firecracker micro-VM with its own guest kernel | Full VM (hypervisor not published) |
| Create and destroy by API | Yes: REST API, CLI, SDKs for TypeScript, Go, Python, Rust, C# and Java (all but TypeScript pre-1.0), and an MCP server with create, exec and destroy tools | REST API, Terraform provider and control panel; SDK languages not captured; MCP not published |
| Memory snapshot (pause and resume) | Yes: pause saves disk, memory and CPU state; vCPU stops billing while paused, memory and storage still bill | Not mentioned in the pages checked; volumes persist and a stopped VM incurs no instance charge |
| Fork | Yes: fork a paused sandbox into new, independent sandboxes | Not published |
| Outbound network controls | 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; VM traffic in and out is free and unlimited |
| Billing granularity | Per second while running, no minimums: $0.03616363 per vCPU-hour, $0.01159025 per GiB-hour | Per minute (marketing pages); only active instances billed |
| Largest size | 8 vCPU / 16 GB on Enterprise (8 / 8 Pro, 4 / 4 Beginner, 1 / 1 Free) | Standard and network-optimised G3A: up to 96 vCPU, 490 GB (Linux) |
| GPU | No GPU shapes | Yes: H100 and others on GPU cloud; VM GPU flavors up to 32 vCPU / 128 GB |
Common Questions
Does Gcore charge for VM egress?
No. Gcore states that ingress and egress for VMs are free and unlimited, while bare-metal egress is charged. CreateOS also has no egress fees, but each sandbox has a 50 GiB outbound budget by default, and recharging beyond it uses account credit at a rate not published.
Can Gcore VMs be paused and resumed with memory?
The Gcore pages reviewed mention no snapshot or memory pause; a stopped VM keeps its volumes and stops instance charges. CreateOS pause stores disk, memory and CPU state, stops vCPU billing, and keeps billing memory and storage while paused.
Is Gcore a better fit than CreateOS for GPU agents?
Yes, if the agent needs a GPU. Gcore sells an 8x H100 SXM server at EUR 2.73 per GPU-hour and VM GPU flavors up to 32 vCPU / 128 GB. CreateOS Sandbox has no GPU shapes, so GPU work has to run elsewhere.
Sources
Checked 26 October 2026.
See CreateOS Sandbox for yourself
Book a demo, or explore the Sandbox and its pricing.