ViteHub
ViteHub is still experimental. Expect bugs and breaking changes.

Vercel

Generate Vercel Provider Output while preserving ViteHub package boundaries.

Vercel is a Provider Selection for packages that can emit Vercel Build Output, functions, queues, workflows, blob-backed storage, or sandbox integration. ViteHub keeps Definitions portable and moves Vercel-specific behavior into package Integration Options and Provider Output.

Vercel boundaries

ConcernViteHub boundary
Build OutputGenerated .vercel/output/** files written by package integrations.
Vercel BlobBlob Store or Workspace Store configuration, depending on which primitive owns the behavior.
Vercel QueuesQueue provider configuration and generated callback output.
Vercel WorkflowWorkflow provider configuration and generated runtime output.
Vercel SandboxSandbox Provider configuration, with Sandbox Identity passed only when the run needs reuse.
CredentialsVERCEL_TOKEN and optional team id for Provision; Server Env for app runtime secrets.

Configure package options

Select Vercel in the package that owns the primitive. Do not move provider fields into runtime invocation input when they affect generated output.

vite.config.ts
import { hubBlob } from '@vite-hub/blob/vite'
import { hubQueue } from '@vite-hub/queue/vite'
import { defineConfig } from 'vite'

export default defineConfig({
  plugins: [
    hubBlob(),
    hubQueue(),
  ],
  blob: {
    driver: 'vercel-blob',
  },
  queue: {
    provider: 'vercel',
    region: 'iad1',
  },
})
Vercel-hosted state needs hosted stores. Use driver: 'vercel-blob' with BLOB_READ_WRITE_TOKEN for Blob, and use Upstash-backed KV with KV_REST_API_URL and KV_REST_API_TOKEN when KV runs on Vercel. Local filesystem stores are development-only in Vercel deployments.

Provision resources

Run a dry run before applying actions. Use VERCEL_TEAM_ID or VERCEL_ORG_ID when the token needs a team scope.

Terminal
pnpm vitehub provision run --provider vercel --dry-run
VERCEL_TOKEN=... VERCEL_TEAM_ID=... pnpm vitehub provision run --provider vercel

Inspect output

Vercel output appears under .vercel/output. Server functions include their own .vc-config.json, while the root output config describes routing and build metadata.

Terminal
pnpm build
find .vercel/output -maxdepth 4 -type f | sort

Production notes

Vercel provider output should make provider-specific runtime packages reachable only when selected. If a build bundles an unselected provider dependency, treat that as a Provider Output Contract issue in the owning package.

Agent Definitions can run on Vercel through the Agent Package's Vercel handler, or through generated host output where the Agent integration owns that route. Keep model keys, state credentials, and other Runtime Env in Vercel environment variables.

Next steps

Copyright © 2026