Vercel

About

Vercel is the frontend cloud platform built around the Next.js framework. Founded in 2015 by Guillermo Rauch as ZEIT, the company rebranded to Vercel in April 2020 alongside the launch of Next.js 9.4. Vercel raised a $250M Series E at a $3.25B valuation in 2024 and crossed an estimated $200M+ ARR by mid-2025.

The platform is the deployment target for a majority of Next.js production apps and competes with Netlify, Cloudflare Pages, AWS Amplify, and (at the enterprise tier) directly with hyperscaler PaaS offerings.

Pricing is one of Vercel’s most-discussed product surfaces — partly because it’s structurally complex (eight billing dimensions on Pro), partly because real bills routinely exceed the $20/seat headline by 5–15x.

Pricing summary : Hybrid seats plus eight metering dimensions

Vercel uses a hybrid model with two dimensions at the plan level, but eight metering dimensions within the Pro tier:

1. Platform access (seat-based): $20 per developer/month on Pro.
2. Infrastructure consumption (multi-dimensional metering): every Pro team gets a $20 monthly usage credit that absorbs overages across bandwidth, edge requests, function invocations, CPU, memory, image optimization, and builds.

What makes this different: Most PaaS competitors (Netlify, Cloudflare Pages) bundle infrastructure into seat fees or meter on 2–4 dimensions. Vercel exposes 8 dimensions, which gives precise alignment to infra costs but creates real bill-prediction difficulty for users.

See the three-plan grid at the top of this page for the core platform tiers. v0 is a separately-billed product — see the v0 sub-section under Pricing by product for its own plan grid.

Pricing by product

Core platform (Hobby, Pro, Enterprise)

Sales motions across products: self-serve PLG for Hobby and Pro; sales-led for Enterprise.

Pro plan: every billing dimension

The $20 monthly usage credit absorbs overages in a fixed priority order: bandwidth first, then edge requests, then function invocations. Once the $20 credit is depleted, additional usage bills at the rates above.

Default spending cap: every new team has an on-demand usage budget of $200/month (customizable). Email, web, and SMS notifications fire as the cap is approached.

Fluid Compute + Active CPU pricing

Vercel’s flagship pricing innovation. Released February 2025 with time-based billing; switched to Active CPU billing in June 2025.

The mechanic: Fluid Compute lets a single function instance handle multiple concurrent requests. Active CPU billing only meters CPU-active milliseconds — the time your code is actually executing, not the time it spends waiting for I/O.

Example impact:

• AI inference call: 50ms compute + 950ms model wait → billed for 50ms (95% savings)
• Database query: 20ms compute + 480ms query wait → billed for 20ms (96% savings)
• Pure-compute function: 100ms compute, no I/O → billed for 100ms (no change)

Vercel publicly cites up to 90% savings for I/O-heavy workloads. This is the first Active CPU billing model from a major PaaS provider.

v0 (AI UI generator) — separately billed

v0 is Vercel’s AI UI generator, billed as a distinct product:

Per-model token pricing (May 2026):

Zero markup policy: Vercel’s AI Gateway passes through token costs without markup, including for bring-your-own-key. This is notably distinct from competitors that bundle inference into seat fees with implicit markup.

Hidden costs : Why the $20-per-seat headline becomes $400-plus

The $20/seat headline understates real bills by 5–15x at moderate traffic. Two real-world examples:

Medium-traffic Next.js app (500k MAU)

A “$20 plan” that actually bills $481/month. The Active CPU savings (~95% on AI inference routes) materially shifted this number — the same workload billed wall-clock would be ~$900. See our Vercel pricing calculator to model your own usage.

Small SaaS app (50k MAU)

For small apps Vercel stays cheap. The cliff hits between 250k and 1M MAU — exactly where Pro→Enterprise pricing conversations get hard. Bill predictability in usage-based pricing is the unsolved problem here.

Estimate your own bill: Vercel pricing calculator — model traffic, function workload, and Fluid Compute savings interactively.

Pricing evolution : From wall-clock to Active CPU billing

Cadence

Tracked range: 2020 Q2 (Vercel rebrand) – 2026 Q2. Quarters not listed above were verified stable (0 changes, 0 additions).

Notable changes

