Connect
Connect CreateOS on Integrations, and CostGraph starts sandboxes in your CreateOS account. You don’t run anything yourself.- In CostGraph, go to Integrations > Sandbox > CreateOS.
-
Enter these fields:
- API key (
CREATEOS_SANDBOX_API_KEY, required): A CreateOS API key from your CreateOS profile page.
- API key (
- Click Connect.
providerTemplate as the root filesystem.
Your own dispatcher
To keep the key out of CostGraph or reach a private network, run your own dispatcher instead. Setprovider to createos-sandbox and the preceding fields as environment variables, as described in Run your own dispatcher.
To see what CreateOS costs, connect the CreateOS integration.
Key and permissions
CREATEOS_SANDBOX_API_KEY is a per-user CreateOS API key sent as X-Api-Key, obtained from the CreateOS dashboard profile page (https://createos.sh/app/profile). No scopes are documented for the per-user API key, which acts with the user’s full access. The only narrower credential, a sandbox access token, is limited to one existing sandbox and cannot list (‘GET /v1/sandboxes requires a user credential’) or create, so the user API key is required. Sources: createos.sh: Overview, createos.sh: Limits, createos.sh: Quickstart, createos.sh: Access Tokens.Limits
- No maximum session length: ‘A sandbox runs until you destroy it, pause it, or it auto-pauses.’ Auto-pause on idle is off by default (60-86,400 s when set; idle = no exec, file transfer or tunnel activity). (source)
- Largest shape per plan: Free 1 vCPU/1 GB, Beginner 4 vCPU/4 GB, Pro 8 vCPU/8 GB, Enterprise 8 vCPU/16 GB; concurrent sandboxes Free 1, Beginner 5, Pro 20, Enterprise 30; no GPU. (source)
- Bandwidth budget 50 GiB per sandbox by default; networking pauses when exhausted until recharged. (source)
- Region chosen at create: eu or us. (source)