Skip to main content
Leap0 runs isolated sandboxes, each in its own Firecracker microVM, that you create from a template, call over HTTP or WebSocket, and delete when done. The following table shows what CostGraph runs on this provider.

​
Connect

Connect Leap0 on Integrations, and CostGraph starts sandboxes in your Leap0 account. You don’t run anything yourself.
  1. In CostGraph, go to Integrations > Sandbox > Leap0.
  2. Enter these fields:
    • API key (LEAP0_API_KEY, required): A Leap0 API key from Settings > API Keys in the Leap0 dashboard.
  3. Click Connect.
For CI runners, CostGraph sets CPU and memory, up to 8 vCPU and 8 GB.

​
Your own dispatcher

To keep the key out of CostGraph or reach a private network, run your own dispatcher instead. Set provider to leap0 and the preceding fields as environment variables, as described in Run your own dispatcher.

​
Key and permissions

LEAP0_API_KEY is a Leap0 API key. Create it in the Leap0 Dashboard under Settings > API Keys > Create Key; it is shown once. keys are not scoped: full access to sandboxes, templates and snapshots in the organization. Source: https://leap0.dev/docs/api-keys Sources: leap0.dev: api keys, leap0.dev: limits, leap0.dev: public preview, leap0.dev: sandboxes.

​
Limits

  • Public preview: free to use, but breaking changes and short periods of downtime may happen. (source)
  • Sandbox timeout is 1 min to 8 hours (default 5 min). With auto_pause=true the sandbox pauses at the timeout instead of stopping. (source)
  • 1-8 vCPU, 512 MiB-8 GB memory (an even number), 10 GiB disk. Requests and responses are capped at 10 MiB, and WebSocket idle timeout is 5 minutes. (source)
  • Organization quotas: 100 API keys, 25 templates, and 1000 API requests per 60 s. Limits may change during the preview. The docs do not state regions or CPU architecture. (source)