• 2020-04 — ZEIT rebrands to Vercel alongside Next.js 9.4 launch. Pro at $20/seat with bundled allocations.
• 2024-04 — Granular per-dimension metering replaces coarse bundled allocations. Now bills separately on bandwidth, edge requests, function invocations, CPU hours, memory GB-hours, image optimization, build minutes. Headline price unchanged.
• 2025-02-12 — Fluid Compute execution model launches. Single function instance handles multiple concurrent requests. Initial billing still time-based.
• 2025-06-12 — Active CPU pricing for Fluid Compute. Only CPU-active milliseconds are billed; I/O wait time costs $0. Up to 90% reduction on I/O-heavy workloads (AI inference, database queries).
• 2025-09-15 — Pro plan adds a $20 flexible spending credit that absorbs overages in priority order (bandwidth → edge requests → function invocations). Several Enterprise-only features pushed down to Pro.
• 2026-03 — v0 launches three model tiers (Mini, Pro, Max) with explicit per-million-token rates. Zero-markup AI Gateway policy formalised — token costs pass through at AI Gateway cost, including bring-your-own-key.

What’s unique : Active CPU, zero-markup AI Gateway, separate v0 billing

1. Eight metering dimensions on one plan. No other PaaS exposes this many axes. Aligns billing precisely to infrastructure cost — and creates the prediction-difficulty complaint that defines Vercel’s pricing reputation.

2. Active CPU is a category-first. Charging $0 for I/O wait is unusual enough that no major competitor offered it as of mid-2026. The savings are real, but they require a Fluid Compute architecture.

3. Priority-ordered credit absorption. The $20 credit absorbs overages bandwidth → edge requests → functions in a fixed order. This is the kind of unglamorous mechanic that materially affects budget planning, and Vercel publishes the order clearly.

4. Zero-markup AI Gateway. v0’s published commitment to pass through AI Gateway tokens at cost (including BYOK) is rare. Most AI-feature-bundled SaaS marks up inference 1.5–3x.

5. Separate v0 billing. v0 is its own product with its own plans — Vercel resisted the temptation to bundle AI UI generation into Pro. This preserves clean unit economics on both sides.

Strengths & weaknesses

Billing UX : Spending caps, multi-channel alerts, priority-ordered credits

• Real-time usage dashboard with per-dimension breakdown.
• Default $200 on-demand budget on every new team — customizable.
• Multi-channel alerts (email, web push, SMS) as caps approach.
• Per-project spending visibility for teams.
• Hard spending cap option blocks deploys/serves once hit (rare for production).
• Pro plan credit priority order published in docs — bandwidth → edge requests → functions.

Strategic wins : The category-defining moves and the principles behind them

1. Active CPU billing is a real customer-friendly innovation

Charging $0 for I/O wait is the kind of pricing move that should be obvious in hindsight but wasn’t. Vercel ate margin (the wait time was previously billed) in exchange for category-defining trust. Every PaaS that follows now has to defend why they’re billing wall-clock.

2. Zero-markup AI Gateway is a defensible moat

For a falling-commodity input like AI tokens, marking up the underlying cost is a race to the bottom. Vercel passing through at cost (including BYOK) means they compete on UX, latency, and developer experience — not arbitrage. Compare to competitors with implicit 2-5x token markups.

3. Priority-ordered credit absorption is honest

Publishing the order (bandwidth → edge requests → function invocations) for how the $20 credit absorbs overages is a small UX detail that builds trust. Most vendors leave this opaque.

4. Separate v0 billing prevents bundling rot

Vercel resisted the obvious move of bundling v0 into Pro. That would have boosted Pro ARPU short-term but destroyed the unit economics on both products. Maintaining clean per-product P&L preserves optionality.

Areas to improve : Calculator, mid-tier, dimension grouping, spend projections

1. Lead with TCO scenarios, not plan cards

The pricing page shows the 3 plans without surfacing the real bill for archetypal users. A “medium-traffic Next.js app” archetype showing “$20 base + ~$400 typical usage = ~$420/month” would set expectations honestly. Today the $20-vs-$481 gap is the source of every “my $20 plan cost me $286” blog post.

2. Build a public Pro/Enterprise calculator

Vercel ships in-product spend dashboards but no public calculator that lets prospects model their bill before signing up. Every other multi-dimensional PaaS in 2026 (Cloudflare, Railway, Render) ships one. Adding a comparable calculator on the pricing page itself would cut the time-to-clarity for buyers from days to minutes.

3. Add a mid-tier between Pro and Enterprise

The gap is wide: Pro is $20/seat + usage; Enterprise typically starts $20k–$45k/year. Companies between these — say, $500/month spend with SSO and committed-use discount needs — have no good fit. A “Team Plus” tier at ~$200/team/mo with SSO + 10% committed-use discount + audit logs would unlock the missing market segment.

4. Reduce dimension count or improve grouping

