Vercel

Vercel manages builds, deployments, delivery, functions, and platform services. It does not own the application's database, third-party service reliability, architecture, or portability, and support varies by framework and runtime feature. Vercel environment variables are a platform-local configuration boundary, not a standalone secrets-management product; the application still owns creation, distribution, rotation, revocation, audit, and exit beyond Vercel.¹²⁵⁶

For: Web teams prioritizing preview deployments and managed delivery, especially for Next.js applications

• The workload needs long-running, stateful, or privately networked server processes.
• The organization needs infrastructure control beyond Vercel's managed runtime configuration.
• Projected multi-product usage makes another hosting model more predictable.

• Preview deployment workflowChanges can receive isolated deployment URLs for review before production.¹
• Framework integrationVercel provides first-party deployment behavior for Next.js and support for other web frameworks.⁴
• Managed functionsServer-side code can run as managed functions that scale with demand under documented runtime rules.²⁶
• Integrated deliveryBuild, deployment, routing, caching, and managed infrastructure usage are operated through one platform.¹

Plans combine team or developer-experience packaging with managed-infrastructure usage. Billable resources can include seats, builds, requests, transfer, active CPU, provisioned memory, invocations, image work, storage, and observability.³

Compute dimensions

Active CPU, provisioned memory, and invocations for current fluid compute³

Workload variables

Requests, transfer, compute, memory, invocations, builds, storage, images, observability, and add-ons³

Cost boundary

Managed infrastructure and developer-experience resources use different billing models³