MicroVM isolation
Per-agent, per-run virtual machines — not shared containers. Spawns in ~120ms, destroyed on exit.
Isolated microVMs, controlled tools and replayable traces — give agents code, browser and shell access without giving up control.
> sandbox.spawn(image="agent-base:2.4", cpu=2, mem=4G)
> tools.allow = [python, browser, fs:/workspace]
> network.egress = allowlist(zirax.ai, pypi.org)
> checkpoint.before("write_back") = armed
# trace sbx-88214 · every syscall recorded · retained 90d
Every ZIRAX sandbox is a disposable microVM: isolated from your network, limited to allowlisted tools, and destroyed the moment the run ends.
Pick an image, resources and lifetime for the run.
Allow only the APIs, files, packages and domains the task needs.
Agent runs with ephemeral storage and snapshot checkpoints.
Approve sensitive actions; replay the full trace at any time.
Per-agent, per-run virtual machines — not shared containers. Spawns in ~120ms, destroyed on exit.
Python, shell, headless browser and file tools pre-installed, versioned and patched by ZIRAX.
Grant exactly the tools, paths, packages and egress domains a task requires — nothing else.
Pause before irreversible actions. Human or rule-based sign-off resumes the run.
Every command, tool call and state change is recorded and replayable for review or compliance.
Thousands of concurrent sandboxes with per-team quotas, budgets and automatic cleanup.
Cold sandbox spawn, ready for tool calls.
Concurrent sandboxes per region, elastic.
Default trace retention; configurable for audit regimes.
Talk to us about sandbox pilots, on-prem images and approval workflows for your team.
Request access