Give your agent a cloud VM with a browser and persistent files. Scale to thousands of Sandboxes, then deploy on Lizard - without managing the infrastructure.
curl -fsSL https://lizard.build/install.sh | bash 
Built for agents. Ready for your product.
A cloud workspace for your agent to run code, work with files, and build apps.
Attach Persistent Volumes to carry your workspace files into the next sandbox.
Deploy persistent web apps and databases on Lizard.
An integrated desktop and browser to open apps and inspect the result.
Build your product on top of Lizard with Lizard SDK.
Full transparency with logs and metrics. Follow your sandbox’s output and resource usage.
Lizard Sandboxes · Pricing
Choose your sandbox size and runtime.
Estimate compute costs before subscription fees and credits.
Pro · $19/month, with $19 in credits
Billed per second while running.
Pause or stop between sessions; running idle time is billed.
$5 trial credits · Card required
Then $19/month unless cancelled.
Estimated sandbox compute
$0.71/ month
1 sandbox × 44 hours × $0.0162 / hour
Compute estimates only, before subscription fees, credits, storage and taxes. Vercel assumes 10% active CPU; Modal reserves the full shown CPU and RAM. Resource availability and session limits differ.
The hourly rate includes the CPU, RAM and local disk shown above. A running sandbox is billed even while idle; pausing it stops its compute charge. Persistent Volumes continue to accrue storage charges.
This estimate covers sandbox compute only. Pro subscription fees, monthly credits and trial credits are not included.
Trial accounts can run up to 5 Sandboxes at once; Pro supports up to 100. Higher limits need an agreement. Restored or legacy resources may use a different billing model.
Full pricing & billing details ↗Lowest median. Lowest average. Measured against E2B, Daytona, and Modal.
Lowest median time
| Provider | Median | Average | p90 | p95 | p99 | Maximum |
|---|---|---|---|---|---|---|
| Lizard | 238 ms — Lowest time | 293 ms — Lowest time | 337 ms — Lowest time | 453 ms — Lowest time | 845 ms | 6,217 ms |
| E2B | 270 ms | 319 ms | 462 ms | 569 ms | 777 ms — Lowest time | 1,238 ms — Lowest time |
| Daytona | 796 ms | 1,108 ms | 1,579 ms | 2,537 ms | 6,202 ms | 12,302 ms |
| Modal | 865 ms | 961 ms | 1,346 ms | 1,463 ms | 1,561 ms | 5,390 ms |
300 runs per provider. Median is the middle result; p90 means 90% of runs finished within that time. Rankings apply to this test.
An AI sandbox is a separate place for an agent to run code, use tools, and work with files. Lizard Sandboxes let agents build, test, and debug in the cloud without running that code on your computer.
Sign in to Lizard, choose a project, and create a sandbox from a ready-made template. Choose base for shell tasks, codex for coding tasks, or interpreter for Python, then select a size and region.
Yes. Run Python scripts with the interpreter template, or use shell commands to run tools and tests. Read command output and save results to files. Each command starts a new process.
Lizard uses a pool of prepared Sandboxes to reduce setup time. Startup time depends on the template, size, region, and available capacity.
Each sandbox runs as a Firecracker microVM with its own kernel. A sandbox that attaches an older pod-backed volume, or restores an older pod snapshot, runs in a Kubernetes pod and shares the host kernel; getInfo().runtime tells you which. Give the agent only the credentials and access needed for its task.
You choose the lifetime when creating a sandbox, including no automatic expiry for longer tasks. A sandbox stops at its deadline even if a command is running. Commands do not extend the deadline, and idle time does not stop it early.
Yes. Attach Persistent Volumes at /workspace to keep files after a sandbox stops and reuse them in later runs. A volume connects to one sandbox at a time. Storage stays on one node, so export files you need to protect against node loss.
Yes. With access to your project, an agent can deploy apps and databases through Lizard CLI. They run as separate resources on Lizard and keep running after you stop or delete the sandbox.
Yes. Create a separate sandbox for each task so agents can run commands and tests at the same time. The number of Sandboxes you can run depends on your account limits and available capacity in the region.
The Small size costs $0.0162/hour for 2 vCPU and 4 GB RAM. Billing runs by the second, including idle time, with CPU, RAM, and sandbox egress included. Persistent Volumes cost extra. Older sandboxes without a size keep their original usage-based billing.
Yes. Pro starts with a 7-day trial and $5 in trial credits, and Sandboxes run on it, up to 5 at once. You need a card to start, and we charge nothing during the trial. After it, Pro costs $19/month with $19 in monthly credits included. Once you use your credits, pay as you go.
You don't need a platform team to go live. Your whole cloud, one CLI command away.
