Limits
On Lizard, an app runs up to 5 replicas per service after the first paid Pro invoice, and 1 during the trial. Pro runs up to 100 sandboxes at once and starts up to 24 a minute; the trial allows 5 at once. Sandbox sizes run from Small (2 vCPU / 4 GB) to Large (8 vCPU / 16 GB), and sandbox egress is included up to 2 TB per account over a rolling 30 days. Limits depend on the resource, plan, and account: a per-replica setting is not the total available to a service or an account. Check your plan and the result of the create or scale request before choosing resources.
Applications
| Setting | Scope | What to check |
|---|---|---|
| CPU and memory | Each replica | Three replicas with a 2 vCPU / 2 GiB ceiling have a combined configured ceiling of 6 vCPU / 6 GiB. This is not a usage forecast. |
| Replica count | Service and plan | Your plan sets the limit: 1 per app during the Pro trial, 5 on Pro after the first paid invoice and on Enterprise. The API accepts at most 10, which only an account override can reach. |
| Account resource cap | Account owner | A second project does not necessarily create a second quota. Ask for the effective account cap before planning a large deployment. |
| Worker mode | Service | containerPort=0 runs without an HTTP listener or public load-balancer route. |
| Custom domain | Hostname | Wildcard custom domains are not accepted. Use a specific hostname and complete ownership and DNS checks. |
Sandboxes
Sandboxes run commands and agent tasks in Firecracker microVMs or containers; see runtime and isolation. The limits below apply to every sandbox an account runs.
Sizes
| Size | CPU and memory | Disk (/workspace) | Price while running |
|---|---|---|---|
| Small | 2 vCPU / 4 GB | 5 GB | $0.0162 per hour |
| Medium (default) | 4 vCPU / 8 GB | 20 GB | $0.0324 per hour |
| Large | 8 vCPU / 16 GB | 50 GB | $0.0648 per hour |
CPU and memory are included in the price. Persistent Volumes are billed separately.
Account limits
These limits cap how many sandboxes an account runs at once and how fast it starts new ones. They follow the account owner’s plan. Trial limits apply until the first paid invoice; see Billing.
| Plan | Running at once | Starts per minute | Per hour | Per day |
|---|---|---|---|---|
| Pro trial | 5 | 6 | 30 | 100 |
| Pro | 100 | 24 | 120 | 400 |
| Enterprise | Custom | Custom | Custom | Custom |
- Lizard counts limits per account owner, across all of the owner’s workspaces. A second workspace does not add a second allowance.
- Running means running or resuming. A paused sandbox does not count; resuming one needs a free slot.
- A start is a new sandbox. A resume is not a start. A create that fails on Lizard’s side does not count.
- Over a limit, create and resume return HTTP 429 with
codeset toSANDBOX_LIMIT_REACHED(running) orSANDBOX_RATE_LIMITED(starts). A start-rate refusal includes aRetry-Afterheader. - The dashboard shows how many sandboxes are running against your limit next to New Sandbox. For more than 100 at once, contact us about Enterprise.
Network egress
Sandbox egress has no separate per-GB charge. The included allowance is 2 TB per account over a rolling 30 days, shared across the account’s sandboxes. If your workload needs more, contact us before running it.
Lifetime
| Setting | Current create API |
|---|---|
| Templates | base, interpreter, codex, desktop, opencode, pi, prime, claude |
| Raw API default lifetime | timeoutMs: 0, no expiration |
| Lizard SDK default lifetime | 300000 ms, five minutes |
| Explicit lifetime range | Integer milliseconds from 0 to 2147483647 |
| Updating a lifetime | At least 1000 ms; it is not an idle timer |
| Persistent volume attachment | One sandbox at a time, on the volume’s node |
The CLI also defaults to five minutes; the dashboard defaults to no expiration. Commands do not reset the deadline. For pause, snapshots, fork and what each one keeps, see the sandbox lifecycle.
Regions
The current configured regions include US East (Virginia), us-east-1, and EU West (Limburg), eu-west-lim-a. A region in the catalog does not guarantee available capacity for every resource. Check region choices when creating the resource; a sandbox using an existing volume must run on that volume’s node. lizard regions lists the regions open to your account; see regions.
Before increasing scale
Check the active plan, per-replica settings, account cap, database connection limit, and storage growth together. Use scaling, metrics, and pricing to compare configured capacity with measured usage. Rates for every resource are on the billing page.
Updated