Skip to main content
Lizard Sandboxes are Firecracker microVMs, each with its own kernel, where agents run code and shell commands, alongside Lizard’s app and database hosting. The following table shows what CostGraph runs on this provider.

​
Connect

Run the dispatcher with provider set to lizard and these variables:
  • LIZARD_API_KEY
  • LIZARD_PROJECT_ID
For CI runners, CostGraph picks the smallest size that fits: small, medium or large.

​
Key and permissions

LIZARD_API_KEY is a Lizard API key (liz_…). Create it in Settings > API keys or with lizard keys create <name>; it is shown once. LIZARD_PROJECT_ID is the ID of the project every sandbox belongs to (an ID, slug or name works). Documented: a key without a scope has full access to every workspace and project you can reach. For least privilege, scope it to the sandbox project with lizard keys create <name> --project <id> (or --workspace). A scoped key works only inside its projects, and cannot see billing, manage keys or members, or change workspace limits. Sources: lizard.build: keys, lizard.build: quickstart, lizard.build: limits, lizard.build: regions.

​
Limits

  • Lifetime: the raw API default is timeoutMs 0 (no expiration). The SDK and CLI default to 5 minutes. An explicit lifetime can be 0-2147483647 ms. This is a deadline, not an idle timer, and commands do not reset it. (source)
  • Sizes: Small 2 vCPU/4 GB, Medium 4/8 GB (default outside the trial), Large 8/16 GB. Concurrency is counted in vCPU: Pro 40, Pro 5x 220, Pro 20x 1,200. Starts are limited on Pro to 24/min, 120/h and 400/day. (source)
  • Trial: Small sandboxes only (up to 4, 8 vCPU) and US regions only. Large sandboxes start after the first Pro payment. (source)
  • Regions include us-east-1 and eu-west-lim-a; “lizard regions” lists the ones open to you. The docs do not state the CPU architecture. (source)