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

# Vercel sandboxes

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

Vercel Sandbox provides on-demand, isolated Firecracker compute for running untrusted code, tests and builds, tied to a Vercel team and project.

The following table shows what CostGraph runs on this provider.

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

## Connect

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

1. In CostGraph, go to **Integrations > Sandbox > Vercel**.

2. Enter these fields:

   * **Access token** (`VERCEL_TOKEN`, required): A Vercel access token from vercel.com/account/tokens.
   * **Team ID** (`VERCEL_TEAM_ID`, required): The Vercel team ID from team settings.
   * **Project ID** (`VERCEL_PROJECT_ID`, required): The Vercel project ID from the project's General settings.

3. Click **Connect**.

For CI runners, CostGraph sets vCPUs; Vercel gives 2 GB of memory per vCPU. `providerTemplate` takes a snapshot id.

### Your own dispatcher

To keep the key out of CostGraph or reach a private network, run your own dispatcher instead.
Set `provider` to `vercel` 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 Vercel costs, connect the [Vercel integration](https://docs.costgraph.ai/costgraph/integrations/vercel.md).

## Key and permissions

VERCEL\_TOKEN is a Vercel access token created at vercel.com/account/tokens (name, Scope, expiration; shown once). VERCEL\_TEAM\_ID is the team ID from team settings; VERCEL\_PROJECT\_ID is the project ID from project General settings. Access tokens are the documented method for external CI (OIDC otherwise).

Token scope levels: Full Account, Team (all projects of one team) or Project. The Sandbox auth page requires "a Vercel access token with access to the team", so a team-scoped token (Scope > team > All Projects) is the documented minimum; whether a project-scoped token works for Sandbox is not documented. No finer permissions exist on access tokens.

Sources: [vercel.com: authentication](https://vercel.com/docs/sandbox/concepts/authentication), [vercel.com: access tokens](https://vercel.com/docs/accounts/access-tokens), [vercel.com: pricing](https://vercel.com/docs/sandbox/pricing).

## Limits

* Max session duration: Hobby 45 min, Pro/Enterprise 24 h; default timeout 5 min, extendable via extendTimeout(); limit is per session, resets on stop/resume. ([source](https://vercel.com/docs/sandbox/pricing))
* Max per sandbox: Hobby 4 vCPU/8 GB, Pro 8 vCPU/16 GB, Enterprise 32 vCPU/64 GB; 64 GB disk; 2 GB RAM per vCPU. ([source](https://vercel.com/docs/sandbox/pricing))
* Concurrent sandboxes: Hobby 10, Pro/Enterprise 10,000; Hobby creation pauses once monthly quota is used. ([source](https://vercel.com/docs/sandbox/pricing))
* Available in 19 regions, default iad1. Architecture not documented. ([source](https://vercel.com/docs/sandbox/pricing))

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