> ## 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.

# exe.dev sandboxes

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

exe.dev provides Linux VMs on demand; standalone VMs (sandboxes) have their own reserved vCPU and memory, metered per second, and are fully scriptable over its SSH/HTTPS API.

The following table shows what CostGraph runs on this provider.

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

## Connect

Connect exe.dev on Integrations, and CostGraph starts sandboxes in your exe.dev account. You don't run anything yourself.

1. In CostGraph, go to **Integrations > Sandbox > exe.dev**.

2. Enter these fields:

   * **API token** (`EXEDEV_API_TOKEN`, required): An exe.dev API token.

3. Click **Connect**.

### Your own dispatcher

To keep the key out of CostGraph or reach a private network, run your own dispatcher instead.
Set `provider` to `exedev` 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).

## Key and permissions

EXEDEV\_API\_TOKEN is an exe.dev HTTPS API bearer token (exe0/exe1), generated with `ssh exe.dev ssh-key generate-api-key` or signed locally with your SSH key.

Tokens are scoped by a 'cmds' list. CostGraph runs new, ls, rm and ssh \<vm>, so the minimum is cmds=\["new","ls","rm","ssh"]. The default cmds list includes new and ls but NOT rm or ssh, so a default token cannot delete or exec. `ssh <vm-name>` restricts ssh to one VM, which does not work for dynamically named sandboxes. On Work/Enterprise teams an admin must also enable standalone VM creation (team settings standalone).

Sources: [exe.dev: https api](https://exe.dev/docs/https-api.md), [exe.dev: https api run on vm](https://exe.dev/docs/https-api-run-on-vm.md), [exe.dev: https api local key](https://exe.dev/docs/https-api-local-key.md), [exe.dev: standalone vms](https://exe.dev/docs/standalone-vms.md), [exe.dev: regions](https://exe.dev/docs/regions.md).

## Limits

* HTTPS API commands time out after 30 seconds (504); request body max 64 KB. Long work must be detached with setsid nohup. ([source](https://exe.dev/docs/https-api.md))
* Standalone VMs: up to 2 GiB memory per vCPU; up to 32 vCPUs on Work, plan vCPUs on other plans. ([source](https://exe.dev/docs/standalone-vms.md))
* VMs are created in the account's region (LAX, NYC, DAL, FRA, TYO, SYD, SGP, LON); no max lifetime is documented. ([source](https://exe.dev/docs/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.