CreateOS Sandbox vs Kamatera
Kamatera is a good pick for custom-sized, long-running servers, including Windows, in a specific country from a long list of data centers. CreateOS Sandbox is the pick for short-lived agent machines you create from code and discard, with pause, fork and outbound allowlists. Kamatera configures servers; CreateOS runs sandboxes.
Pricing at a Glance
CreateOS rates verified 17 October 2026. Kamatera 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
Kamatera
Packages start at $4 per month (1 vCPU, 1 GB, 20 GB NVMe, 5 TB traffic), and a configurator example of 1 core and 512 MB shows $10 per month or $0.014 per hour, with extra traffic at $0.01 per GB, as of 17 October 2026.
Where CreateOS Sandbox Fits Better
What CreateOS Sandbox brings to this matchup, with a plain note on where Kamatera has the edge.
Create and destroy per task from an SDK, where Kamatera servers go through a VM-provisioning flow.
Pause that keeps memory, plus fork from the paused state, which Kamatera does not publish.
Outbound rules by host, IP or CIDR that code inside the sandbox cannot change.
Where Kamatera is strong
Very flexible per-component configuration, with CPU class, up to 104 vCPUs, RAM and disk chosen separately, 5 TB of included traffic and many data-center locations.
Which to Pick
Pick CreateOS Sandbox if
- Each agent run should get its own disposable machine
- You want per-second billing rather than hourly or monthly
- You want to pause and fork environments between runs
Pick Kamatera if
- You need a server in a specific country, such as Israel, Romania or Japan
- You want to pick CPU class, up to 104 cores, RAM and disk separately
- You need long-running Windows servers
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 | Kamatera |
|---|---|---|
| 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 | API and CLI (not re-verified) |
| Memory snapshot (pause and resume) | Yes: pause saves disk, memory and CPU state; vCPU stops billing while paused, memory and storage still bill | Not published; disk persists, optional daily backup |
| 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; firewall sold as a product |
| Billing granularity | Per second while running, no minimums: $0.03616363 per vCPU-hour, $0.01159025 per GiB-hour | Hourly (billed by the minute) or monthly |
| Largest size | 8 vCPU / 16 GB on Enterprise (8 / 8 Pro, 4 / 4 Beginner, 1 / 1 Free) | Up to 104 vCPUs; RAM to at least 128 GB in the configurator |
| GPU | No GPU shapes | Not published on the pricing page |
Common Questions
Does Kamatera offer a free trial?
Yes, a 30-day free trial worth up to $100 on one server. CreateOS Free needs no card and gives 500 credits, one concurrent 1 vCPU / 1 GB sandbox, and 10 sandbox creates per rolling 24 hours.
How does Kamatera bill network traffic?
Listed plans include 5 TB of traffic, extra traffic is $0.01 per GB, and if inbound exceeds 33% of total traffic, all traffic is billed. CreateOS charges no egress fees and gives each sandbox a 50 GiB outbound budget by default.
Can Kamatera servers be created per agent task?
They can be created through Kamatera's API, but servers follow a configure-and-deploy flow (Kamatera states 60 seconds to deploy) and no fork or memory snapshot is published. CreateOS sandboxes are created, paused, forked and destroyed from SDK, CLI or REST calls.
See CreateOS Sandbox for yourself
Book a demo, or explore the Sandbox and its pricing.