> ## Documentation Index
> Fetch the complete documentation index at: https://docs.costgraph.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Lizard sandboxes

> Run CostGraph workflows and CI jobs in Lizard sandboxes: the key to create, its permissions, and its limits

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.

| Workflows | CI runners | Connect with |
| - | - | - |
| Yes | Yes | Integrations or your own dispatcher |

## Connect

Connect Lizard on Integrations, and CostGraph starts sandboxes in your Lizard account. You don't run anything yourself.

1. In CostGraph, go to **Integrations > Sandbox > Lizard**.

2. Enter these fields:

   * **API key** (`LIZARD_API_KEY`, required): A Lizard API key from Settings > API keys.
   * **Project** (`LIZARD_PROJECT_ID`, required): The ID, slug or name of the Lizard project sandboxes belong to.

3. Click **Connect**.

For CI runners, CostGraph picks the smallest size that fits: small, medium or large.

### Your own dispatcher

To keep the key out of CostGraph or reach a private network, run your own dispatcher instead.
Set `provider` to `lizard` and the preceding fields as environment variables, as described in [Run your own dispatcher](https://docs.costgraph.ai/costgraph/workflows/managed-sandboxes.md#run-your-own-dispatcher).

## 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](https://lizard.build/docs/cli/keys.md), [lizard.build: quickstart](https://lizard.build/docs/sandboxes/quickstart.md), [lizard.build: limits](https://lizard.build/docs/platform/limits.md), [lizard.build: regions](https://lizard.build/docs/deploy/regions.md).

## 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](https://lizard.build/docs/platform/limits.md))
* 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](https://lizard.build/docs/platform/limits.md))
* Trial: Small sandboxes only (up to 4, 8 vCPU) and US regions only. Large sandboxes start after the first Pro payment. ([source](https://lizard.build/docs/platform/limits.md))
* 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](https://lizard.build/docs/deploy/regions.md))

## Related

* [Supported sandbox providers](https://docs.costgraph.ai/costgraph/workflows/sandbox-providers.md)
* [Run workflows on a managed sandbox provider](https://docs.costgraph.ai/costgraph/workflows/managed-sandboxes.md)
* [Run CI jobs in sandboxes](https://docs.costgraph.ai/costgraph/autopilot/ci-sandboxes.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.