CreateOS Sandbox vs Amika
Amika is built for engineering teams that want shared agent workstations, with Claude Code, Codex or OpenCode on their repos and teammates watching or steering, on hardware they already own at no compute charge. CreateOS Sandbox is built for running agent or untrusted code with documented Firecracker isolation, egress allowlists available today and lower hosted compute rates.
Amika's open-source CLI is marked beta, and its homepage still mentions early access while open signup is linked from GitHub.
Pricing at a Glance
CreateOS rates verified 17 October 2026. Amika 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
Amika
- Compute
- $0.1008 /vCPU-hr
- Memory
- $0.0324 /GiB-hr
Amika charges $30/month per active user on Team (Free covers up to 3 users with $50 compute credit), and hosted compute at $0.1008 per vCPU-hour, $0.0324 per GiB-hour and $0.00216 per GiB-hour of storage, as of 17 October 2026.
Where CreateOS Sandbox Fits Better
What CreateOS Sandbox brings to this matchup, with a plain note on where Amika has the edge.
Hosted compute at $0.03616363 per vCPU-hour and $0.01159025 per GiB-hour, against Amika's $0.1008 and $0.0324.
Outbound allowlist rules work today and are enforced on the host; Amika lists its network controls as coming soon.
Isolation is a documented Firecracker micro-VM with its own guest kernel; Amika does not publish its VM technology.
Where Amika is strong
Amika is built around team collaboration on agent work: shared sessions, preview URLs, control from chat tools, and Rigs on hardware or cloud accounts you already pay for, with no compute charge.
Which to Pick
Pick CreateOS Sandbox if
- You are sandboxing untrusted code and need egress rules today.
- Hosted compute cost per vCPU-hour is a deciding factor.
- You want pause with memory and fork through an SDK.
Pick Amika if
- Your team wants shared, watchable agent sessions controlled from Slack or Linear.
- You want to run agent Rigs on your own Kubernetes or cloud accounts without metering.
- You need GPUs on an Enterprise plan.
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 | Amika |
|---|---|---|
| Isolation | Firecracker micro-VM with its own guest kernel | VM per agent; technology not published |
| Pause and resume | Pause saves disk, memory and CPU state; vCPU stops billing, memory and storage still bill | Rigs can be short-lived or persistent; snapshots not published |
| Fork | Yes, fork a paused sandbox into many independent copies | 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; network controls listed as coming soon |
| Inbound access | Closed by default; opt-in public HTTPS URL | Private HTTPS preview URLs and SSH |
| Concurrency | 1 / 5 / 20 / 30 by plan; paused sandboxes count toward the cap | 10 concurrent service-account sandboxes on Free and Team; unlimited on your own machines |
| Billing | Per second: $0.03616363 per vCPU-hour, $0.01159025 per GiB-hour, storage $0.0001584 per GB-hour; no egress fees, 50 GiB bandwidth budget per sandbox | $30/month per active user on Team, plus per-second hosted compute at $0.1008 per vCPU-hour |
| SDKs and interfaces | TypeScript, Go, Python, Rust, C#, Java SDKs (all but TypeScript pre-1.0), CLI, MCP, REST | amika CLI, HTTP API, TypeScript SDK; MCP servers on Team |
| Self-host or BYOC | Enterprise only, onboarded by our team | Core CLI open source (Apache-2.0, beta); Rigs on your own Kubernetes or clouds; control plane closed |
| GPU | No GPU shapes | Enterprise plan only; models not published |
Common Questions
Does Amika charge for agents on my own machines?
No. Amika never meters hours on your own machines; only hosted compute is billed, at $0.1008 per vCPU-hour and $0.0324 per GiB-hour. CreateOS Sandbox runs on managed hosts, with self-hosting reserved for enterprise customers.
Can Amika restrict outbound network traffic?
Amika's product page lists inbound and outbound network controls as coming soon, and its Enterprise plan lists advanced network controls. CreateOS Sandbox already supports allowlist rules by host, IP, CIDR or wildcard, enforced on the host outside the VM.
Where do Amika Rigs run?
On Kubernetes nodes, on your own clouds or machines, or on providers such as E2B, Daytona and Vercel, with Mac support through smolmachines. CreateOS Sandbox runs every sandbox as a Firecracker micro-VM in its eu or us region.
Sources
Checked 17 October 2026.
See CreateOS Sandbox for yourself
Book a demo, or explore the Sandbox and its pricing.