Vercel pricing explained: the seat, the meter, and the rule that catches side projects

How Vercel pricing actually works

Vercel bills on two axes at the same time, and most confusion comes from reading only one of them.

• The seat. $20 per developer per month on Pro. Five developers is $100 before anyone visits your site.

• The meter. Edge requests, data transfer, function invocations, CPU time, memory, build minutes — each with its own rate, each billing above an included allowance.

So your invoice is a function of how many people build the site and how many people visit it. Those two numbers have nothing to do with each other, which is exactly why the bill is hard to predict.

There's also a rule on the free plan that isn't a price at all, and it catches more people than any overage rate. We'll get to it.

Vercel plans in 2026 (official)

Verified August 2026, from the Vercel pricing page.

• Hobby — free. Personal, non-commercial use only. 1M edge requests/month · 100 GB fast data transfer · 1M function invocations · 4 hours active CPU · 360 GB-hrs provisioned memory · 1 GB Blob storage · 1 team member · unlimited deployments · automated DDoS mitigation · firewall with up to 3 custom rules. No build minutes, no custom environments, and you cannot purchase additional usage.

• Pro — $20 per developer seat/month, including $20 of usage credit. 10M edge requests · 1 TB fast data transfer · unlimited function invocations · 1 custom environment · up to 40 custom firewall rules and 100 IP blocking rules · unlimited read-only viewer seats. Additional developer seats are $20/month each.

• Enterprise — custom. Everything in Pro plus SAML SSO, SCIM and directory sync, audit logs, managed WAF rulesets, multi-region compute and failover, a 99.99% SLA, advanced support and custom overage pricing.

Note what the $20 on Pro actually is: a seat fee that happens to include $20 of usage. It isn't $20 for the account and then metered usage on top — the first $20 of consumption is already paid for. Everything past it bills at the rates below.

Every overage rate, in one place

These are the numbers that decide whether a busy month costs $20 or $200. Pro rates, verified August 2026:

• Edge requests — $2 per 1M beyond the included 10M.

• Fast data transfer — $0.15/GB beyond the included 1 TB.

• Function invocations — $0.60 per 1M.

• Active CPU — $0.128 per hour.

• Provisioned memory — $0.0106 per GB-hour.

• Build minutes — $0.014 to $0.105 per minute, depending on the machine type you build on.

Individually these are reasonable. Collectively they mean one thing worth internalising: on Vercel, traffic costs money rather than capacity. A spike doesn't slow your site down — it shows up on the invoice at the end of the month. That's a genuine engineering advantage and a genuine budgeting problem, and which one it is depends entirely on whether you can predict your traffic.

The Hobby rule that catches side projects

Hobby isn't priced — it's scoped. It is for personal, non-commercial use. Not a soft suggestion; it's what the plan is for.

The pattern that trips people up is boring and extremely common:

• You build a side project and deploy it to Hobby. Perfectly fine.

• You add a Stripe button, or a client starts paying for it, or it becomes your company's landing page. Now it's commercial — and the plan it's sitting on isn't.

Nothing dramatic happens the same afternoon. But you're now running a commercial project on a plan that says it isn't for that, with no ability to purchase extra usage if you outgrow the caps, and one team member. If the project matters to your income, that's a strange place to leave it.

The second Hobby limitation is the quieter one: you can't buy more usage. On paid plans an overage is an invoice. On Hobby it's a wall. For a hobby project that's the right design; for anything that must stay up during an unexpected traffic day, it isn't.

Three scenarios with numbers

Scenario 1: a personal site, no money involved

A portfolio, a blog, a demo. A few thousand visitors a month, nowhere near any cap.

What you pay: $0. Hobby is genuinely generous here and the non-commercial rule doesn't apply to you. Vercel at its best — use it and don't overthink it.

Scenario 2: one developer, one commercial product

A real product with real users. One person deploys. Traffic is moderate and mostly predictable.

The math. One seat at $20, which includes $20 of usage. A site well inside 10M edge requests and 1 TB of transfer stays right there.

What you pay: $20/month in a quiet month; more in any month where a launch, a newsletter or a Reddit thread moves traffic. Fair value — you're getting a genuinely excellent platform for the price of a seat.

Scenario 3: a team of five

