vercel.md

description	Set up the Vercel provider for ComputeSDK, configure project credentials or OIDC auth, and create sandboxes to run commands.
layout	width title description tableOfContents outline pagination metadata tags actions default visible true visible visible true visible true visible true visible true visible true visible true
tags	tag primary benchmarked true

Vercel

{% embed url="https://www.computesdk.com/benchmarks/sandboxes/vercel/" %}

Vercel provider for ComputeSDK - Execute code in globally distributed serverless environments.

Installation & Setup

npm install @computesdk/vercel

Add your Vercel credentials to a .env file:

VERCEL_TOKEN=your_vercel_token
VERCEL_TEAM_ID=your_vercel_team_id
VERCEL_PROJECT_ID=your_vercel_project_id

Usage

import { vercel } from '@computesdk/vercel';

const compute = vercel({
  token: process.env.VERCEL_TOKEN,
  teamId: process.env.VERCEL_TEAM_ID,
  projectId: process.env.VERCEL_PROJECT_ID,
});

// Create sandbox
const sandbox = await compute.sandbox.create();

// Run a command
const result = await sandbox.runCommand('echo "Hello from Vercel!"');
console.log(result.stdout); // "Hello from Vercel!"

// Clean up
await sandbox.destroy();

Configuration Options

interface VercelConfig {
  /** Vercel token - if not provided, will use env vars */
  token?: string;
  /** Team ID for team accounts */
  teamId?: string;
  /** Project ID */
  projectId?: string;
  /** Execution timeout in milliseconds */
  timeout?: number;
  /** Ports to expose on the sandbox */
  ports?: number[];
  /** Port for the daemon SSE channel (defaults to 38989); set false to disable */
  daemonSsePort?: number | false;
}

Authentication

When no credentials are provided in config (no token, teamId, or projectId), the provider falls back to OIDC authentication using the VERCEL_OIDC_TOKEN environment variable. Run vercel env pull to populate VERCEL_OIDC_TOKEN in your .env file. This is an alternative to the token-based authentication shown above.