Fast and affordable Sandboxes in EU & US
San Francisco, CA
Joined February 2025
- Tweets112
- Following43
- Followers174
- Likes82
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
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
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
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
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
Lizard retweeted
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
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