Five developers with deploy access, one production site, real traffic.

The math. $20 × 5 = $100/month before a single visitor. Usage on top of that, with the meters above. Read-only viewer seats are unlimited and free, so the honest optimisation is to be strict about who genuinely needs a developer seat.

What you pay: $100–200/month for a fairly ordinary setup. This is where teams start pricing alternatives — not because the platform disappoints, but because they're paying per person for something that doesn't get better with more people on the invoice.

How to keep a Vercel bill predictable

• Audit seats quarterly. Every developer seat is $20/month whether or not that person deployed anything. Viewer seats are free and unlimited — move anyone who only reviews.

• Watch fast data transfer, not page views. Images and video move far more data than HTML. Compress aggressively and serve appropriately-sized images; this single habit is usually the biggest line-item saving.

• Cache to cut function invocations. Every uncached dynamic route is an invocation. Static generation where you can, sensible cache headers where you can't.

• Check the build machine. Build minutes range from $0.014 to $0.105 per minute. A bigger machine that halves build time may or may not be cheaper — that's arithmetic, not a preference.

• Set spend alerts. The whole point of usage billing is that the number moves. Find out during the month, not after it.

Usage-based vs flat: the honest comparison

None of these rates are unfair — Vercel built Next.js and its platform is the smoothest place to run it. The question is which billing shape fits how you work.

Usage billing rewards you when traffic is low and charges you when it's high. Per-seat billing charges you for the size of your team regardless of either. If your traffic is spiky and your team is small, that combination is fine. If your team is five people and your traffic is steady, you're paying two variable costs for a workload that is neither.

On a flat host the same site costs the same every month: livemy.app is $10/month with a custom domain, free SSL and no seat count and no compute meter. The trade is real and worth stating — you give up Vercel's edge network, its preview deployments per branch, and the deepest Next.js integration in existence. If you're not using those, you're paying for them. If you are, they're worth the money. Our guide to deploying Next.js without Vercel covers what actually changes, and cheap Vercel alternatives has the full lineup.

FAQ

Is Vercel free?

The Hobby plan is free but limited to personal, non-commercial use. It includes 1M edge requests, 100 GB fast data transfer, 1M function invocations, 4 hours of active CPU and 1 team member per month — and you cannot purchase extra usage if you exceed it.

How much does Vercel cost per month?

Pro is $20 per developer seat per month and includes $20 of usage credit. Additional developer seats are $20/month each; viewer seats are free and unlimited. Enterprise is custom. Verified August 2026.

Can I use the free Vercel plan for a commercial project?

No — Hobby is specified for personal, non-commercial use. A project that takes payments, serves a client, or acts as a company site belongs on Pro or another host. This is the single most common Vercel pricing mistake.

Why is my Vercel bill higher than $20?

Because $20 is a seat fee with $20 of usage included, not a cap. Extra developer seats add $20 each, and traffic past the included allowances bills at $2 per 1M edge requests, $0.15/GB transfer, $0.60 per 1M invocations, plus CPU, memory and build minutes.

What counts as fast data transfer?

Data served from Vercel's edge network to your visitors — pages, assets, images, API responses. It's the meter most affected by media-heavy sites, and 1 TB is included on Pro with $0.15/GB after that.

Does Vercel charge for bandwidth spikes?

Yes. On paid plans a traffic spike bills rather than throttles, so your site stays fast and your invoice grows. On Hobby you can't buy extra usage at all, so the allowance simply runs out. Set spend alerts either way.

Is Vercel worth it compared to a flat-priced host?

If you're deep in the Next.js ecosystem and use preview deployments and the edge network daily, yes — nothing else runs Next.js as smoothly. If you deploy a finished app and mostly need it online, you're paying per seat and per request for capability you aren't using; a flat $10/month host does that job at a fixed number.

Two meters, and only one of them is about your app

Vercel's pricing is honest and unusually well documented — every rate above is published. The thing to decide before comparing it to anything is which of the two meters is actually driving your bill. If it's traffic, usage billing is a fair trade for a platform that doesn't buckle under a spike. If it's headcount, you're paying for seats on a plan whose best features are about requests — and that's worth pricing honestly.

→ Host your app on livemy.app · Flat $10/month · No seat fees, no compute meter · Custom domain and SSL included.