Vercel Pro plan in 2026: what it really costs

TL;DR: Vercel Pro costs $20 a month per deploying seat, and the whole team shares one $20 usage credit. For a small app that's $20 for one person, $40 for two and about $104 for five. Traffic past the included CDN tier and busy build queues push five people to $126 to $210.

• The credit: $20 per team, not per seat. At five seats, builds alone use it up.
• Overages: extra seats, metered usage past the credit, a higher CDN tier, builds, add-ons and bot traffic.
• Capping the bill: possible for metered usage only, and the cap works by pausing production.
• Pick Vercel Pro if you're one or two developers with modest traffic, or you need free read-only seats for clients.
• Pick your own server with Ployz, which I build, if you're three or more developers. A rented server plus Ployz costs about $16 a month, whatever the team size.

Vercel Pro is Vercel's paid plan for teams: a monthly platform fee that includes one deploying seat and $20 of usage credit, plus $20 for each extra person who can deploy and whatever your traffic costs past that.

This article covers the Pro plan itself: seats, the credit, spend limits and what sends the bill past $20. For a full traffic bill at 100 GB, 1 TB and 5 TB, see my Vercel pricing breakdown.

What does Vercel Pro cost for 1, 2 and 5 people?

For a small app with 50,000 page views a month, Vercel Pro costs $20 for one person, $40 for two and $104 for five. At 250,000 page views it's $40, $60 and $126. At 1 million it's $120, $140 and $210. Seats are a fixed $20 each, builds grow with the team, and the CDN tier grows with traffic.

My assumptions, so you can swap in your own:

• Each developer pushes 5 times per working day, 22 working days a month. Each push builds once, for 3 minutes, on a 4 vCPU machine.
• Elastic builds are the default for new Pro teams. They pick between 4 and 30 vCPUs and bill $0.0035 per CPU minute (managing builds). That's $4.62 of builds per developer a month.
• Pages make 20 CDN requests each and run 30 ms of CPU in one function call.
• Flat Rate CDN is on. It's the default for Pro teams created since 8 September 2026 (changelog).

The credit hides a lot at one or two seats. Builds and functions stay under $20, so you pay only for seats and the CDN tier. At five seats, builds alone ($23.10) use up the whole credit, and everything after that is on-demand. Pinning projects to the 2 vCPU Basic machine halves the build line, at the cost of slower builds.

One caveat: the pricing page lists "10M / month" CDN requests for Pro, while the Pro plan docs say the included tier is 1M. I used the docs. If 10M is right, the 250k page view rows drop by $20.

Move the sliders to match your team and your app. The per-page compute matches my Vercel pricing reference app: 30 ms of CPU, 250 ms wall time at 2 GB, and 1 MB per page.

What's in the Pro plan price?

The $20 platform fee includes one deploying seat and $20 of usage credit. On top of that you pay $20 for each extra deploying seat, your Flat Rate CDN tier, and any metered usage past the credit. Billing is monthly only, by card.

Billing rules the pricing page doesn't spell out, all from the Pro billing FAQ:

• Seats and add-ons are charged in advance "for the next 30 days". Usage is charged in arrears for the last 30 days.
• Annual billing is Enterprise only.
• If a renewal payment fails, "payment must be successfully made within 14 days, else all deployments on your account will be paused."
• A big month can bring a partial invoice before the cycle ends, if your usage crosses a billing threshold.

Paid Pro teams also get one free first-year domain on TLDs such as .dev and .app (Pro plan).

What does the $20 usage credit cover?

The credit pays for Vercel's metered infrastructure from the first unit: functions, origin transfer, image optimization, builds, ISR and so on. It expires at the end of each month. It doesn't pay for seats, add-ons or the Flat Rate CDN tier.

It's one credit per team. "Every Pro plan has $20 in monthly credit," say the Pro plan docs, and the platform fee is the line that "includes $20 in usage credit". Extra seats are $20 each with no credit attached, so the fifth seat costs a full $20 while your usage headroom stays the same.

Vercel emails you at 75% of the credit. Once you pass it, "Vercel switches your team to on-demand usage" and sends daily and weekly summaries (Managing your spend).

How far $20 goes, at Washington D.C. (iad1) rates, the cheapest region (iad1 pricing, builds):

The pricing page also lists Pro usage as "included" (1M function invocations, 5K image transformations and so on). Read those as things the credit pays for, not as separate free buckets.

Who needs a paid seat on Vercel Pro?

Anyone who can deploy needs a paid seat. On Pro that means Owners and Members, which the pricing page calls a "Developer seat". Viewers are free: they can open deployments, read analytics and comment on previews, but "cannot configure or deploy projects." One Billing member is also free.

The free Viewer seat arrived with the September 2025 Pro plan change, which also introduced the $20 credit. Before that, a designer or client who wanted to look at previews was another paid seat. Today a founder, a PM and three clients can watch for free.

Viewers have limits, though. Pro Viewers can't see logs, observability data, team settings, or detailed usage and billing (Pro Viewer role). Anyone who needs to read logs while debugging needs a deploying seat.

How does Flat Rate CDN change the Pro bill?

Flat Rate CDN replaces per-GB and per-request charges with a fixed tier. For most apps, requests decide the tier, and the tier becomes the biggest line after seats.

The tier is a team-wide subscription, so seats don't change it. It isn't paid from the $20 credit, and spend management doesn't cover it. A one-day spike doesn't move you up a tier; a whole month over capacity does, from the next cycle. Past 150M requests you're back on on-demand pricing.

