
Vercel is cheap until you hit one of three numbers: 1TB of monthly bandwidth, 10 million edge requests, or your fifth developer seat. Cross any of them and your bill jumps from $20 a month to $200 or $300 fast, with no warning and no hard cap to stop it.
That is the short answer. The longer answer is that Vercel is still the best deal in the industry for solo developers and small teams shipping Next.js apps, and a genuinely bad deal once you scale past roughly 100,000 monthly active users or eight engineers. Below is the honest breakdown, with real numbers from Vercel's pricing page (May 2026), real overage examples from teams who got surprised, and the exact thresholds where you should consider moving.
Vercel ships three tiers. Most pricing reviews list them and stop there. We will list them and then tell you the traffic level at which each one stops being a good idea.
| Plan | Base cost | Included bandwidth | Included edge requests | Best for |
|---|---|---|---|---|
| Hobby | Free | 100 GB/month | 1M/month | Personal sites, side projects, prototypes (non-commercial only) |
| Pro | $20/seat/month + $20 usage credit | 1 TB/month | 10M/month | Commercial apps under 50K MAU, teams of 1-5 |
| Enterprise | Custom (typically $20K-$150K/year) | Custom | Custom | SAML, HIPAA, dedicated support, predictable billing |
Hobby is genuinely free. Pro starts at $20 per developer seat per month, with a $20 monthly usage credit baked in. Enterprise pricing is opaque and starts in the low five figures annually for most accounts we have seen, climbing fast for traffic-heavy SaaS.
The trap is the overage table. Once you cross any included quota, Vercel charges per unit, and the units add up faster than founders expect.
| Resource | Pro included | Overage rate |
|---|---|---|
| Fast Data Transfer (bandwidth) | 1 TB/month | $0.15/GB |
| Edge Requests | 10M/month | $2 per 1M |
| Function Invocations | 1M/month | $0.60 per 1M |
| Active CPU (functions) | included | $0.128/hour |
| ISR Reads | 1M/month | $0.40 per 1M |
| ISR Writes | included | $4 per 1M |
| Image Transformations | 5,000/month | $0.05 per 1,000 |
| Build Minutes | included | $0.014/minute |
| Speed Insights | 10K events | $10/project + $0.65 per 10K |
Numbers like "$0.15 per GB" sound trivial. They stop sounding trivial when your launch goes well and you push 4TB through a CDN in a week.
Here is the real-world translation, drawn from billed examples reported across deployment-cost reviews in 2026:
The base plan is honest. The bill is not, because of five line items that are easy to miss when you sign up.
1. Bandwidth overages compound silently. A viral launch, a misconfigured client-side polling loop, or a single video embed can push you past 1TB without warning. The Pro plan includes a $20 usage credit that covers the first 133 GB of overage, then charges flat $0.15/GB after that. AWS CloudFront charges roughly $0.085/GB for similar volume; Cloudflare Pages currently includes unlimited bandwidth on its free and paid tiers.
2. No hard spend cap. Vercel offers Spend Management with soft thresholds, but no real budget ceiling. If a function loops on a Friday night, your Monday-morning bill is whatever the function did before someone noticed. Founders coming from AWS expect this; founders coming from Heroku do not.
3. Per-seat fees compound with team size. Every developer seat is $20/month. A 10-person engineering team pays $200/month before a single byte is served. Add a few overages and you are above $400/month for what is effectively static-site hosting plus a function runtime.
4. Add-ons cost real money. SAML SSO is $300/month on Pro. HIPAA BAA is $350/month. Static IPs are $100/project/month. Observability Plus and Web Analytics Plus are $10/month each. Most of these are free on Cloudflare or self-hosted alternatives.
5. Image optimization is metered separately. Pro includes 5,000 image transformations per month. After that it is $0.05 per 1,000. An e-commerce catalog with 30,000 products and weekly cache invalidation can rack up $100-$200/month in image bills alone. Storing images on S3 and serving through Cloudflare avoids this entirely.
This would be a hatchet job if we did not name what Vercel does well, because the reason teams pay the premium is real.
Next.js shipping speed. If you are using Next.js, no other host comes close. Edge functions, ISR, image optimization, and Preview deployments work out of the box, with zero config. The same setup on AWS takes a week of Terraform and a senior engineer who has done it before.
Preview URLs per pull request. Every PR gets its own deployable URL. Designers, PMs, and customers can click and review. Building this on Cloudflare Pages is possible; building it on AWS amplifies the engineering burden.
Edge network performance. Vercel's edge network is genuinely fast. Cold-start times for Edge Functions are in the 50ms range. Lambda@Edge cold starts are typically 200ms or worse.
Observability and DX. Build logs, runtime logs, and performance traces are right there in the dashboard. No CloudWatch tab-switching.
The free tier is real. A Hobby project on Vercel handles a Hacker News front page hit without breaking, as long as you stay under 100GB bandwidth and 1M edge requests. For prototypes and side projects, this is hard to beat.
At scale, the bill becomes irrational. A 200K-MAU SaaS on Vercel can pay $1,500/month for what costs roughly $50/month on a Hetzner VPS or $200/month on Cloudflare Workers + R2. The hosting is not 30 times better. You are paying for the convenience.
Bandwidth-heavy workloads. Video, large image galleries, software downloads, and downloadable data are economically painful on Vercel. Cloudflare R2 has zero egress fees. AWS S3 + CloudFront is cheaper. Bunny CDN is roughly 5x cheaper.
Per-seat pricing on platform teams. A 20-person platform team pays $400/month in seat fees alone. GitLab Pages, Cloudflare Pages, and self-hosted Coolify charge nothing per seat.
Compliance gates. SAML, HIPAA, and audit logs are all paywalled behind add-ons or Enterprise. Auth0, Clerk, and most SaaS competitors include SSO in their non-Enterprise tiers now.
These are the points where you should reconsider Vercel, based on real billing data from teams using it in 2026.
| Threshold | Recommendation |
|---|---|
| Single dev, <50K MAU, <500GB/mo | Stay on Hobby (if non-commercial) or Pro. Vercel is the cheapest sane option. |
| 1-5 devs, <100K MAU, <1TB/mo | Pro plan is fair value. Total cost typically $40-$150/month. |
| 5-10 devs, 100K-500K MAU, 1-5TB/mo | Vercel costs $300-$1,500/month. Audit your usage. Move static assets to R2 or Bunny CDN. Keep the app on Vercel. |
| 10+ devs OR >500K MAU OR >5TB/mo | Migrate the bandwidth-heavy parts off Vercel. Consider Cloudflare Pages + Workers, or self-hosted Next.js on Coolify/Render. |
| Compliance required (SOC 2, HIPAA, FedRAMP) | Either pay for Vercel Enterprise or self-host. The Pro add-on prices ($300-$350/month each) make Pro a worse deal than Enterprise above ~$1,500/month total. |
The hidden cost of moving is engineering time. A clean migration of a Next.js app from Vercel to self-hosted on Render, Coolify, or AWS ECS typically takes a senior engineer 3 to 5 working days. At a $1,500/week rate, that is roughly $1,000 of engineering time. If your Vercel bill is already at $300/month, the migration pays back in 4 months. If your bill is $1,500/month, it pays back in under three weeks.
This is the calculation most pricing reviews skip, because the cost of competent engineering is the variable nobody wants to quantify. Useful framing on whether to keep paying for a tool or invest engineering time in replacing it shows up in our Cursor IDE review for senior engineers in 2026, and the same logic applies here: the tool is worth its price as long as the alternative costs more in engineering hours than it saves in subscription fees.
Three real alternatives are worth naming honestly.
Cloudflare Pages + Workers. Free bandwidth, generous request limits, $5/month base for Workers. Loses to Vercel on Next.js feature parity (no native ISR, weaker image optimization). Wins on scale economics by a factor of 10 or more. Best for teams comfortable with Workers' runtime and willing to lose some Next.js sugar.
Netlify. Similar pricing to Vercel ($19/seat/month Pro, 1TB bandwidth, $55/100GB overage). Slightly cheaper per-seat, slightly more expensive per-overage. Roughly a wash. The honest reason to pick Netlify over Vercel today is if you prefer their Forms or Identity products.
Self-hosted on Coolify, Render, or a Hetzner VPS. Cheapest by a wide margin (Hetzner CCX13 = $13/month, includes 20TB bandwidth). Trade-off is operational overhead. You are responsible for SSL renewal, monitoring, scaling, and backups. Most founders should not do this until their Vercel bill exceeds $500/month.
For teams comparing the build-vs-buy decision on infra more broadly, the same principle from our analysis of SQL vs NoSQL choices applies: optimize for the boring choice that is cheapest to walk away from later.
Buy Pro if you are a 1-to-5-person team, shipping a Next.js app, with under 100,000 MAU, and you would rather pay $50-$150/month than spend a week setting up infrastructure. The math works.
Skip Pro if you are bandwidth-heavy (video, large images, downloads), running on a non-Next.js framework, or you have a 10+ person engineering team where the per-seat fee starts to dominate.
Skip Vercel entirely (use Cloudflare Pages or self-host) if your traffic is over 500K MAU and your team includes anyone competent at deploying Docker containers. The savings will pay an engineer's salary.
If you want a second opinion on whether your current stack is over-built or under-built for your stage, the Ship-or-Skip tool gives you an honest grade on every line item in your infra budget. It will tell you when Vercel is the right call and when you are paying tax for convenience you do not need.
A note for founders who do not have a senior engineer on staff to run this audit: every engineer on Cadence is AI-native by default, vetted on Cursor, Claude Code, and Copilot fluency before they unlock bookings, and most can do a Vercel cost audit and migration plan inside their 48-hour free trial.
A senior engineer on Cadence is $1,500/week. A migration off Vercel to Cloudflare Pages or self-hosted Render typically takes 3 to 5 days of focused work, plus a day of cutover. Total cost: one week, $1,500. If your Vercel bill is over $400/month, it pays for itself in four months. Mid engineers at $1,000/week handle the same migration if your stack is straightforward (vanilla Next.js, no custom edge functions). Booking a senior engineer through Cadence gets you a 48-hour trial to scope the migration before you commit.
For teams under 5 people running a commercial Next.js app under 50K MAU, yes. The included $20 usage credit covers most workloads at that scale, and the developer experience is hard to beat. Above 5 seats or 100K MAU, the per-seat fees and bandwidth overages start to dominate, and alternatives like Cloudflare Pages become more attractive.
Roughly at 100K MAU, 1TB monthly bandwidth, and 5+ developer seats. At that point the typical Vercel bill is $200-$300/month, while the same workload on a Hetzner VPS runs around $15/month and on Cloudflare Pages runs near zero for bandwidth. The crossover sharpens fast above 500K MAU, where Vercel can cost 20 to 30 times more than self-hosting.
Yes, but only for non-commercial projects. The Hobby plan is free forever and handles 100GB bandwidth, 1M edge requests, and 5,000 image transformations monthly. Vercel reserves the right to enforce the non-commercial clause; many indie projects with light commercial activity skate by, but a real SaaS will get a friendly email asking you to upgrade.
Cloudflare Pages with Workers for SSR, at roughly $5/month base. You lose some Next.js-specific features (native ISR, Vercel's image optimization), but bandwidth is effectively free and request pricing is roughly 10x cheaper. For non-Next.js apps, a $5/month Hetzner VPS running Coolify gives you Vercel-like git-push deploys with no per-GB fees.
You cannot. Vercel offers Spend Management with soft notifications and project-pause thresholds, but no true budget ceiling. If you are worried about runaway bills, configure aggressive Spend Management thresholds, set up function timeouts, and monitor the dashboard weekly. Or, if predictable billing matters more than convenience, switch to a fixed-price host.