Vercel Pro Pricing 2026: One Month, Three Developers

Vercel Pro pricing changed shape in September 2025, when Vercel moved it to a credit model. The docs now describe a $20 monthly platform fee that includes one deploying seat and $20 of usage credit. Extra seats that can deploy cost $20 each. Read-only viewer seats are free and unlimited.

Enterprise is quoted on request, so there is no published Vercel enterprise pricing to compare.

This is a worked example, not a customer. Three developers, all of whom deploy. A designer and a product manager who only look at previews.

• Platform fee, including the first developer: $20.
• Two more deploying seats: 2 x $20 = $40.
• Designer and product manager as viewers: $0.

That is $60 a month before a single request is served. It is the same as three seats at $20, which is why seat count, not the headline fee, drives a small team's bill.

The app is a Next.js site with server-rendered pages. Assume 1.5 million function invocations in the month, 50 ms of active CPU per request and a 200 ms instance lifetime per request on a 2 GB function. The functions run in the default Washington region, iad1, so the rates are $0.128 per CPU-hour and $0.0106 per GB-hour.

That sits inside the $20 credit, so it adds nothing to the invoice. Vercel bills active CPU only while your code runs, not while it waits on a database, which is a genuine advantage for I/O-heavy pages. Memory keeps billing during the wait, though.

So the credit is not a balance you build up. Unused credit is lost each month, and Vercel sends a notice when usage reaches 75 percent of it. By default, new customers also get a spend alert at $200 per billing cycle. You can set your own threshold, and an automatic action, in the spend management settings.

Say a launch pushes CDN traffic to 5 million requests. The included Flat Rate CDN tier covers 1 million. Vercel says that if your total usage exceeds capacity, it moves you to a higher tier at the start of the next billing cycle, and a one-day spike does not trigger it.

The next tier is $20 a month for 10 million requests and 50 TB of transfer. Above that sit tiers at $100 (50 million requests) and $300 (150 million). Exceed the highest and Vercel moves you to on-demand pricing. Flat Rate CDN is meant for application delivery. Vercel says bulk file distribution and media-heavy delivery fall outside it.

One caution on the figures. Vercel's pricing page and its docs describe the included CDN allowance differently, so we used the docs, which were updated on 14 September 2026. Check your dashboard before you plan around either number.

Suppose the team protects a staging project with a password and later wants single sign-on for a client.

We have not assumed the credit offsets the CDN tier. If it does, your bill is lower. The point about Vercel Pro pricing is its shape: seats are the floor, and a few add-ons can double it.

For a Next.js team, often yes, and Vercel Pro pricing is fair for what it delivers. Vercel builds the framework and runs it first, previews per pull request are close to instant, and viewer seats mean reviewers cost nothing. Functions on Pro can run up to 800 seconds, use up to 4 GB and 2 vCPU, and be set to multiple regions.

There is a small sweetener too. Each paid Pro team gets one free first-year domain on an eligible extension, including .app and .dev. It renews at the standard rate after year one, so treat it as a saving of one year, not a permanent discount.

Its edge network reaches far more places than any small platform. If your users are spread across North America and Asia, that matters more than any price line here, and we would not talk you out of it.

• Seats. Ten people who deploy is 10 x $20 = $200 a month before usage.
• A database. The price list we read has Blob storage but no Postgres line, so a database is a separate vendor and a second bill.
• Regional rates. The same function costs $0.184 per CPU-hour in Frankfurt against $0.128 in Washington.
• Add-ons. SSO at $300 and static IPs at $100 per project are individual line items.

Two behaviours are easy to miss. First, once the $20 credit is gone, Vercel switches the team to on-demand usage. The default $200 spend notice is an alert, not a ceiling, unless you set an automatic action yourself. Second, downgrading a Pro team to Hobby removes all active members except the original owner. Both are documented, and both are the sort of thing you would rather read before a bad month than during one.

The full picture of the two-vendor pairing is in what Vercel costs a small team and Helm7 against Vercel and Supabase.

Stay on Vercel Pro if you are a small Next.js team, your users are global, or you need framework features the day they ship. Look elsewhere if seats are your main cost, because Vercel Pro pricing scales with headcount. Helm7 does not charge per seat: Builder is $12 a month minimum for an app with Postgres, auth and storage, and Pro is $29. Usage draws down against that minimum.

The limits are real. Helm7 runs in Falkenstein and Helsinki only, is new, and is best with Next.js rather than every framework. For a fair side-by-side, see Vercel vs Railway and how to host a Next.js app. Our Next.js deploy guide shows the Helm7 route.