Skip to main content
MIOSA Sandboxes are fast, isolated Linux VMs (Firecracker by default) for code execution, builds, tests and dev servers, with preview URLs and snapshots. The following table shows what CostGraph runs on this provider.

​
Connect

Connect MIOSA on Integrations, and CostGraph starts sandboxes in your MIOSA account. You don’t run anything yourself.
  1. In CostGraph, go to Integrations > Sandbox > MIOSA.
  2. Enter these fields:
    • API key (MIOSA_API_KEY, required): A MIOSA API key from the MIOSA dashboard.
  3. Click Connect.
For CI runners, CostGraph sets CPU and memory; MIOSA rounds up to its next size.

​
Your own dispatcher

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

​
Key and permissions

MIOSA_API_KEY is a MIOSA API key (msk_<role>_…). Create it in the dashboard or with POST /api/v1/api-keys (key_type user); it is shown once. Documented as role-typed keys, with no finer scopes: a user key (msk_u_) covers compute, desktop, files, exec, CUA, OSA and credits across the workspace, which is enough to create, exec, list and delete sandboxes. Admin keys (msk_a_) add /api/v1/admin/* and are operator-internal. Platform keys (msk_p_) are for tenant-wide automation and are minted by tenant owners or admins. Sources: miosa.ai: authentication, miosa.ai: sandboxes, miosa.ai: timeouts, miosa.ai: sizing, miosa.ai: regions.

​
Limits

  • timeout_sec counts from the last activity: default 3600 s, range 1-86400. When it expires, a persistent sandbox (the default) moves to stopped with its disk kept, and a non-persistent one is destroyed. always_on=true disables the timeout. (source)
  • idle_timeout_sec: accounts created on or after 2026-10-11 stop idle sandboxes after 30 minutes by default (wake on request); 0 disables it. (source)
  • Sizes go from xs (1 vCPU/2 GB) to xl (16 vCPU/32 GB): cpu_count 1-16, memory_mb 2048-32768. Default is small, 2 vCPU/4 GB. (source)
  • Regions: us-west (default), us-east, us-mia, all live with every size. No EU region is listed, and the docs do not state the CPU architecture. (source)