High Concurrency Sandboxes in EU & US, Fast and Affordable.
San Francisco, CA
Joined February 2025
- Tweets137
- Following45
- Followers189
- Likes94
Pinned Tweet
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-…
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
Migrate on Lizard easily via CLI
Builds are temporarily paused
We are currently investigating this issue
Status: Investigating status.railway.com/incident/…
We timed 1,200 sandbox boots. Lizard's median: 238 ms
300 cold starts each on Lizard, E2B, Daytona and Modal. Every ball in the video is one sandbox boot, dropped into a bin by how long it took to start
lizard.build/session
Median cold start:
> Lizard 238 ms
> E2B 270 ms
> Daytona 796 ms
> Modal 865 ms
Lizard had the lowest median and average of the four. When your agent spins up a sandbox for every task, that wait adds up fast. The full table, up to p99, is on our sandboxes page
Your agents sat idle all weekend. You paid for every hour of it
Most agent setups keep their machines running around the clock, even when nobody gives them work. 50 coding agents on Small sandboxes running 24/7 cost $136 a week. Paused outside working hours, the same 50 cost $36
lizard.build/replay
> a paused Lizard sandbox costs $0 an hour
> resume on Monday with the same memory, files and running processes
> billed per second while it runs, so a 10-minute task costs 10 minutes
> apps and databases on Lizard go to sleep on their own after 10 minutes with no requests
Pause your sandboxes when the work stops. Your agents won't notice, your bill will
Your agents sat idle all weekend. You paid for every hour of it
Most agent setups keep their machines running around the clock, even when nobody gives them work. 50 coding agents on Small sandboxes running 24/7 cost $136 a week. Paused outside working hours, the same 50 cost $36
lizard.build/replay
> a paused Lizard sandbox costs $0 an hour
> resume on Monday with the same memory, files and running processes
> billed per second while it runs, so a 10-minute task costs 10 minutes
> apps and databases on Lizard go to sleep on their own after 10 minutes with no requests
Pause your sandboxes when the work stops. Your agents won't notice, your bill will
Your agent moved to a new sandbox mid-task. It didn't notice
Pause it in the EU, restore it in the US 300-900 ms later, and it picks up on the same line with the same memory, processes and files. Fork it mid-task and the copies keep everything too
Try it free for a week: lizard.build/sandboxes/resum…
> pause and resume with memory and running processes kept
> restore from a snapshot on any machine, EU or US
> fork a running agent and let the copies try different ideas
> a paused sandbox costs $0, a running one is billed per second
What would this cost for your agents? There's a calculator on the page
1,000 deploys from a sandbox at 3 am. Your agents fixed every failed one
Your coding agent builds in a Lizard sandbox and ships straight from it. When a deploy breaks, the CLI doesn't just print a wall of logs: every error comes back as structured JSON with a reason and an exit code, so the agent in the sandbox reads why it failed and fixes it on its own
lizard.build/sandboxes/guard
In our example the agent:
> saw the health check fail with "DATABASE_URL is not set" and added Postgres with lizard add postgres
> redeployed, saw "table users does not exist" and ran the migrations
> shipped on the third try, with zero messages to you
Every sandbox is its own isolated microVM. Works with Claude Code, Codex, Cursor and any agent with a terminal
1,000 deploys from a sandbox at 3 am. Your agents fixed every failed one
Your coding agent builds in a Lizard sandbox and ships straight from it. When a deploy breaks, the CLI doesn't just print a wall of logs: every error comes back as structured JSON with a reason and an exit code, so the agent in the sandbox reads why it failed and fixes it on its own
lizard.build/sandboxes/guard
In our example the agent:
> saw the health check fail with "DATABASE_URL is not set" and added Postgres with lizard add postgres
> redeployed, saw "table users does not exist" and ran the migrations
> shipped on the third try, with zero messages to you
Every sandbox is its own isolated microVM. Works with Claude Code, Codex, Cursor and any agent with a terminal
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
Lizard retweeted
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
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
racing 300 sandboxes per provide: @LizardBuild vs E2B vs Daytona vs Modal
result: Lizard Sandboxes win every column
no sandbox we tested boots faster
Host what your agent builds
Most sandboxes end with the session, and the app your agent built ends with them. On Lizard, one command deploys that code as a live web app in a persistent container with its own HTTPS URL. It keeps running after the sandbox is gone.
> no copying files out and no second platform to sign up for
> add Postgres, Redis or S3 storage next to it, one command each
> live logs and metrics for every service
Build in Lizard Sandboxes. Host on Lizard. One bill, best prices on the market
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 🦎