Skip to main content
Promigence runs sandboxes forked from verified snapshots of your repository, driven by a CLI and a TypeScript SDK and billed per second. The following table shows what CostGraph runs on this provider.

Connect

Connect Promigence on Integrations, and CostGraph starts sandboxes in your Promigence account. You don’t run anything yourself.
  1. In CostGraph, go to Integrations > Sandbox > Promigence.
  2. Enter these fields:
    • API key (PROMIGENCE_API_KEY, required): A Promigence API key for the project sandboxes run in.
  3. Click Connect.

Your own dispatcher

To keep the key out of CostGraph or reach a private network, run your own dispatcher instead. Set provider to promigence and the preceding fields as environment variables, as described in Run your own dispatcher. To see what Promigence costs, connect the Promigence integration.

Key and permissions

PROMIGENCE_API_KEY is a Promigence API key; every key belongs to one project. Create it with “promigence signup”/“promigence login” (the CLI stores a key) or “promigence keys create” (secret shown once; owners can make service keys for CI that survive a member leaving). Keys have an --access level: full (default), run (sandboxes, runs and builds, but no changes to secrets, keys or billing) or read. Minimum for create/exec/list/delete is a run" key on the project, ideally a service key with "--expires set. Source: https://www.promigence.ai/docs/cli Sources: www.promigence.ai: quickstart, www.promigence.ai: cli, www.promigence.ai: sdk, www.promigence.ai: limits.

Limits

  • Each sandbox runs for up to an hour (15 minutes unless --timeout asks for more). (source)
  • New account runs 20 sandboxes at once; paused sandboxes do not count and are kept 30 days; raise limits via [email protected]. (source)
  • Sizes up to large (8 vCPU); small tier is 2 vCPU / 4 GiB. (source)
  • Servers are on the US East Coast; a free credit must be claimed before the first run. (source)
  • Beta: CLI reference is for promigence CLI 0.1.0-beta.14. (source)