A client rang me in January 2025, not 2024, not some cautionary tale from the distant past, genuinely panicked because Vercel had charged his card $380 for a month he'd described as "quiet." His site was a Next.js marketing page for a SaaS tool. Maybe 40,000 monthly visitors. Not exactly Hacker News front-page traffic. The culprit was a combination of Edge Function invocations and an image optimisation misconfiguration that had been silently churning through his usage limits for six weeks. He'd never looked at the usage dashboard once.
I've deployed well over 12,000 sites across my career, a large portion of them through Seahawk Media, and Vercel is genuinely brilliant infrastructure. But its pricing model rewards people who read the small print, and punishes everyone else. So let me walk through every plan as it stands in 2026, flag the specific things that generate surprise invoices, and give you a straight answer on when Vercel actually makes sense.
---
The Four Plans at a Glance
Vercel runs four tiers: Hobby, Pro, Enterprise, and a relatively new Managed Infrastructure offering that's mostly relevant to large engineering teams. Most people reading this are deciding between Hobby and Pro, with maybe a sidelong glance at Enterprise.
Hobby is free. One person, personal projects only, and Vercel is pretty clear that commercial projects are not allowed on Hobby. A lot of freelancers ignore this. I've ignored it myself on the odd experimental build. But if you're running a client's revenue-generating site on a Hobby account, you're violating terms and Vercel can (and occasionally does) enforce this.
Pro costs $20 per month per member. A solo freelancer running client work pays $20. A two-person team pays $40. That baseline number is very reasonable. The problem is that it's a baseline, not a ceiling.
Enterprise is custom pricing. You negotiate, you get SLAs, you get SSO, dedicated support, and spending controls that are actually worth having. Typically starts around $2,000/month in my experience, though I've seen deals structured differently.
Managed Infrastructure sits adjacent to Enterprise and targets teams that want Vercel to handle the whole deployment pipeline for large Next.js or monorepo setups. I won't dwell on it here because if you're asking about it, you already have procurement conversations happening.
---
What's Included in Pro (And What Isn't)
The Pro plan includes a genuinely useful set of defaults. Vercel's own pricing page lists the current numbers, but broadly in 2026 you're looking at:
- 1 TB of bandwidth per month (soft overage kicks in after this)
- 100 GB of Edge Network data transfer
- 1,000 GB-hours of serverless function execution
- 1,000 image optimisations per month (this one bites people)
- 100 deployments per day
- Basic DDoS mitigation
The Image Optimisation Trap
Here's where my January client went wrong. Vercel's built-in next/image optimisation counts every unique image transformation as a billable event after your monthly allowance. The Hobby plan gives you 1,000 per month. Pro gives you more, but it's still a hard quota with per-unit overages above it.
If you've got an e-commerce build with product images, or a blog where editors upload high-res photos and you're serving three responsive breakpoints, 1,000 transforms disappears in days. I had a WooCommerce migration client at Seahawk where we'd ported a catalogue to a Next.js front-end and nobody had thought about this. We hit the limit by the 9th of the month.
Fix: use Cloudinary or Imgix for image serving and pass pre-optimised URLs to next/image with the unoptimized flag, or add a custom loader. Slightly more setup. Saves a lot of money.
Serverless Function Execution Time
The GB-hours metric confuses people because it combines memory allocation with execution duration. A function allocated 1 GB of memory running for 1 second costs 1 GB-hour. Run that function 3.6 million times in a month and you've consumed your Pro allowance.
That sounds like a lot. But if you've got an API route that hits a database, does some processing, and returns JSON, and you're getting reasonable traffic, those invocations add up. Especially if something's calling your API on a loop because of a front-end polling implementation someone wrote in a hurry.
---
Edge Functions vs. Serverless Functions: Two Different Billing Lines
This distinction matters and most developers hand-wave past it.
Serverless Functions run in specific AWS regions. They're Node.js, they can be long-running (up to 900 seconds on Pro), and they bill on the GB-hours model above.
Edge Functions run on Vercel's own Edge Network, closer to users, with faster cold starts. They're billed separately, on invocation count, with a limit of 1 million invocations per month on Pro before overages hit.
If you've written middleware that runs on every request, for auth checking, A/B testing flags, geolocation redirects, you are burning Edge Function invocations on every single page view. A site with 100,000 monthly page views and middleware on every route is using 100,000 invocations minimum. Add crawlers, bots, and prefetch requests and you can easily triple that number.
I review Vercel projects for clients fairly often and middleware misuse is the single most common billing issue I find. Someone read a tutorial, added middleware, forgot about it.
---
Bandwidth: The One That Actually Scales
Bandwidth overages on Vercel are $0.15 per GB above your included allowance on Pro. That's not the cheapest in the market (Cloudflare Pages, for comparison, has no bandwidth charges on their free tier), but it's not obscene either.
Where it becomes a problem is video. Or large file downloads. Or if you're serving assets directly from Vercel rather than offloading them to a CDN. A 5 MB PDF that gets downloaded 10,000 times in a month is 50 GB of bandwidth. Do the maths. Always put large static assets on S3 or Cloudflare R2 and reference them from there.
---
Spend Controls and Alerts: Use Them
Vercel added spending controls to Pro accounts a while back, and they improved the alerts dashboard significantly in late 2024. You can set a monthly spend limit so Vercel pauses your usage rather than running up an infinite bill.
The catch: pausing usage means your site goes down. So it's a hard stop, not a soft warning. You need to set your alert thresholds sensibly: maybe a warning at $50, a hard stop at $150, and then actually respond to the alert email.
Here's the practical setup I give every client before I hand over a Vercel project:
- Go to Settings > Billing > Spend Management
- Set a soft alert at roughly 1.5x your expected monthly bill
- Set a hard limit at 3x your expected monthly bill
- Add a secondary billing email, not just the founder's personal Gmail
- Check the Usage tab on the first of every month, even for five minutes
That last step catches everything. Usage anomalies almost always show a pattern from the first week of the month.
---
When Hobby Makes Sense (And When It Really Doesn't)
Hobby is genuinely good for:
- Personal portfolios
- Side projects with no commercial intent
- Internal tools you're building for yourself
- Open source project demos
It's not appropriate for client work, and beyond the terms issue, the practical limits bite hard. No custom SLAs, no team members, no advanced analytics, and support is community-only. I ran a client's staging environment on Hobby for about two months back in 2023 to save them money while they sorted out their budget. One day the function limits kicked in during a demo. Never again.
---
Pro vs. Self-Hosted: The Real Comparison
The question I get most often from agency owners is whether to stay on Vercel Pro or move to self-hosted alternatives. Railway, Render, and Fly.io are the three I recommend most for teams stepping away from Vercel.
The honest answer: Vercel's DX is still better than anything else for Next.js. The preview deployments, the Git integration, the Edge Network performance. If your project lives or dies on developer velocity and you're heavily invested in the Next.js ecosystem (Vercel builds Next.js, worth remembering), the $20/month is worth it before you even think about overages.
But if you're running a fairly predictable workload, not doing heavy serverless computing, and you want cost certainty, a $7/month Render instance or a $5 Railway service handles a huge proportion of what Vercel Pro handles. The deployment experience is worse. The DX is worse. The price is predictable.
Seahawk runs a mix. Client projects that are Next.js-heavy and need preview URLs for stakeholder sign-off go on Vercel. Simpler projects, high-traffic static sites, anything with aggressive cost sensitivity goes elsewhere.
---
FAQ
Is Vercel free for commercial projects?
No. The Hobby plan explicitly prohibits commercial use in Vercel's terms of service. If you're building anything that generates revenue, even indirectly, you need a Pro account. Vercel has been inconsistent about enforcement historically, but that's not a policy you want to test with a client's live site.
What actually causes surprise Vercel bills?
The four most common causes I see: image optimisation overages from next/image without a custom loader; Edge Function invocations from middleware running on every request; serverless function execution time from inefficient database queries inside API routes; and bandwidth spikes from large assets served directly from Vercel rather than a CDN. Any one of these can turn a $20 month into a $200 month.
How does Vercel's pricing compare to Netlify in 2026?
Netlify's Pro plan is $19/month per seat, so roughly parity on base cost. Netlify's included bandwidth is slightly lower (100 GB vs. Vercel's 1 TB on Pro), but Netlify's function execution model prices differently and can work out cheaper for certain workloads. If you're not deep in the Next.js ecosystem, Netlify is worth a serious look. If you're building with Next.js specifically, Vercel's tight integration with the framework is hard to replicate elsewhere.
Can I set a hard spending cap on Vercel Pro?
Yes. Vercel's Spend Management feature lets you set a hard monthly limit. When you hit it, Vercel pauses your project's usage, which means the site stops responding until either the month rolls over or you raise the limit. Set your limit thoughtfully. Getting an alert email at 11pm that your production site is down because you hit your $50 cap is not a fun experience (yes, this happened to someone I know).
Is Enterprise worth it for agencies?
At the price point, Enterprise makes sense for agencies running 10+ active client projects on Vercel simultaneously, or for any single project generating serious revenue where downtime has a direct financial cost. The biggest practical benefit isn't the SLA, it's the spend controls and the dedicated support channel. Having an actual human to contact when something breaks at 2am is underrated.
---
Vercel is good infrastructure. I'm not here to talk you out of using it. But it's priced like a utility, which means your bill is a direct function of how much you think about your usage patterns. The developers who get surprised invoices are almost always the ones who deployed something, forgot about it, and assumed "free tier" meant "free forever." It doesn't. Spend ten minutes with the usage dashboard before you hit publish on anything with real traffic behind it.