Skip to main content
StateSet Sandbox runs commands in isolated runtimes behind an HTTP controller API (api.sandbox.stateset.app), with create, execute, status, stop and delete operations. The following table shows what CostGraph runs on this provider.

​
Connect

Connect StateSet on Integrations, and CostGraph starts sandboxes in your StateSet account. You don’t run anything yourself.
  1. In CostGraph, go to Integrations > Sandbox > StateSet.
  2. Enter these fields:
    • API key (STATESET_API_KEY, required): A StateSet Sandbox API key.
    • API URL (STATESET_API_URL, optional): A different StateSet Sandbox API address, if you do not use the default.
    • Resource class (STATESET_RESOURCE_CLASS, optional): The StateSet resource class: shared or dedicated.
  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 stateset and the preceding fields as environment variables, as described in Run your own dispatcher.

​
Key and permissions

STATESET_API_KEY is a StateSet Sandbox API key (sent as ‘Authorization: ApiKey <key>’), obtained by signing up at sandbox.stateset.app or POST /api/v1/register; a usable key is issued only after email verification. Use an API key that can create, inspect, execute in and stop a sandbox. StateSet doesn’t publish scope names. Sources: docs.stateset.com: stateset sandbox quickstart, docs.stateset.com: overview, docs.stateset.com: stateset sandbox sdk node.

​
Limits

  • Lifetime is capped by plan: non-durable sandboxes run up to 24 hours. (source)
  • Runtime and quota policies can reject a request; CPU/memory maximums, resource_class, regions and architecture are not documented. (source)
  • Docs warn a published reference does not establish that the hosted service is available; requires a provisioned deployment. (source)