Clean machines for ambitious agents.
Give Codex, Claude Code, OpenCode, Pi and your own agents a real Linux microVM. Keep it, sleep it or throw it away — without letting one workload near another.
- Isolation
- Firecracker microVM
- Default image
- Ubuntu 24.04
- Interfaces
- API · CLI · SDK · MCP
One clean environment for
- Codex
- Claude Code
- OpenCode
- Pi
- Aider
- Hermes
A machine is the primitive.
Zero gives every agent an isolated computer with explicit resources, real persistence and an audit trail. The portal is useful; the API remains the source of truth.
Real Linux, not a shared process
Each sandbox boots its own trusted kernel boundary under Firecracker and Jailer, with dedicated disks, network identity and host-enforced resource limits.
Sleep without starting over
Idle sandboxes can pause and wake transparently before terminal, exec or ingress activity. Persistent workspaces survive stop and start.
Resources are explicit
Choose a preset or set CPU, memory, workspace disk and network rate independently. Billing follows resolved resources, not a vague machine label.
Evidence, not guesswork
Logs, metrics, state transitions and charge explanations line up around the same stable sandbox identity — even after teardown.
Network policy by default
Agent mode permits the internet protocols coding tools need while blocking private networks, the host and neighbouring sandboxes. Air-gap with one command.
One system.
Every surface.
Build interactively in the portal, automate through Python, hand tools to an agent through MCP, or keep it plain with HTTPS. They all use one typed client and one authoritative API.
- Idempotent lifecycle operations
- Typed errors and structured JSON output
- Browser terminal and CLI shell
- Scoped secrets injected only at execution
# One login, then the short path
sandbox login https://api.sandbox.0-uk.com
sandbox doctor
sandbox create dev
sandbox shell dev
# Inspect exactly what happened
sandbox logs dev --level error
sandbox metrics dev
sandbox billing summary --last 7d
from sandbox_control import SandboxClient
with SandboxClient() as client:
result = client.sandboxes.create(
"dev",
project_id="PROJECT_ID",
size="medium",
wait=True,
)
output = client.sandboxes.exec(
result.sandbox.id,
["uname", "-a"],
)
print(output.stdout)
{
"mcpServers": {
"sandbox": {
"command": "sandbox-mcp",
"env": {
"SANDBOX_PROFILE": "default"
}
}
}
}
// Tools include sandbox_create, sandbox_exec,
// sandbox_logs, package_get and billing_explain.
Buy a pool. Use it your way.
One Standard hour is one 2-vCPU, 4-GiB sandbox running for one hour. Package hours are shared across your organisation, not tied to individual machines.
£0/month
- No commitment
- Use any machine shape
- Metered by the second
£10/month
- Everything in PAYG
- Organisation-wide pool
- PAYG after allowance
£39/month
- Everything in Starter
- Built for daily agent work
- PAYG after allowance
£99/month
- Everything in Pro
- For busy teams and fleets
- PAYG after allowance
Storage, retained snapshots and public internet egress are metered separately. Included hours do not roll over.
Designed for code you didn’t write.
Agent workloads are useful precisely because they can act. Zero treats every workload as untrusted and makes the boundary visible.
Review the API contract- MicroVM boundary
- Firecracker, Jailer, namespaces and cgroups isolate each machine from the host and its neighbours.
- Tenant boundary
- Organisation scoping is enforced in the service layer and reinforced with PostgreSQL row-level security.
- Network boundary
- Default-deny forwarding, restricted agent egress and an immediate air-gap mode.
- Secret boundary
- Encrypted at rest, injected only for the selected command and excluded from images, logs and billing records.
Your agent needs a machine.
Give it a clean one.
Email confirmation required. Private beta capacity is limited.