You shipped an update. 1,000 users lost their files. Not on Lizard Every app that gives users their own agent hits this sooner or later: you push a new version, rebuild the environments, and whatever your users made inside them is gone On Lizard each user gets their own sandbox, and their files live on a persistent volume at /workspace, not inside the sandbox. Ship a new version, snapshot it once, and every user's sandbox comes back on it in 1 to 3 seconds with the same volume attached lizard.build/sandboxes > the sandbox is new, the user's files stay exactly where they were > no migration scripts, no copying data between machines > each user's sandbox is its own isolated microVM > billed per second while it runs, and a paused sandbox costs nothing Ship as often as you want. Your users won't notice anything except the new features

96 agents, one shared bucket, and a city built together We gave 96 agents their own Lizard sandboxes, one shared bucket and a private network, and let them build a city together. Every agent reads and writes the same bucket and talks to the others directly, even between our EU and US regions lizard.build/sandboxes On most clouds that's where the bill hides: a fee on every read and write, and a fee on every message between machines. On Lizard both are $0 > Object Storage has no per-request fees > traffic between sandboxes runs on a private network, it's free and doesn't count toward your egress > each agent runs in its own isolated microVM, $0.0162 an hour for a Small sandbox You pay for the sandboxes while they run and for what you store. Not for your agents talking to each other

Your agents can talk to each other, and the traffic is free Lizard sandboxes reach each other over a private network, even across regions. Put a planner in the EU and its workers in the US, pass files, diffs and test results between them, and pay $0 for that traffic lizard.build/sandboxes > private network between sandboxes, not the public internet > works between EU and US regions > traffic between sandboxes is free and doesn't count toward your 2 TB of egress > every agent runs in its own isolated microVM

One bug, 50 agents, first fix wins Set up a sandbox once and snapshot it, or fork one that's already running with its memory and processes. Each copy is ready in 1 to 3 seconds. Give 50 agents the same bug and a different idea each, and keep the first fix that turns the tests green lizard.build/sandboxes > 50 Small sandboxes cost $0.81 an hour while they run > pause the other 49 the moment one passes, and they cost nothing > every fork runs in its own isolated microVM

Run 100 coding agents at once Every Lizard sandbox boots in about 238 ms, and Pro runs up to 100 of them at the same time. Give each one Claude Code or Codex and its own task, and all 100 work in parallel lizard.build/sandboxes > each agent in its own isolated microVM > 100 Small sandboxes cost $1.62 an hour together > billed per second, so a 20-minute task costs 20 minutes > pause them when they're done and they cost nothing until you resume

Your agent reads files all day. Here's what that costs We priced one month of a typical agent workload: 1 TB stored, 100 GB served, 500M reads and 50M writes Lizard: $18 Cloudflare R2: $420 AWS S3: $473 lizard.build/sandboxes > no per-request fees on Lizard Object Storage, you pay for storage and egress only > storage at $0.0135 per GB-month, S3-compatible > sits next to your sandboxes, apps and databases on one bill Competitor prices are from their public pricing pages as of October 2026

Host 10,000 apps and pay for the ones people use Any Lizard apps and databases is serverless now! A small app using 60 MB of RAM costs about $0.60 a month running and about $0.01 paused. After a stretch with no requests (10 minutes by default, you can change it), the whole project, frontend, backend, Postgres and Redis, freezes in its current state. > while it's paused you pay only for its storage > the next request wakes it in 0.5 to 1 second, right where it left off > made for app builders and agents that ship thousands of small apps, most of them idle most of the day Billed by usage while it runs

Fastest to boot, and the cheapest to keep running Yura raced 300 cold starts per provider and Lizard came first in every column, from the median to the slowest start. Speed is half of it. An agent that runs all day also has to be cheap to keep running We took the same four providers and priced 10 Small sandboxes (2 vCPU, 4 GB RAM) running 24/7 for a full month, using the calculator on our sandboxes page: Lizard: $118 Modal: $440, 3.7x more E2B: $907, 7.7x more Daytona: $912, 7.7x more > billed per second, so a sandbox that runs for 10 minutes costs 10 minutes > pause it and it costs nothing until you resume > every sandbox is its own isolated microVM, in US or EU regions

Lizard: sandboxes for AI agents at half the price of the next-cheapest provider Give your agent its own cloud machine. It starts in 247 ms, works all night, and you pay only while it runs lizard.build/silent-moss > a Firecracker microVM with its own kernel for every sandbox > templates with Claude Code, Codex, opencode or a full Linux desktop with Chromium > runs until you delete it. Pause it and resume tomorrow with files and running processes where you left them > US and EU regions, so the box sits next to your agent When the agent builds something worth shipping, lizard up puts it on a live URL, with managed Postgres, Redis and S3 next to it. One platform, one bill From $0.009/h, billed per second. $10 in free credits to start 🦎

Delete Sandbox after: Never It's a real option when you create a Lizard sandbox. The box runs until you delete it. Nothing reaps it after 24 hours or kills it while your agent waits on a long build Pause it at the end of the day and resume it tomorrow with its memory and files intact. Your agent picks up where it stopped, even if your laptop was closed all night Billing is per second while it runs. A Small box running for a whole month costs about $6.50 In the dashboard, pick Never. With the Lizard CLI, tell your coding agent to spin up a sandbox that never expires and it runs the command for you lizard.build/cool-petal

Lizard sandboxes are now fully isolated, and still the cheapest on the market Every sandbox runs in its own Firecracker microVM with its own kernel. Templates: base: Python 3.11 interpreter: Python and Node with pandas, numpy, matplotlib, scipy and Jupyter desktop: a full Linux desktop with Chromium, for computer use claude, codex, opencode, pi, prime: the coding agent is installed and ready for a prompt Pause a sandbox and resume it later. Files and running processes stay where you left them From $0.009/h, billed per second, half of what the next-cheapest provider charges. $10 in free credits to start 🦎 lizard.build/sandboxes

US or EU based sandboxes? Multiple regions is best option A coding agent can do that hundreds of times in one task. Put an ocean between the agent and the box and each trip costs you around 90 ms. 200 tool calls is 18 seconds of your agent waiting on the Atlantic Lizard runs sandboxes in both the US and the EU. Keep the box next to your agent when your users' data has to stay there From $0.009/h, billed per second. $10 in free credits to start 🦎 lizard.build/sandboxes

Shipping a vibe-coding app takes three pieces. Sandbox-only providers sell you one 🦎 1. Sandboxes where your users' agents write and run code 2. Hosting to put what they build into production 3. A database right next to it On a big cloud you wire up 2 and 3 yourself: containers, VPC, IAM, a load balancer, a registry On Lizard it's one platform and one bill: - sandboxes from $0.009/h - lizard up ships the app to a live URL - managed Postgres, Redis and S3 storage next to it - pay as you go, billed per second Our bet: you can launch your own vibe-coding app on Lizard in a day. Show us yours