> ## Documentation Index
> Fetch the complete documentation index at: https://docs.costgraph.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# MIOSA sandboxes

> Run CostGraph workflows and CI jobs in MIOSA sandboxes: the key to create, its permissions, and its limits

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.

| Workflows | CI runners | Connect with |
| - | - | - |
| Yes | Yes | Integrations or your own dispatcher |

## 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](https://docs.costgraph.ai/costgraph/workflows/managed-sandboxes.md#run-your-own-dispatcher).

To see what MIOSA costs, connect the [MIOSA integration](https://docs.costgraph.ai/costgraph/integrations/miosa.md).

## 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](https://miosa.ai/docs/authentication.md), [miosa.ai: sandboxes](https://miosa.ai/docs/develop/sandboxes.md), [miosa.ai: timeouts](https://miosa.ai/docs/develop/sandboxes/timeouts.md), [miosa.ai: sizing](https://miosa.ai/docs/develop/sandboxes/sizing.md), [miosa.ai: regions](https://miosa.ai/docs/api-reference/regions.md).

## 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](https://miosa.ai/docs/develop/sandboxes/timeouts.md))
* 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](https://miosa.ai/docs/develop/sandboxes/timeouts.md))
* 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](https://miosa.ai/docs/develop/sandboxes/sizing.md))
* 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](https://miosa.ai/docs/api-reference/regions.md))

## Related

* [Supported sandbox providers](https://docs.costgraph.ai/costgraph/workflows/sandbox-providers.md)
* [Run workflows on a managed sandbox provider](https://docs.costgraph.ai/costgraph/workflows/managed-sandboxes.md)
* [Run CI jobs in sandboxes](https://docs.costgraph.ai/costgraph/autopilot/ci-sandboxes.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.