CreateOS Sandbox vs Kedge
Pick Kedge if you want to run snippets and then publish what you built to a global URL from the same SSH session, across ten regions. Pick CreateOS Sandbox if your agent sandboxes must live longer than an hour, keep memory across pause, fork into copies, or accept inbound HTTPS traffic.
Kedge is in public preview, and its published rates are labelled estimates for a future paid service.
Pricing at a Glance
CreateOS rates verified 17 October 2026. Kedge 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
Kedge
- Compute
- $0.0205 /vCPU-hr
- Memory
- $0.0068 /GiB-hr
Kedge meters actual use per second at an estimated $0.0205 per vCPU-hour, $0.0068 per GiB-hour, $0.05 per GiB-month of storage and $0.01 per GiB of egress, with $5 of free usage per month, as of 17 October 2026.
Where CreateOS Sandbox Fits Better
What CreateOS Sandbox brings to this matchup, with a plain note on where Kedge has the edge.
Sandboxes live until you destroy them; a held Kedge sandbox expires 5 minutes after its last command or at a 1-hour deadline.
Pause keeps disk and memory and fork clones the state; Kedge sandboxes have no snapshots or fork and lose their disk at expiry.
Opt-in HTTPS ingress per sandbox; Kedge sandboxes have no ingress.
Outbound allowlists by host, IP or CIDR; Kedge offers on or off (-no-network) with no allowlist documented.
Where Kedge is strong
Kedge offers sub-millisecond warm sandbox starts on VMs with their own kernel (vendor-stated), bills on active CPU and touched memory pages rather than allocation, and runs in ten regions including South America, India and Africa, with deploy and database built in.
Which to Pick
Pick CreateOS Sandbox if
- A sandbox must stay up for hours or days.
- Your agent needs to resume with processes in memory or fork from a prepared state.
- The sandbox has to serve a dev server or webhook over HTTPS.
Pick Kedge if
- You run short snippets and want billing on consumed CPU and memory, not allocation.
- You need regions in South America, India, Africa or Asia-Pacific.
- You want to publish an app with replicated SQLite from the same tool.
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 | Kedge |
|---|---|---|
| Isolation | Firecracker micro-VM with its own guest kernel, root filesystem and network identity | VM with its own Linux kernel for every app instance, handler, sandbox and CI runner (hypervisor not named) |
| Pause and resume | Saves disk, memory and CPU state; vCPU stops billing while paused, memory and storage still bill | Sandboxes: none; the disk is gone at expiry. Workspaces persist their filesystem and sessions |
| Fork | Fork a paused sandbox into many independent copies, each with its own id and IP | No user-facing sandbox fork |
| 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; -no-network leaves only loopback; no allowlist documented |
| Inbound access | Closed by default; opt-in public HTTPS URL, plus API-authenticated shell and port tunnels | Sandboxes have no ingress; apps publish through Kedge's HTTPS edge |
| Concurrency | Free 1, Beginner 5, Pro 20, Enterprise 30; paused sandboxes count toward the cap | Per-account cap on held sandboxes, value not published |
| Session length | No lifetime cap; optional idle auto-pause from 60 s to 24 h, off by default | Held sandbox expires 5 minutes after its last command or at a ttl_seconds deadline up to 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 on consumed CPU and memory pages: est. $0.0205/vCPU-hr, $0.0068/GiB-hr, $0.01/GiB egress |
| SDKs and interfaces | TypeScript, Go, Python, Rust, C#, Java (all but TypeScript pre-1.0), CLI, MCP, REST | SSH, CLI, Git push, REST with OpenAPI; no language SDKs listed |
Common Questions
How long does a Kedge sandbox last?
Briefly. A held Kedge sandbox expires 5 minutes after its last command, or at a ttl_seconds deadline of up to 1 hour, and one command is capped at 10 minutes. CreateOS Sandbox has no lifetime cap and pauses on idle only if you set auto_pause_after_seconds.
Can a Kedge sandbox keep state between runs?
Kedge sandboxes cannot; the VM lives in host memory and its disk is gone at expiry. Kedge workspaces, a separate product, do persist. A CreateOS Sandbox pause saves disk, memory and CPU state to durable storage, and you resume or fork from it later.
Why are Kedge's rates lower than CreateOS Sandbox's?
Partly because Kedge bills a different thing: consumed CPU time and touched memory pages, while CreateOS bills allocated vCPU and memory per second. Kedge's figures are also preview estimates. Compare a real workload on both before deciding on price.
Sources
Checked 17 October 2026.
See CreateOS Sandbox for yourself
Book a demo, or explore the Sandbox and its pricing.