ViteHub

Vercel Sandbox

Configure @vitehub/sandbox to execute definitions through Vercel Sandbox.

Use the Vercel provider when sandbox execution should run through Vercel Sandbox.

Vercel needs the @vercel/sandbox package and project credentials. Credentials can come from environment variables or explicit provider config.

Install the provider SDK

pnpm add @vercel/sandbox

Configure Sandbox

Register the Vite plugin and set sandbox.provider to vercel:

vite.config.ts
import { defineConfig } from 'vite'
import { hubSandbox } from '@vitehub/sandbox/vite'

export default defineConfig({
  plugins: [hubSandbox()],
  sandbox: {
    provider: 'vercel',
  },
})

Add credentials

Set the plain Vercel environment variables:

VERCEL_TOKEN=<vercel-token>
VERCEL_TEAM_ID=<vercel-team-id>
VERCEL_PROJECT_ID=<vercel-project-id>

Framework-prefixed names are also supported:

RuntimeTokenTeamProject
NitroNITRO_SANDBOX_TOKENNITRO_SANDBOX_TEAM_IDNITRO_SANDBOX_PROJECT_ID
NuxtNUXT_SANDBOX_TOKENNUXT_SANDBOX_TEAM_IDNUXT_SANDBOX_PROJECT_ID
ViteVITE_SANDBOX_TOKENVITE_SANDBOX_TEAM_IDVITE_SANDBOX_PROJECT_ID

You can also pass credentials in config:

sandbox: {
  provider: 'vercel',
  token: process.env.VERCEL_TOKEN,
  teamId: process.env.VERCEL_TEAM_ID,
  projectId: process.env.VERCEL_PROJECT_ID,
}

Tune Vercel options

sandbox: {
  provider: 'vercel',
  runtime: 'node22',
  timeout: 30_000,
  cpu: 2,
  ports: [3000],
}
OptionDescription
runtimeVercel sandbox runtime image. Use node22 or node24.
timeoutExecution timeout in milliseconds.
cpuCPU allocation passed to Vercel Sandbox.
portsPorts exposed by the sandbox when needed.
sourceVercel sandbox source configuration.
networkPolicyVercel sandbox network policy.

Verify the provider

Call a known sandbox route:

curl -X POST http://localhost:3000/api/release-notes \
  -H 'content-type: application/json' \
  -d '{"notes":"- Added Vercel provider"}'

Successful execution returns a normal Sandbox result:

{
  "result": {
    "summary": "Added Vercel provider",
    "items": [
      "Added Vercel provider"
    ]
  }
}

Common failures

SymptomCauseFix
Sandbox provider could not be inferredNo provider was configured and Vercel was not detected.Set sandbox.provider to vercel.
Vercel sandbox cannot create a runtimeCredentials are missing or incomplete.Set token, team ID, and project ID through env vars or config.
Provider package warning during build@vercel/sandbox is not installed.Run pnpm add @vercel/sandbox.
Copyright © 2026