Vercel pricing looks simple on the surface — free, $20/seat/month, call us — but the bill a real Next.js project generates depends almost entirely on a handful of usage meters that aren't obvious until you've already deployed. Here is what those meters actually are, what triggers them, and what a mid-traffic marketing site should expect to pay in 2026.
What Hobby actually allows commercially
Hobby is free and it is not for commercial use. Vercel's terms explicitly prohibit using the Hobby plan for commercial projects. That is not a grey area — it covers any site that generates revenue directly or indirectly, including lead-generation sites, e-commerce storefronts, and SaaS marketing pages. If you are building something for a client or for your own business, you are on Pro from day one.
What Hobby gives you if you are legitimately prototyping: 100 GB bandwidth per month, 6,000 Edge Middleware invocations, 500,000 Edge Request units, and serverless function execution capped at 100 GB-hours. Deployments are limited to one concurrent build. That is fine for a portfolio or a learning project. It is not fine for anything a client will see in production.
Pro per-seat maths for small teams
Pro is $20 per seat per month, billed monthly, or $216 per seat per year (10% off). Seat count is based on team members with access to the Vercel dashboard — not end users of your site.
For a typical freelance engagement: you need one seat for yourself and one for the client. That is $40/month. If the client has a developer on their side plus a project manager who occasionally checks deployments, you are at $80/month just for seats before a single request is served.
For a small agency team of five developers all working across shared projects, you are at $100/month in seats alone. That is a fixed cost that compounds before you touch any usage line item.
Pro includes 1 TB bandwidth, 1,000 GB-hours of serverless function execution, and 5,000 image optimisations per month at no additional cost. The question is whether those included amounts are enough.
The usage line items that surprise people
Three meters catch teams off guard. These are the ones worth modelling before launch.
Function duration (serverless and Edge). Every route handler, Server Component data fetch, and API route that runs on Vercel serverless burns GB-hours. A cold-started Node.js function using 512 MB of memory running for 2 seconds costs 0.000278 GB-hours. That sounds trivial. At 10,000 requests per day, you burn 2.78 GB-hours daily, or roughly 84 GB-hours per month — well inside the 1,000 GB-hour Pro inclusion. But if you have long-running data aggregation routes, PDF generation, or AI inference calls that run for 10–30 seconds, the maths shifts fast. Overage is $0.18 per GB-hour.
Image optimisation. Vercel's built-in next/image optimisation counts each unique source image at each unique size as one optimisation request. Pro includes 5,000 per month. A marketing site with 50 blog posts, each with a hero image served at three breakpoints, generates 150 unique optimisations on first load. Add product images, author avatars, and Open Graph images and you can hit 5,000 genuinely quickly if you have not configured a minimumCacheTTL or are generating many unique query-string variants. Overage is $5 per 1,000 optimisations. Caching images in a CDN or using Sanity's own image CDN for transformation sidesteps this entirely.
Bandwidth. 1 TB is the Pro inclusion. Most content sites stay under this, but if you are serving video previews, large PDFs, or downloadable assets directly from Vercel rather than from a dedicated object store, bandwidth climbs. Overage is $0.15 per GB after the included 1 TB.
A less commonly discussed meter: Deployment build minutes. Pro includes 24,000 build minutes per month. If your ISR revalidation triggers frequent full rebuilds, or you have many preview deployments, you can eat into this. Overage is $0.01 per build minute — low cost but worth monitoring.
Realistic monthly total for a mid-traffic marketing site
Assumptions: a Next.js App Router marketing site with a Sanity CMS backend, roughly 80,000 unique visitors per month, a 30-page site with a blog at 100 posts, image-heavy but properly configured with minimumCacheTTL: 86400 and Sanity serving transformed images at the CDN level. Two Vercel seats (developer + client).
| Line item | Included | Estimated usage | Overage cost |
|---|---|---|---|
| Pro seats (2) | — | 2 × $20 | $40.00 |
| Bandwidth | 1 TB | ~60 GB | $0 |
| Function execution | 1,000 GB-hrs | ~120 GB-hrs | $0 |
| Image optimisations | 5,000 | ~3,200 | $0 |
| Build minutes | 24,000 | ~800 | $0 |
| Monthly total | $40.00 |
For this profile, the bill is just the seat cost. The inclusions comfortably absorb the usage. Where it breaks: if image optimisation is not cached (costs climb to $15–$40/month in overage), or if function duration is high due to uncached database queries (easily adds $20–$60/month).
A heavier project — e-commerce with personalised routes, server-rendered cart state, and ~500,000 monthly visits — realistically lands at $80–$180/month on Pro before you are asked to call the Enterprise team.
When Enterprise conversations start
Vercel does not publish Enterprise pricing publicly. The conversation typically starts when a team needs one or more of: SSO and SAML, custom SLAs, DDoS protection above what Pro provides, audit logs, spend controls, or IP allowlisting for Vercel deployments. In practice, Enterprise contracts I have seen discussed in public forums start around $3,000–$5,000 per month for small-to-mid organisations, rising significantly with traffic and feature requirements.
The realistic trigger for most Next.js product teams is the compliance requirement (SOC 2, audit logs) rather than raw traffic — Pro handles a lot of traffic just fine. If a procurement team asks for a DPA and SSO on day one, budget Enterprise from the start.
What to watch before your first invoice
Set a Vercel spend limit as soon as you create the team. It is under Settings → Billing → Spend Management. Without it, usage overages accumulate silently. Enable Vercel Analytics separately — it does not affect your compute bill but it does add $10–$14/month if you opt into the paid tier for longer data retention. And if you are using Sanity for images, route all image transformation through Sanity's CDN rather than Vercel's optimisation pipeline — you eliminate one entire meter.
Top comments (0)