A client rang me in a panic last March. His Next.js marketing site had just racked up a $340 bill on Vercel after a Reddit post sent a traffic spike his way. He was on the Pro plan. He'd read nothing about bandwidth limits. And honestly? I hadn't warned him clearly enough. That's on me.
That conversation made me sit down properly and map out what Vercel and Netlify actually cost, not what their landing pages suggest they cost. I've deployed on both platforms across hundreds of projects at Seahawk Media, and the gap between the headline price and the real invoice is where most agency owners get stung.
So let's go line by line.
---
The Free Tiers: More Different Than They Look
Both platforms offer a free tier. Both call it "Hobby" or similar. Both seem generous on the surface. But they're structured very differently, and that matters a lot depending on what you're building.
Vercel's Hobby Plan
Vercel's free tier gives you 100GB of bandwidth per month, 6,000 minutes of Edge Function invocations, and 100GB of Edge Middleware invocations. Sounds like plenty. And it is, for a single portfolio site or a side project that gets 200 visitors a day.
The ceiling that catches people: Serverless Function execution is capped at 100GB-hours per month. If you're running any kind of API route inside your Next.js app (auth checks, form handling, fetching from a CMS), those hours add up faster than you'd expect. I tested this on a personal project last autumn. A simple site with a contact form and three API routes hit 40% of the monthly function allowance within a week of moderate traffic. Nothing viral. Just real usage.
One other thing most people miss: the Hobby tier does not allow commercial use. It's in Vercel's terms. I know plenty of freelancers who deploy client sites on Hobby "just temporarily" and never move them. That's a real liability.
Netlify's Free Tier
Netlify gives you 100GB bandwidth too, but their free tier also includes 300 build minutes per month and 125k serverless function invocations (not GB-hours, invocations). That unit change matters. A function that runs fast and cheap won't burn your quota the way a slow or memory-heavy one will on Vercel's model.
Netlify's free plan also allows commercial projects, which is a practical win for freelancers testing a client build before handoff.
The honest weakness: Netlify's build times on their free tier are noticeably slower than on paid plans. I've waited 6-7 minutes for a basic Gatsby build on free vs under 2 minutes on Pro. If you're iterating fast on a project, that friction is real.
---
Pro Plans: Where the Real Divergence Starts
This is where most professional developers and agency owners actually live, so it's worth spending time here.
Vercel Pro is $20/month per member . Netlify Pro (they call it "Core" now in some markets) runs at $19/month per member. Practically identical on paper.
But the per-member pricing model is where things get interesting. At Seahawk, we have a dev team. Once you've got 4-5 people on a workspace, you're looking at $80-100/month before you've deployed a single site on either platform. Both platforms charge per seat. Neither gives you a discount for adding junior devs or contractors who just need read access.
Bandwidth Overage Costs
Here's where Vercel can bite you. On Pro, you get 1TB of included bandwidth. After that, it's $0.15 per GB. That Reddit spike I mentioned at the top? A 300GB overage at $0.15/GB is $45. A 2TB traffic event is $150 in overages on top of your plan cost.
Netlify Pro also includes 1TB. Their overage rate is $0.20 per GB, which is actually higher per GB than Vercel. But Netlify lets you set hard spending caps, which means you can stop the bleeding before it becomes a $340 surprise. Vercel added spending limits to Pro plans too, but they were slower to make this accessible and the UI for configuring it is buried.
Build Minutes
Vercel Pro includes 24,000 build minutes per month. Netlify Pro includes 25,000. The difference is negligible for most teams.
Where it gets complicated: both platforms charge for concurrent builds separately. If you want multiple builds running in parallel (useful in a CI/CD pipeline with multiple branch deploys), you're buying add-ons. On Netlify, concurrent builds are $40/month per additional slot. On Vercel, it's baked into how their queue works on Pro but with limits on parallelism that can slow deployment pipelines on larger repos.
---
Serverless Functions and Edge: The Hidden Cost Layer
I'd argue this is the most misunderstood part of both pricing structures.
Vercel has gone hard on Edge Functions and their Edge Network. The pitch is low-latency computation at the edge, globally. The reality for pricing: Edge Function invocations are cheap on Pro, but if you're using them heavily (think middleware running on every request for auth, A/B testing, personalisation), you will cross into paid territory. The Pro plan includes 1 million Edge Middleware invocations per month. Sounds like a lot. A site doing 50k daily visits with middleware on every page request chews through that in under a month.
Netlify's Edge Functions run on Deno. They're included in the Pro plan but the documentation around exactly when you start paying for overages is, to put it charitably, vague. I've had to contact their support twice to get straight answers on billing thresholds. That opacity is a real issue when you're trying to cost a project for a client.
My Rule for Client Projects
When I'm scoping a project that involves heavy server-side logic, I'm usually reaching for a separate backend anyway (a small Railway or Render instance, or a proper API on AWS Lambda billed through the AWS console). Both Vercel and Netlify are frontend deployment platforms at heart. Trying to run a busy backend through their serverless layers is expensive and architecturally awkward.
---
Add-Ons That Quietly Inflate Your Bill
Both platforms have turned add-ons into a meaningful revenue stream. Here's what to watch:
- Vercel Analytics: $0 on Hobby, included on Pro for the basics. But Vercel Web Analytics at scale (high-traffic sites) moves into territory where you're paying per data point retained beyond 30 days.
- Netlify Forms: Free up to 100 submissions/month. After that, it's $19/month for 1,000 submissions. If a client has a busy contact form or a lead capture page, this adds up fast. I almost always swap this out for Typeform or a self-hosted solution.
- Netlify Identity: The authentication add-on starts free (up to 1,000 active users) but jumps steeply for anything above that. At 5,000 MAUs you're looking at $99/month just for Identity. For most client projects, I'd point you toward Clerk or Auth0 instead.
- Vercel Postgres / Blob / KV: These are billed separately through Vercel's storage products. Convenient? Yes. Cheap at scale? No. Vercel Postgres is essentially Neon under the hood, and going direct to Neon is almost always cheaper once your storage needs grow.
- Audit your add-ons every quarter.
- Anything you're paying both the platform and a third-party tool for, consolidate.
- For Netlify Forms specifically, set a submissions alert so you're not surprised mid-month.
- Don't use Vercel's storage products for anything you'll scale, unless the DX convenience genuinely justifies the premium.
---
Team Plans and Enterprise: When to Have a Different Conversation
Vercel's Enterprise tier has no public pricing. You're getting on a call with their sales team. From what I've seen quoted at Seahawk for larger client projects, you're typically looking at five figures annually before discounts. Their pitch is SLA guarantees, SSO, advanced security controls, and dedicated support.
Netlify Enterprise is similar. No public pricing. Custom contracts. I've seen Netlify come in more competitively priced than Vercel for mid-market clients, particularly agencies managing dozens of sites under one contract. But that entirely depends on your negotiation and what you actually need.
Honestly, if you're at the point of needing Enterprise, the pricing conversation is less about per-GB rates and more about support responsiveness and legal terms. Both platforms have had outages. Both have reasonable status pages. The question is who picks up the phone when your client's site is down at 2am.
---
Which Platform Is Actually Cheaper?
Depends what you're building. But I can give you concrete scenarios.
Portfolio or brochure site, one developer, low traffic: Netlify Free wins. Commercial use is allowed, and the function invocation model is more forgiving for simple contact forms.
Next.js app with moderate API usage, small team of 3: Vercel Pro is better optimised for Next.js (they built it, after all). At 3 seats that's $60/month. Budget an extra $20-30/month for occasional function or bandwidth overages and you're looking at ~$80-90 realistically. Netlify would run similar but with slightly worse Next.js support (ISR, for instance, requires workarounds on Netlify that are native on Vercel).
Agency managing 20+ client sites: This is where Netlify's per-site structure can be more attractive. Vercel's per-member pricing stings when you've got a growing team. Netlify's pricing for multiple sites under one account has historically been more agency-friendly, though this varies with plan negotiations.
High-traffic marketing site with occasional spikes: Neither platform is ideal without spending caps configured. Set them. Today.
---
FAQ
Does Vercel charge per project or per seat?
Per seat on the Pro plan. You pay $20/month for each team member, not per project. Projects themselves aren't individually billed, but resource usage (bandwidth, functions, builds) is pooled across the workspace and that's where overages occur.
Can I use Netlify's free plan for a client site?
Yes. Netlify explicitly allows commercial use on their free tier, unlike Vercel. That said, the 100GB bandwidth limit is a real constraint for any site with meaningful traffic, and the slow build times on free are annoying for active development.
Is Vercel better for Next.js than Netlify?
For most use cases, yes. Incremental Static Regeneration, Server Components, and the App Router all have first-class support on Vercel because Vercel maintains Next.js. Netlify has improved their Next.js support significantly with their Next.js Runtime, but there are still edge cases where things behave differently than on Vercel. If you're shipping a complex Next.js app, that matters.
What happens if I go over my bandwidth limit?
Both platforms let you continue serving traffic (they don't hard-cut you off by default). The overage is billed at the end of the month. Vercel charges $0.15/GB over 1TB on Pro. Netlify charges $0.20/GB. Both allow you to configure spending caps to prevent surprise bills. Configure them during setup, not after your first nasty invoice.
Are there cheaper alternatives to both?
Yes. Cloudflare Pages is worth a serious look, especially for static sites. Their free tier is extremely generous, and their Workers-based functions are billed on a consumption model that can be dramatically cheaper than either Vercel or Netlify for high-invocation workloads. I've been migrating a handful of static client sites to Cloudflare Pages over the past year and the cost savings are meaningful.
---
The bottom line is this: neither platform is a ripoff, and neither is automatically the budget choice. The difference shows up in the details, in whether you configure spending caps, in how you've architected your functions, in how many seats your team actually needs. Read the pricing page like a contract, not like a brochure. Because when that traffic spike hits at midnight, that's exactly what it is.