Eight billing dimensions is too many to reason about. Group them into 3 logical buckets — Delivery (bandwidth + edge requests), Compute (functions + CPU + memory), Assets (images + storage + builds) — with a single overage credit per bucket. The total bill stays the same; cognitive load drops materially.

5. Spend projections, not just dashboards

The current dashboard shows what you’ve spent. It doesn’t project what you’ll spend at current trajectory. A “your projected month-end bill: $X (currently $Y)” projection — emailed weekly — would prevent ~80% of bill-shock churn cases.

Key takeaways

1. Multi-dimensional metering accurately reflects cost — and confuses customers. Pick a number of dimensions a finance person can reconstruct in a spreadsheet (3, maybe 4). Beyond that, you need a calculator and projection tooling AS A PRODUCT FEATURE, not a footer link.
2. Active CPU is now the bar. Charging for I/O wait time on serverless is increasingly defensive. Vercel changed the category.
3. Zero markup is defensible when the underlying input is a falling commodity. AI tokens, bandwidth, storage — all candidates. Don’t lock yourself into a margin you can’t defend.
4. Publish your credit absorption rules. Small UX detail, outsized trust impact. Customers don’t trust math they can’t reproduce.
5. Resist the bundling temptation. v0 separate from core Vercel preserves unit economics on both. Every “we’ll bundle this for revenue acceleration” move usually destroys two P&Ls.

UBP implications

1. Multi-dimensional metering needs really good prediction tooling. Vercel’s 8 dimensions are accurate to cost but unfriendly to budgeters. The lesson: if you bill on more than 3 dimensions, you must ship a top-tier cost calculator AND in-product spend projections.
2. Active CPU is a viable “fairness” innovation. Charging only for active compute aligns customer cost with vendor cost very tightly. If your product has natural I/O wait, this is a powerful pricing differentiator.
3. Zero-markup gateways are a defensible position. When the underlying commodity (AI tokens) has falling per-unit cost, marking it up locks you out of price competition. Vercel’s pass-through gives v0 room to compete on UX while leaving margin to the platform layer.
4. Credit pools with priority order are operationally legible. Telling users exactly how a credit will be consumed is friendlier than opaque absorption. This is a small UX detail with outsized trust impact.

Sources

• Vercel official pricing page (accessed 2026-05-23)
• Vercel functions usage and pricing docs (accessed 2026-05-23)
• Active CPU pricing changelog (accessed 2026-05-23)
• Vercel AI Gateway pricing docs (accessed 2026-05-23)
• v0 pricing page (accessed 2026-05-23)
• Vercel changelog (accessed 2026-05-23)

Bottom line

Vercel’s pricing is the most accurate reflection of frontend-cloud infrastructure cost in 2026 — and the hardest to predict before you sign up. Active CPU billing and zero-markup AI Gateway are category-defining wins. Eight billing dimensions and the missing mid-tier are unforced errors. The platform’s job over the next year is to ship the prediction tooling that makes the accuracy tractable for budgeters.

Want to compare Vercel against other frontend cloud and PaaS pricing? Browse the pricing blueprint.

Pricing timeline : Major events on a vertical axis

Each milestone below corresponds to a public pricing change, product launch, or material adjustment. Major events use a filled marker; minor adjustments use a faded one.

v0 Three-Tier Model Lineup

Mar 2026

v0 launched Mini / Pro / Max model tiers with explicit per-million-token pricing. Zero markup policy on AI Gateway tokens formalized.

Credit-Based Pro Plan Restructuring

Sep 2025

Pro plan added a $20 flexible spending credit that absorbs overages across dimensions. Several previously Enterprise-only features moved down to Pro.

Active CPU Pricing for Fluid Compute

Jun 2025

Switched Fluid Compute to 'Active CPU' billing — I/O wait time is free, only CPU-active milliseconds count. Up to 90% savings for I/O-heavy workloads.

Fluid Compute Launch

Feb 2025

Introduced 'Fluid Compute' execution model with built-in concurrency that allows a single function instance to handle multiple requests. Initial billing still time-based.

Granular Metering Rollout

Apr 2024

Moved from coarse bundled allocations to per-dimension metering (separate prices for bandwidth, edge requests, function invocations, CPU, memory). Aligned pricing with infrastructure cost.

Rebrand to Vercel + Team Pricing

Apr 2020

Company renames to Vercel. Introduces Pro plan at $20/seat with bundled bandwidth and serverless allocations.

ZEIT Now Launches (Vercel's Predecessor)

Apr 2017

Founded by Guillermo Rauch as ZEIT, launched 'Now' as serverless deployment platform with per-second billing for compute.