Vercel — Library index

Canonical reference for Vercel — the frontend cloud / “AI cloud” — covering the deployment platform (projects, previews, production, Skew Protection, Rolling Releases, Instant Rollback), the Vercel Delivery Network and its 126+ POPs, Vercel Functions (Fluid Compute, Edge vs Node.js, Routing Middleware), the Vercel AI SDK (Core + UI + RSC + provider plugins), storage products (Blob, Edge Config, Marketplace databases), Observability + Speed Insights, Cron Jobs, and v0. Companion sub-library to _index (the other major edge platform) and _index / _index (the model providers behind most Vercel AI apps).

Vercel is the path of least resistance for shipping a Next.js / Astro / SvelteKit / Nuxt application — git push triggers a build, every push gets a preview URL, production is one promote away. The platform’s defining shift in 2024-2025 was the Fluid Compute concurrency model: Vercel Functions can now share a single instance across concurrent requests (vs Lambda’s one-request-per-instance), eliminating most cold-start pain and changing the cost equation for AI / I/O-bound workloads. Combined with the AI SDK (the most-used TypeScript LLM toolkit), Vercel positions itself less as “frontend hosting” and more as “the place you ship AI-powered web apps”.

This sub-library lives inside Math-and-Compute/Compute/ alongside the other vendor sub-libraries. Notes are version-pinned to 2026-05-25. Vercel ships features weekly and renames things often (vercel.json configurations migrate, runtime names change — nodejs20.xnode22, edge runtime semantics shifted in 2024) — verify against vercel.com/docs before quoting specific syntax.

See also

  • _index — the other major edge platform; many design patterns transfer
  • microservices-patterns — Vercel Functions implement many serverless patterns
  • observability-stack — what Vercel Observability does under the hood (OpenTelemetry)
  • _index — Anthropic’s Claude is the most-used model with the AI SDK
  • _index — Bedrock is a provider in the AI SDK

Library contents

Foundations

FileWhat it covers
vercel-platform-and-deploymentsProjects, deployments, environments (Production / Preview / Custom), Git integration, Skew Protection, Build Cache, Rolling Releases, Instant Rollback, Deployment Protection, Monorepo (Turborepo) support
vercel-edge-network-and-functionsThe Vercel Delivery Network — 126+ POPs, regions, ISR, caching tiers, Image Optimization. Vercel Functions — Fluid Compute, runtime options (Node.js / Python / Edge), regions, memory/CPU configuration, streaming, Routing Middleware

AI

FileWhat it covers
vercel-ai-sdkThe AI SDK — Core (generateText / streamText / generateObject), UI (useChat / useCompletion / useObject), RSC (streamUI for React Server Components), tool definitions, all 16+ provider plugins (Anthropic / OpenAI / Google / xAI / Mistral / Cohere / Groq / Together AI / Fireworks / DeepInfra / Replicate / Amazon Bedrock / Azure / Vertex / Ollama / OpenRouter), AI Gateway

Storage & data

FileWhat it covers
vercel-storage-and-dataVercel Blob (S3-compatible), Edge Config (read-optimized, < 1 ms reads), Marketplace storage (Neon Postgres, Upstash Redis, Supabase, MongoDB Atlas, etc.), the deprecation of native Vercel KV / Postgres in favor of Marketplace

Operational

FileWhat it covers
vercel-observability-and-monitoringObservability (free), Observability Plus (Pro/Enterprise), Speed Insights, Web Vitals, Runtime Logs, OpenTelemetry tracing, integrations (Sentry, Datadog, LogDrains), Spend Management, Notebooks
hidden-tricks-and-gotchas-vercelEdge Function 1MB size limit + 50ms CPU, Serverless cold-start mitigation, middleware cost (runs on every request), ISR / On-Demand Revalidation pattern, image optimization defaults, preview-deployment auth, cron limits per plan, free-tier vs Pro economics, v0 vs Cursor vs Claude tradeoffs

How to use this library

  1. Picking a runtime — start at vercel-edge-network-and-functions for the Edge vs Node.js vs Fluid Compute decision tree.
  2. Building an AI featurevercel-ai-sdk for the SDK; _index / _index / _index for the model provider.
  3. Choosing a databasevercel-storage-and-data catalogs the Marketplace options.
  4. Production debuggingvercel-observability-and-monitoring + hidden-tricks-and-gotchas-vercel for the undocumented escape hatches.
  5. Optimizing spendhidden-tricks-and-gotchas-vercel has the free-tier vs Pro vs Enterprise math, plus Fluid Compute economics.

Conventions used in this library

  • Code examples use TypeScript and Next.js App Router by default (Vercel’s most common deployment shape). Where the API differs in Pages Router or non-Next.js frameworks, this is noted.
  • Pricing is in USD as of 2026-05-25. Where multiple \$ symbols appear on the same line they are backslash-escaped to avoid Obsidian MathJax interpretation.
  • Plan names are capitalized: Hobby (free), Pro ($20/seat/month), Enterprise (custom).
  • “Per vercel.com/docs 2026-05” tags a claim sourced from official documentation as of the file’s created date.
  • Routing rules and middleware examples target Next.js 15+ App Router. Older Pages Router behavior is noted where it diverges.

Sources read while building this library (2026-05-25 pass)

  • vercel.com/docs (root)
  • vercel.com/docs/cdn (CDN overview)
  • vercel.com/docs/functions (Vercel Functions)
  • vercel.com/docs/fluid-compute (Fluid Compute)
  • vercel.com/docs/ai-sdk (AI SDK)
  • vercel.com/docs/ai-gateway (AI Gateway)
  • vercel.com/docs/storage (Storage overview)
  • vercel.com/docs/vercel-blob
  • vercel.com/docs/edge-config
  • vercel.com/docs/observability
  • vercel.com/docs/cron-jobs
  • vercel.com/docs/git
  • vercel.com/docs/deployment-protection
  • vercel.com/docs/incremental-static-regeneration
  • vercel.com/docs/image-optimization
  • sdk.vercel.ai/docs (AI SDK reference)
  • v0.app/docs (v0)
  • github.com/vercel/ai (AI SDK source)
  • github.com/vercel/next.js (Next.js — Vercel’s flagship framework)

Where official docs are silent but behavior is observable (cold-start dynamics in different regions, exact CPU budget for middleware, edge function instance reuse), entries are labelled “Undocumented as of 2026-05-25 — observed behavior” so a future reader knows to verify.