Skip to main content
microsandbox cloud runs the same microsandbox microVM sandboxes on hosted infrastructure, using the same SDKs and msb CLI as local use. The following table shows what CostGraph runs on this provider.

​
Connect

Run the dispatcher with provider set to microsandbox and these variables:
  • MSB_API_KEY
For CI runners, CostGraph sets CPU and memory. If you connected Microsandbox for cost data, CostGraph’s dispatcher can start sandboxes with the key from your Microsandbox integration. That key then needs the permissions in the next section as well.

​
Key and permissions

MSB_API_KEY is an organization API key (msb_…). Create it in the dashboard at dashboard.microsandbox.dev/access/api-keys. Cloud access is in private beta and must be requested first. keys are not scoped: an API key acts on its whole organization, which is taken from the key. The API reference documents no per-operation scopes, only org-level key versus user personal token (msb_pat_). Source: https://docs.microsandbox.dev/api-reference/overview.md Sources: docs.microsandbox.dev: overview, docs.microsandbox.dev: overview, docs.microsandbox.dev: get quota usage, docs.microsandbox.dev: lifecycle.

​
Limits

  • microsandbox cloud is in private beta and needs a request for access. (source)
  • Per-sandbox maximum memory and disk, concurrent running sandboxes and total sandboxes come from the billing plan and org overrides, readable from the quota endpoint. The docs publish no fixed numbers or maximum lifetime. (source)
  • Lifecycle (start, stop, delete) is documented. No auto-stop or idle limit for cloud sandboxes and no region list were found. (source)