I compare Flat Rate with on-demand at 100 GB, 1 TB and 5 TB in the Vercel pricing article. The short version: under about 200 GB, on-demand can be cheaper.

What triggers overages on Vercel Pro?

Six things push the bill past $20 a seat: a new deploying seat, metered usage past the credit, a month over your CDN tier, builds, paid add-ons, and traffic Vercel doesn't block, such as bots. Only metered usage counts toward spend management.

Builds are the line teams miss. Pro allows up to 500 concurrent builds with on-demand concurrency on, and "you are billed for the build minutes you use" (concurrency limits). Every push to every pull request is a build, so build cost grows with how often people push, not only with headcount.

Password protection is the surprise for agencies. If every client preview needs a password, that's $20 per protected project, every month.

Can you cap your Vercel Pro bill?

Partly. Spend management lets you set an On-Demand Budget, and if you turn on Pause Production Deployments, Vercel pauses every project when you reach it. Visitors then get a 503. Seats, add-ons and the CDN tier sit outside the budget.

The rules, from the spend management docs:

• "Setting a spend amount does not stop usage on its own." You have to switch on pausing.
• New teams get spend notifications at $200 by default, and a notification stops nothing.
• The budget covers only "metered usage that goes beyond your Pro plan monthly credit." It "does not include seats, integrations (such as Marketplace), or separate add-ons."
• Vercel checks spend "every few minutes", so you can go over before anything fires. Vercel suggests setting the budget below your true maximum.
• Pausing stops production for all projects at once. It doesn't stop AI Gateway or v0 usage billed to the team.
• Raising the budget doesn't unpause anything; you resume each project by hand.
• Notifications go out at 50%, 75% and 100% of the budget, and a webhook can fire at the same points.

So a real cap means choosing between a bill and an outage. For a side project that's easy. For a business, pausing all of production because a crawler hit you is rarely what you want.

Is Vercel Pro worth it for a team?

For one person with a small commercial app, yes: $20 a month for preview deployments, a global CDN and no servers is fair. For a team of three or more, I don't think so. Five developers pay $100 a month before any traffic, while the same app on a rented server with Ployz costs about $16 a month with no seat count.

The $16 in the tables is a Hetzner CX23 with its IPv4 address plus $9 a month for custom domains on Ployz Cloud. Hetzner's prices are after its 15 June 2026 increase. In the US, Netcup's VPS 500 in Manassas plus custom domains comes to about $20.

What you give up for that price:

• No global CDN. One server serves from one city.
• No free Viewer seats. Preview environments get their own HTTPS address, so you can still send a client the link.
• Builds share the box. Five busy developers mean builds compete with your app for CPU. A CX33, a second server, or building in your own GitHub Actions fixes that.
• Upkeep is yours. OS updates and database backups are your job.

For how Vercel's seat rules compare with other platforms, see PaaS pricing.

Where Ployz fits

Ployz turns a server you rent into a platform with the Vercel workflow you'd miss: push to GitHub and it builds and deploys, and every pull request gets a preview environment at its own HTTPS address.

ployz up --server root@your-server

That installs Ployz on a Linux server with systemd, builds the current directory and gives it an HTTPS address.

What it does for a team that's tired of seat pricing:

• No per-seat fee. Deploys come from GitHub pushes, so anyone who can push to the repo ships. Ployz is free on your own servers, with unlimited projects and preview environments.
• Builds where you want them. On your server, or in your own GitHub Actions with one workflow file, with no registry to run. Node, Python, Ruby, PHP, Go, Rust, Java and Elixir need no Dockerfile.
• Zero-downtime deploys once you set a health check: a new replica must answer it before an old one stops.
• Coding agents can drive it. Every command takes --json, and ployz setup agent lets Claude Code deploy for you.

What it doesn't do yet: there are no teams or roles, so one person signs into the dashboard per organization. There's no global CDN, no backups and no rollbacks. If clients need read-only dashboard access or your visitors are spread worldwide, Vercel Pro covers that today.

Start free on your own server.

FAQ

Is there a free trial of Vercel Pro?

Yes, 14 days, one per user account, with a $20 credit. It ends early at 16 CPU-hours of Active CPU, 1,440 GB-hours of memory or 1M function invocations. It allows one Owner and 10 members in total. Without a card on file, the team falls back to Hobby and every member is removed. The free first-year domain, drains and account webhooks aren't available during the trial, and you can't change Owners until you're on a paid plan (trial docs).

What happens when you downgrade Vercel Pro to Hobby?

"All active members except for the original owner are removed" (downgrading). If you want to know what Hobby allows before you go back, I covered it in is Vercel free.

Can you pay for Vercel Pro annually?

No. Pro is billed monthly, by card. Annual billing is Enterprise only (billing FAQ).

How I checked

I checked every price and rule on 2026-10-01 in Vercel's own docs, linked next to each number. Vercel bills in USD before tax. Where usage is priced by region, I used Washington D.C. (iad1), the cheapest one. The 1, 2 and 5 seat bills are my arithmetic on the assumptions listed above, not real invoices. Server prices come from Netcup's and Hetzner's own price pages. I build Ployz, so weigh the "Where Ployz fits" section with that in mind; the Vercel numbers don't depend on it.

Deploy your app on your own server with Ployz, free, with no seat count: get started.