Run agents in sandboxes Ship what they build

Give your agent a Cloud VM with a browser and persistent storage. Scale to thousands of sandboxes and ship what agents build in one command.

Install Lizard Skill
npx skills add lizard-build/skill -g

Full-stack AI-agentic infrastructure

Built for agents. Ready for your product.

Lizard Sandboxes

Run concurrent agents
in isolated VMs

Up to 100 sandboxes at once on Pro, or any number on Enterprise. Each boots in under 250 ms.

Persistent Volumes

Keep your files on a persistent volume

A volume keeps your files after a sandbox stops. Attach it to your next sandbox to use the same files.

Apps & databases

Deploy apps & databases with zero ops

Run web apps your agents build with Managed Postgres, Redis and S3-⁠compatible storage, without managing CI/CD.

Desktop & browser

Open and test apps in a browser

Use the built-in desktop and browser to interact with apps in your sandbox and check your agent’s work.

Multiple regions

Run Sandboxes in the US or EU

Choose US East or EU West when you create a sandbox.

Logs & metrics

Inspect logs, CPU and memory

Read process output and track resource usage to debug errors and identify resource bottlenecks.

Know what your agents cost

Choose your sandbox size and runtime.
Estimate compute costs before subscription fees and credits.

More room. Less overhead

Configuration

Sandboxes at once
Runtime
44 h
ResourcesPer sandbox
Resources per sandbox

Estimated sandbox costs

$0.71/ month

Compare different providersSame CPU, RAM & runtime
Cloudflare$3.074.3×
Vercel$4.866.8×
E2B$7.2910×
Daytona$7.2910×
Modal$10.4715×
What is included, and what costs extra?

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 ↗
Hourly rates compared

Price per hour for 2 vCPU and 4 GB of memory, from each provider's public pricing page. Rates checked on .

ProviderPer hourCompared with LizardHow it is billed
Lizard$0.01621×Flat rate per size, billed by the second
Cloudflare$0.06974.3×10% active CPU; memory and disk as provisioned
Vercel$0.11046.8×10% active CPU; all allocated memory
E2B$0.165610×Per vCPU and GiB of memory, by the second
Daytona$0.165610×Per vCPU and GiB of memory, by the second
Modal$0.238015×Sandbox rates; 1 physical core = 2 vCPU

Vercel and Cloudflare bill CPU only while it is active, so the table assumes 10% active CPU, as the calculator does. Plan fees, credits, storage and egress are not included.

Give your agents a better place to run

Lowest median. Lowest average. Measured against E2B, Daytona, and Modal.

Lizard
228ms

Lowest median time

Less time is better

Full benchmark results

300 runs per provider. The lowest time in each column is highlighted.
ProviderMedianAveragep90p95p99Maximum
Lizard228 ms — Lowest time239 ms — Lowest time265 ms — Lowest time310 ms — Lowest time477 ms — Lowest time693 ms — Lowest time
E2B264 ms323 ms487 ms603 ms736 ms1,260 ms
Daytona819 ms945 ms1,370 ms1,671 ms2,332 ms5,532 ms
Modal929 ms983 ms1,290 ms1,422 ms1,593 ms1,932 ms
How we measured

· 300 starts per provider, from the create request to the first verified Python output. Runner: Railway US East (us-east4).

Lizard: base template, Small (2 vCPU / 4 GB), us-east-1. Providers used different regions, templates and resource sizes. Starts can use prepared capacity; results vary by workload.

Run code in a sandbox

Create a Firecracker microVM, run a command and stop it with Lizard SDK for TypeScript and Python, or with Lizard CLI.

npm install @lizard-build/sdk
import { Lizard } from '@lizard-build/sdk'// Reads LIZARD_API_KEY from the environmentconst lizard = new Lizard({ project: 'my-project' })const sandbox = await lizard.create('interpreter', { size: 'small' })try {  const run = await sandbox.process.exec("python -c 'print(2 ** 10)'")  console.log(run.stdout) // 1024} finally {  await sandbox.kill()}

AI sandbox FAQ

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.

In our 12 October 2026 test, the median time from the create request to the first Python output was 228 ms over 300 starts (base template, Small size, us-east-1). E2B took 264 ms, Daytona 819 ms and Modal 929 ms in the same test. Results vary with the template, size, region and free capacity.

Lizard Sandboxes run as Firecracker microVMs, each with its own kernel. Give the agent only the credentials and access its task needs.

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 trial runs up to 5 Sandboxes at once and Pro up to 100. Enterprise has no limit on how many run at once, so you can scale to thousands.

The Small size costs $0.0162/hour for 2 vCPU and 4 GB RAM. For the same 2 vCPU and 4 GB, E2B and Daytona charge $0.1656/hour and Modal $0.2380/hour (rates checked on 20 October 2026). Billing runs by the second while the sandbox runs, including idle time. CPU and RAM are included, along with 2 TB of sandbox egress per account over a rolling 30 days. A successful pause stops compute charges; Persistent Volumes storage is billed separately. Older sandboxes without a size keep their original usage-based billing.

Sandbox egress limits

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.

Build with AI. Ship with Lizard

You don't need a platform team to go live. Your whole cloud, one CLI command away.

Services
—
Add-ons
—
Deployments
—
Sandbox starts
—