Connect
Connect Isorun on Integrations, and CostGraph starts sandboxes in your Isorun account. You don’t run anything yourself.- In CostGraph, go to Integrations > Sandbox > Isorun.
-
Enter these fields:
- API key (
ISORUN_API_KEY, required): An Isorun API key from the Isorun dashboard.
- API key (
- Click Connect.
providerTemplate as the image.
Your own dispatcher
To keep the key out of CostGraph or reach a private network, run your own dispatcher instead. Setprovider to isorun and the preceding fields as environment variables, as described in Run your own dispatcher.
Key and permissions
ISORUN_API_KEY is an Isorun API key (isorun_live_<region><id><hmac>). Create it in the dashboard at app.isorun.ai. Each key belongs to your organization and that organization’s region (US or EU). keys are not scoped: one API key has full access to its organization (in its region). The docs describe no scopes, permission levels or roles. Source: https://docs.isorun.ai/getting-started/authentication Sources: docs.isorun.ai: home, docs.isorun.ai: authentication, docs.isorun.ai: lifecycle, docs.isorun.ai: troubleshooting, docs.isorun.ai: pricing.Limits
- Idle timeout: timeoutSec defaults to 300 s, and the sandbox is destroyed when it fires. Extend it with setTimeout(seconds); 0 disables it. No maximum lifetime is documented. (source)
- Default size is 1 vCPU, 1 GiB RAM and 4 GiB scratch disk. No maximum vCPU or memory is documented. (source)
- exec has a default timeout of 30 seconds; pass a longer timeout or use execStream for long work. Concurrent sandboxes count against your limits (429), but the number is not published. (source)
- Regions are US and EU, fixed per organization and taken from the key. The docs do not state the CPU architecture. (source)