Skip to main content
Superserve sandboxes are isolated cloud environments built on Firecracker microVMs, each launched from a reusable template. The following table shows what CostGraph runs on this provider.

​
Connect

Connect Superserve on Integrations, and CostGraph starts sandboxes in your Superserve account. You don’t run anything yourself.
  1. In CostGraph, go to Integrations > Sandbox > Superserve.
  2. Enter these fields:
    • API key (SUPERSERVE_API_KEY, required): A Superserve API key from Settings > API keys in the Superserve console.
  3. Click Connect.
Sandbox size comes from the template set as providerTemplate.

​
Your own dispatcher

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

​
Key and permissions

SUPERSERVE_API_KEY is a Superserve API key (ss_live_…) created at console.superserve.ai under Settings > API keys > Create key (shown once). Sent as X-API-Key; per-sandbox file/command calls use a separate short-lived X-Access-Token. Keys are scoped to a single team, with no per-key permissions or roles. Sources: docs.superserve.ai: home, docs.superserve.ai: api key, docs.superserve.ai: lifecycle, docs.superserve.ai: sandbox.

​
Limits

  • Auto-pause is off unless timeoutSeconds is set; it caps active time per session, not idle time. (source)
  • Paused sandboxes are kept forever by default; auto-delete window max 30 days. (source)
  • Max lifetime, vCPU/RAM caps, regions, architecture: not documented. (source)