Vercel Cost for a Small Team: 1, 3, 5 and 10 Seats

There are three parts to it. The platform fee is $20 a month, which includes one deploying seat and $20 of usage credit, and every extra deploying seat adds $20 more. Usage is then metered on top, and the first $20 of it is covered by the credit.

The credit belongs to the team rather than the seat, and it expires at the end of the month if you do not use it, so ten seats do not get ten credits. That is why the seat count dominates the Vercel cost until traffic is high.

Assumptions first: every seat deploys, so every seat is paid, and nobody buys an add-on. The formula is seats times $20, plus any usage above the $20 credit. I have used three usage levels: usage worth $15 (inside the credit), $60 and $200 at Vercel's on-demand rates. These usage figures are illustrations rather than measurements of any real site, and your own usage page will tell you where you sit.

Check one cell. Five seats is 5 x $20 = $100. Usage of $60 less the $20 credit leaves $40 on demand. The bill is $100 + $40 = $140.

Read down a column and the seats add a straight line, and read across a row and usage adds on top of it. For a team under five people with a modest site, the whole Vercel cost is usually the seat line and nothing else.

No, because Vercel's docs give Pro unlimited free Viewer seats. A viewer can see deployments and analytics and comment on previews, but cannot configure or deploy projects. Take ten people where four ship code and six only review, and the seat cost is 4 x $20 = $80 rather than $200.

Count who deploys, not who is on the team, because designers, product managers and clients who only read previews are the obvious viewers.

Usage is priced by region, and Vercel publishes a range for each resource. Here is what the ranges mean on invented but plausible volumes. Each line is a worked example you can redo.

• Function compute: active CPU is $0.128 to $0.221 an hour depending on region, so a month of 150 active CPU hours is 150 x $0.128 = $19.20 at the low end and 150 x $0.221 = $33.15 at the high end, and provisioned memory is extra at $0.0106 to $0.0183 per GB-hour.
• Image optimisation: transformations are $0.05 to $0.0812 per 1,000, so a site that makes 200,000 of them in a month pays 200 x $0.05 = $10.00 to 200 x $0.0812 = $16.24.
• Data transfer: on demand, Fast Data Transfer is $0.15 to $0.35 per GB, so moving 500 GB costs 500 x $0.15 = $75 to 500 x $0.35 = $175 if nothing else covers it.
• Add-ons: Password Protection is $20 a month per protected project, so three projects is $60, while Preview Deployment Suffix is $100 a month and SAML single sign-on is $300 a month, and none of them counts towards a spend cap.

None of these is unreasonable alone, but a busy month can add two or three of them at once, on top of a seat bill that never moves, and that is when the Vercel cost surprises people.

Team A has three developers and two people who only read previews. It runs a marketing site whose usage stays inside the credit. Seats are 3 x $20 = $60, the two viewers are free, and the bill is $60.

Team B has five developers and three viewers, and it runs a shop with many product images. Assume 300,000 image transformations and 200 active CPU hours in a month, with no data transfer charge because it sits inside its Flat Rate CDN tier. Images are 300 x $0.05 = $15.00 to 300 x $0.0812 = $24.36. Compute is 200 x $0.128 = $25.60 to 200 x $0.221 = $44.20. Usage totals $40.60 to $68.56, so after the $20 credit the team pays $20.60 to $48.56 on demand.

Seats are between 67 and 83 percent of that bill. Even for a shop with real usage, the Vercel cost is mostly a headcount number, so the cheapest lever is the number of people who need to deploy.

This is the part that changed. Older write-ups, including our own price notes, describe a 1 TB allowance and $0.15 per GB beyond it, whereas today Vercel's Pro docs describe Flat Rate CDN instead, and Pro includes its lowest tier at no extra cost.

If a month goes over capacity, Vercel moves you up a tier at the start of the next billing cycle, and one busy day does not trigger it. Note the request column, because a site with small pages and many hits can outgrow the free tier on requests long before it reaches 1 TB. The per-GB rates above apply if you switch Flat Rate CDN off, and two Vercel pages frame this a little differently, so confirm what your own team is on under Billing.

You have to turn on Pause Production Deployments as well, and then production stops serving traffic when the amount is reached, although Vercel checks only every few minutes, so spend can pass the line first. The cap covers usage above the credit but not seats, integrations or add-ons, which are billed monthly regardless. A cap protects you from a runaway month, but it cannot lower the seat line.

A database. Vercel's docs route Postgres through Marketplace providers such as Neon, Supabase or AWS Aurora Postgres, and say you pay for them through your Vercel account. That keeps the invoice single, but the database has its own price. Our Vercel and Supabase comparison prices that pairing, and the Vercel Pro plan review covers the plan's limits.

For contrast, Helm7 charges no seats. Its Builder plan is a $12 minimum and Pro is a $29 minimum, and each includes Postgres, with usage drawing down against the minimum. That is not a like-for-like swap. Vercel has a large edge network, and Helm7 runs in two EU regions only. See pricing.

It is worth it when the team is small, the app is Next.js, and the time saved is worth the seats. Preview deployments on each pull request are hard to beat, and there is almost nothing to set up. For one to three deployers with a moderate site, the Vercel cost is close to a flat $20 to $60, which is fair.

It stops being an easy yes when seats reach the high single digits, when most of the team only reads previews (use viewers), or when image, function and transfer usage climbs past the credit month after month. At that point compare it with a platform priced on usage alone, such as the ones in Vercel vs Railway, or with other ways to host a Next.js app.