A client rang me in October last year, slightly panicked. He'd launched a Next.js marketing site the previous month, traffic had picked up, and his Vercel bill had jumped from $0 to $94. No warning. No gradual escalation. Just a number he wasn't expecting. And the thing is, nothing was wrong. He hadn't misconfigured anything. The platform was doing exactly what it's designed to do.
That conversation is the reason I'm writing this. Vercel is genuinely excellent infrastructure, and I say that having deployed probably 400+ projects on it across Seahawk's history. But the pricing structure has traps in it that catch people who didn't read the fine print, or read it and didn't run the actual numbers. Let me do that for you.
The Hobby Plan: Free Until It Isn't
Vercel's free tier, called Hobby, is legitimately useful. For a personal project, a portfolio, or a low-traffic blog, it'll handle everything. You get 100GB of bandwidth per month, 6,000 minutes of Edge Middleware invocations, and 100GB-hours of serverless function execution. Those numbers sound enormous. They're not, once you're running something real.
Here's what actually eats your Hobby allowance:
- Serverless function duration. Each function call counts against your GB-hours. A data-heavy API route that runs for 3 seconds and uses 512MB of memory burns through 0.0004 GB-hours per invocation. Sounds trivial. At 10,000 requests a day, that's 1.2 GB-hours. Your allowance is 100. You've got room. But stack three or four such routes and you're gone by mid-month.
- Bandwidth. If you're serving any kind of media, 100GB goes fast. A site with product images, video previews, or even a reasonably rich portfolio can hit that in two weeks of decent traffic.
- Build minutes. 6,000 build minutes per month. A complex Next.js 14 app with a lot of static pages can take 4-8 minutes per build. If you're deploying frequently, that adds up.
The biggest restriction on Hobby is this: it's for personal, non-commercial use. That's not just fine-print padding. If you're building client sites, even small ones, you're technically violating the terms of service. I know agencies that have run client projects on Hobby accounts for months without issue. I also know one that got their deployments suspended. Not worth the risk.
Pro Plan: $20/Month, Then It Gets Complicated
The Pro plan starts at $20 per month per member. One developer working alone pays $20. A team of four pays $80 just for seats. That's the baseline, and it's reasonable.
But Vercel's pricing is consumption-based above those baseline limits. The Pro tier gives you:
- 1TB of bandwidth (vs 100GB on Hobby)
- 1,000 GB-hours of serverless function execution
- 24,000 build minutes
Beyond those included amounts, you pay overages. Bandwidth overages run at $0.15 per GB. Serverless execution overages are $0.18 per GB-hour. Build minute overages are $0.01 per minute.
What a Real Mid-Size Project Looks Like
Last year, Seahawk built out a Next.js 13 e-commerce front-end for a UK fashion client. Single developer account, so $20/month for the seat. The site had about 80,000 monthly visitors, a product catalogue served via API routes pulling from a headless Shopify instance, and ISR (Incremental Static Regeneration) running on about 3,000 product pages.
Average monthly bill: $47.
The breakdown: $20 for the seat, roughly $18 in bandwidth overages (they were serving a lot of high-resolution imagery before we pushed them to Cloudinary), and about $9 in function execution. Once we moved image delivery to Cloudinary and added a bit of caching logic to the API routes, it dropped to $26/month. Small change in architecture, meaningful change in bill.
That's the thing about Vercel costs. They're not fixed. They respond to how well you've built the thing.
The Edge Functions Variable
If you're using Vercel Edge Functions (not the same as serverless functions), pricing works differently. Edge runs on the V8 isolate model rather than Lambda-style containers, so it's faster and cheaper per invocation. You get 500,000 edge function invocations per month on Pro. After that, it's $2 per million.
For most teams, edge function costs are negligible. The dangerous one is serverless. Always check which runtime your functions are using.
Image Optimisation: The Invisible Line Item
This one catches almost everyone. Vercel's built-in Next.js image optimisation (the <Image /> component hitting the /_next/image endpoint) counts against your included fast origin transfer and, in some configurations, generates its own usage charges.
On Pro, you get 5,000 source images and 50,000 optimisation credits per month. Each unique image at a new size combination burns a credit. A product grid with 200 products, each rendered at three breakpoints, generates 600 optimisations on first load. Cache hits don't cost you. But cold deployments, or frequently-changing catalogues, can drain this quickly.
The fix is simple: use a CDN or image service like Cloudinary, Imgix, or even Bunny.net in front of Vercel's optimiser. Or configure a custom image loader and bypass Vercel's pipeline entirely. I set this up as default on every new Next.js project now.
Team Accounts and the Per-Seat Trap
Here's where agency owners get stung. Pro is $20 per member per month. If you're onboarding clients to your Vercel team so they can see deployment previews, manage environment variables, and check analytics, each one of them is a seat.
Six client contacts plus your four internal developers: $200/month before you've hit a single usage overage.
The workaround most people land on is keeping a single team with internal members only, and sharing deployment preview links manually with clients. You lose the live-collaboration aspect, but you save real money.
Some agencies create one Vercel Pro account per client instead. That's $20/month per client, billed to the client. Cleaner, actually. Each client owns their infrastructure, you're just the deployer. We moved to this model at Seahawk around 2022 and it's been cleaner from a client-handover standpoint too.
When Does Enterprise Make Sense?
Vercel's Enterprise plan has no public pricing. You talk to sales. Based on conversations I've had and bills I've seen, teams tend to hit the Enterprise conversation at around $1,500-$3,000/month on Pro with overages, where Vercel will often negotiate a committed-spend contract that ends up cheaper per unit.
Enterprise adds:
- SSO and SAML
- Custom spend limits and committed-use pricing
- SLA guarantees (99.99% uptime commitment)
- DDoS mitigation at a higher tier
- Advanced observability integrations
For most agencies building client sites, Enterprise is overkill. The clients who need it are usually running high-traffic consumer apps, internal SaaS tools with strict security requirements, or anything where a 10-minute outage has direct revenue consequences.
If you're spending more than $500/month on Pro consistently and not expecting the workload to drop, a sales call is worth 30 minutes of your time.
How Vercel Compares at a Practical Level
I'm not going to do a full breakdown of every alternative (that's a separate post), but here's the honest context.
Netlify's comparable pricing is structured similarly: free tier, then $19/month Pro per seat, with its own bandwidth and function overages. In my experience, Netlify ends up slightly cheaper for simpler static sites and slightly more expensive for complex serverless workloads. The developer experience is also just a notch below Vercel's for Next.js specifically, which makes sense given that Vercel built Next.js.
Railway, Render, and Fly.io price on pure compute rather than per-seat. For server-side applications that need persistent processes, they're often significantly cheaper. But they're not Vercel alternatives for Next.js front-ends specifically. Different tool.
If cost is your primary concern and you're comfortable with a bit more configuration, Cloudflare Pages is remarkable value. Unlimited bandwidth, Workers for serverless, free tier that's genuinely usable in production. The Next.js compatibility via the Cloudflare adapter is decent but not perfect. I've had smooth deployments and I've had gnarly edge case bugs. Worth knowing about.
Tactics to Reduce Your Actual Bill
Here's what actually moves the needle, based on real projects rather than documentation-reading:
- Cache aggressively at the CDN layer. Vercel's built-in CDN is good, but if you're serving the same serverless response repeatedly, you're paying per invocation. Set cache headers properly. Even a 60-second cache on a high-traffic route can cut costs dramatically.
- Move static assets off Vercel. S3 + CloudFront, Bunny.net, or R2 (Cloudflare's storage, which has no egress fees) for images, videos, and other large assets. Bandwidth overage at $0.15/GB adds up. Bunny.net charges around $0.01/GB for European bandwidth.
- Audit your serverless function regions. Functions run in all regions by default in some configurations. If your users are in Europe and your database is in eu-west-1, routing functions through us-east-1 adds latency and invocations. Pin your functions to the right region.
- Use edge runtime for lightweight logic. Auth token validation, header manipulation, redirects. These are faster and cheaper on edge than on serverless.
- Review your team roster quarterly. Stale seats at $20/month each are just waste.
FAQ
Is Vercel free for commercial projects?
No. The Hobby plan explicitly prohibits commercial use. If you're building something for a paying client, or building a product that generates revenue, you need to be on Pro. This isn't an ambiguous grey area; Vercel's terms of service are clear on it.
What happens if I go over my limits on Pro?
Vercel doesn't cut you off. It bills you for overages at the rates listed on their pricing page. Bandwidth is $0.15/GB, serverless execution is $0.18/GB-hour. There's no hard cap by default, though you can configure spend limits in your billing settings to get alerts or stop deployments. I always set up a spend alert on new projects. Discovering a surprise bill a month after the fact is avoidable.
Can I run a high-traffic Next.js app on Vercel Pro without hitting Enterprise?
Yes, absolutely. The deciding factor isn't usually traffic volume, it's architecture. A well-cached, edge-optimised Next.js app with proper ISR and external image delivery can handle millions of monthly visitors on Pro for $30-60/month. A poorly-built one with chatty serverless functions and no caching will cost five times that at a quarter of the traffic.
Is the $20/month Pro plan per project or per team?
Per seat on a team. You pay $20 per member in your Vercel team, and that team can have unlimited projects. If you're a solo developer, you pay $20/month regardless of how many projects you deploy.
Does Vercel charge for preview deployments?
Preview deployments themselves don't have a separate charge. But they do consume build minutes, and any serverless functions invoked during preview testing count against your execution limits. On a busy team with lots of pull requests, build minutes can become a real line item.
---
The honest summary: Vercel is good infrastructure, and for Next.js especially, it's hard to beat on developer experience. But it's not a flat-rate service, and if you're onboarding clients or scaling a product, you need to model your usage before launch rather than after. Run your expected function invocations, your bandwidth, your image optimisations. Build in 20% buffer. Then decide if Pro makes sense or if the architecture needs adjusting first.
The client who rang me in a panic? He's still on Vercel. Bill is $31/month now. Worth it.