High Concurrency Sandboxes in EU & US, Fast and Affordable.
San Francisco, CA
Joined February 2025
- Tweets189
- Following47
- Followers308
- Likes122
100x machines.
At 10,000 sandboxes @modal $532,224 more every month
10,000 small sandboxes, 8 hours a day, 30 days:
> Lizard $38,880
> Boat $43,200
> @Cloudflare $167,184
> Vercel $264,960
> @e2b $397,440
> Daytona $397,440
> Modal $571,104
lizard.build/now
Enterprise has no cap on how many run at once.
Some users asked where is comparison with @boatdotdev. Added it, and scaled the bill to a real agent fleet
100 small sandboxes, 8 hours a day, 30 days:
> Lizard $389
> Boat $432
> Cloudflare $1,673
> Vercel $2,650
> E2B $3,974
> Daytona $3,974
> Modal $5,712
lizard.build/boat
Very close, but Lizard still better price!
Some users asked where is comparison with @boatdotdev. Added it, and scaled the bill to a real agent fleet
100 small sandboxes, 8 hours a day, 30 days:
> Lizard $389
> Boat $432
> Cloudflare $1,673
> Vercel $2,650
> E2B $3,974
> Daytona $3,974
> Modal $5,712
lizard.build/boat
Very close, but Lizard still better price!
This list is missing the sandbox that costs $11.66 a month. Modal charges $171 for the same box
Same small sandbox, running 24/7 for 30 days:
> Lizard $11.66
> Cloudflare $50
> Vercel $79
> E2B $119
> Daytona $119
> Modal $171
lizard.build/options
Firecracker microVMs, 228 ms cold start, snapshots and pause built in. First week free
This list is missing the sandbox that costs $11.66 a month. Modal charges $171 for the same box
Same small sandbox, running 24/7 for 30 days:
> Lizard $11.66
> Cloudflare $50
> Vercel $79
> E2B $119
> Daytona $119
> Modal $171
lizard.build/options
Firecracker microVMs, 228 ms cold start, snapshots and pause built in. First week free
Most goated alternatives to Vercel sandbox:
1. E2B (@e2b) - e2b.dev
2. Instabox (@insforge) - instabox.sh
3. Modal sandbox(@modal ) - modal.com
4. Sandboxer(by @jonoringer) - sandboxer.com
5. Daytona(@daytonaio ) - daytona.io
6. Cloudflare Sandbox(@Cloudflare ) - cloudflare.com/products/sand…
There is. It's metal.
Software get copied in a week. Hardware, power and servers you own don't.
Get a nice long term spot in sandbox industry:
lizard.build/moat
700 VMs of minecraft is cool. we brought the shotgun: 50 Lizard sandboxes running doom
One sandbox first: 4 vCPU, 8 GB, a desktop, Doom installed. It was up in under a second. We snapshotted it in 18 seconds, then restored that snapshot 50 times
lizard.build/launch
Every copy loaded its own map and its own bot, with a real screen recording from each desktop. No mockups, the grid in the video is all 50
> 50 sandboxes, 4 vCPU / 8 GB each
> one snapshot, 50 different games
> $0.0324/h per sandbox, $1.62/h for the whole grid
> desktop, snapshots, pause and resume built in
Next time we'll let the agents play
nice try
we spun up 700 boat.dev VMs 4c x 8gb, started codex + minecraft, made it all play in multiplayer together
they all booted from a snapshot in the first 10s, which cost $0.07, same price per VM, core & ram
but much more impressive capabilities and scale
Railway's report is out: rotate every secret stored before Oct 21!
If you're rotating everything anyway, set the new keys on Lizard and let your coding agent move the rest. Apps, workers, Postgres, Redis, S3 and your agent sandboxes, on one bill
lizard.build/rotate
> npx skills add lizard-build/skill -g
> tell your agent "migrate us to Lizard"
> it recreates services, databases and the data inside
Agent sandboxes come out 18x cheaper: 10 running 24/7 cost $118/mo on Lizard vs ~$2,129 on Railway. First week free
The preliminary report related to the October 21st Security Incident is now available.
blog.railway.com/p/prelimina…
For anyone moving off Railway this week
10 sandboxes (2 vCPU, 4 GB) running 24/7 for a month:
> Lizard: $118
> Railway: ~$2,129
lizard.build/move
> app hosting costs less too: $18.26 per vCPU and $9.13 per GB of RAM a month
> Postgres, Redis, S3 and agent sandboxes on one bill
> tell your coding agent "migrate us to Lizard" and it moves your apps, databases and data
Rotate your secrets first, then move. First week free
An urgent notice from the Railway team
blog.railway.com/p/security-…
Railway deploys still paused? Here's a Railway alternative
Rotate your secrets first, then tell your coding agent "migrate us to Lizard": it redeploys your apps and workers, sets up Postgres, Redis and S3 and imports your data
lizard.build/unpause
> set fresh secrets on Lizard, don't copy the old ones
> apps, databases and agent sandboxes on one account, one bill
> first week free
The easy way to move is right here 👇
Deploys paused and secrets to rotate? Your agent can move you to Lizard sandboxes and hosting in one prompt
If your platform froze deploys this week, you don't have to wait it out. Rotate your secrets first, then hand the move to your coding agent
lizard.build/column
> install the Lizard Skill: npx skills add lizard-build/skill -g
> tell your agent "migrate us to Lizard": it redeploys your services and workers, provisions Postgres, Redis and S3 and imports your data
> set your new, rotated secrets on Lizard instead of copying the old ones
> point your domain and you're back to shipping
Works with Claude Code, Codex, Cursor and any agent with a terminal. Your agents can keep building in Lizard sandboxes, and the first week is free
Deploys paused and secrets to rotate? Your agent can move you to Lizard sandboxes and hosting in one prompt
If your platform froze deploys this week, you don't have to wait it out. Rotate your secrets first, then hand the move to your coding agent
lizard.build/column
> install the Lizard Skill: npx skills add lizard-build/skill -g
> tell your agent "migrate us to Lizard": it redeploys your services and workers, provisions Postgres, Redis and S3 and imports your data
> set your new, rotated secrets on Lizard instead of copying the old ones
> point your domain and you're back to shipping
Works with Claude Code, Codex, Cursor and any agent with a terminal. Your agents can keep building in Lizard sandboxes, and the first week is free
An urgent notice from the Railway team
blog.railway.com/p/security-…