Hobby is free, Pro is $20/seat/month, Enterprise is “call us.” The interesting part isn’t the sticker price — it’s the resource-by-resource overage math that shows up the first time a blog post lands on Hacker News. Numbers verified against vercel.com/pricing.
Vercel sells you a developer experience and bills you for the underlying infrastructure that experience consumes. The plan tiers — Hobby, Pro, Enterprise — are the wrapper. The bill you actually receive is the sum of seven or eight metered resources: bandwidth, build minutes, function invocations, function duration, edge requests, image optimization, ISR reads, and the occasional surprise. This guide walks resource-by-resource and shows where solo founders get stung.
Methodology. All limits and overage prices below are taken from vercel.com/pricing and the “Limits” documentation, last reconciled May 2026. Vercel periodically rebrands their bandwidth and compute units (“Fast Data Transfer,” “Edge Requests,” etc.) but the underlying allocations and overage rates have been broadly stable. Always sanity-check against the live pricing page before committing.
The Hobby plan is genuinely free for personal use. It’s also explicitly non-commercial — per Vercel’s terms, you cannot run a paid product on it. People do anyway. The risk is a sudden “you’ve crossed Hobby limits, please upgrade” email mid-launch.
Resource limits on Hobby:
Hobby works for genuinely personal projects: a portfolio, a side blog, a learning playground. The moment you put up a pricing page and a Stripe button, you should be on Pro. Not because Hobby will mechanically refuse to serve you — it might still work fine for months — but because Vercel’s commercial-use clause is unambiguous, and getting a takedown email at 100 paying customers is a worse outcome than $20/month.
Pro is the floor for any commercial product on Vercel. It includes:
Heads-up: Pro is per-seat. If you add a contractor as a team member instead of using Vercel’s “Guest Access” or read-only roles, you just doubled your base bill to $40. We covered the contractor onboarding workflow in when to hire your first contractor.
Enterprise pricing is custom — expect a starting point in the four-figure-monthly range, climbing fast based on traffic, seats, and add-ons like dedicated edge regions, SAML SSO, and an SLA. The features that actually matter at this tier:
You don’t need Enterprise as a solo founder. You need it when you have an enterprise customer demanding it — usually a SOC 2 or HIPAA audit pushes you there. Until then, Pro plus careful resource management gets you to seven-figure ARR.
Three line items account for nearly every “wait, why is my Vercel bill $400 this month” story we hear:
Vercel’s next/image component is gorgeous and almost frictionless. It also charges per source image transformed. A marketing-heavy SaaS — case studies, blog posts, dynamic OG images — can hit 5,000 source images by the time it’s nine months old. Going past that on Pro is $5 per additional 1,000 sources, which sounds tiny until you realize a single dynamic OG-image route can generate thousands per week.
The fix: pre-optimize images at build time using Sharp or similar, only use next/image for the genuinely dynamic parts of your app, and don’t use it for static OG images at all (use Cloudinary or pre-generated PNGs).
Vercel charges by GB-hours of function compute. A page that streams an LLM response for 30 seconds, holds a database connection open while it does, and renders large JSX trees is orders of magnitude more expensive per request than a typical API route. Solo founders shipping AI features regularly see compute bills climb past their bandwidth bills.
The fix: stream from the edge where possible (lower per-second cost), avoid keeping serverless functions warm by accident, and consider moving genuinely long-running AI workloads to a dedicated provider like Modal, Railway, or Fly.io. Our Vercel vs Railway writeup walks through the cross-over point, and Fly.io vs Railway covers the alternative stack for compute-heavy workloads.
1TB sounds enormous until you serve a 4MB hero video on every page. A modest blog with autoplay video and 30,000 monthly visitors can chew through bandwidth shockingly fast. At $0.40/GB overage, an extra 500GB month is $200.
The fix: serve video and large media from a dedicated CDN like Cloudflare R2 or Bunny.net (both an order of magnitude cheaper for raw bandwidth), and let Vercel handle only the HTML, JS, and small assets it’s actually optimized for.
| Resource | Vercel Pro | Cloudflare Pages | Netlify Pro |
|---|---|---|---|
| Base price/seat | $20 | $5 Workers Paid | $19 |
| Bandwidth included | 1 TB | Unlimited | 1 TB |
| Bandwidth overage / GB | $0.40 | $0 | $0.55 |
| Function invocations | 1M | 10M | 2M |
| Build minutes | ~24K | ~24K | 25K |
| Image optimization | Yes, metered | Cloudflare Images add-on | Yes, metered |
Cloudflare Pages wins flat-out on bandwidth economics. Netlify is roughly Vercel-equivalent. Vercel’s premium is justified by the Next.js integration depth — if you’re shipping a Next.js app with ISR, server actions, middleware, and image optimization wired together, the time you save versus running it on Cloudflare or Netlify often clears the price difference. If you’re shipping a static React or Astro site, Cloudflare Pages is a better deal at scale.
Most solo SaaS stacks pair Vercel with Supabase. Here’s the realistic combined cost at three scale points, assuming a typical B2B SaaS shape (logged-in dashboard, modest blog, no heavy media):
| Scale | Vercel | Supabase | Combined |
|---|---|---|---|
| 1K MAU, low traffic | $20 (Pro) | $0–$25 | $20–$45 |
| 10K MAU, modest blog | $20–$60 | $25–$60 | $45–$120 |
| 100K MAU, content-heavy | $150–$400 | $100–$300 | $250–$700 |
The 100K MAU range is where the “is Vercel still the right call” question genuinely opens up. At that scale, swapping bandwidth-heavy paths to Cloudflare and keeping Vercel for the app routes can shave hundreds per month. We dig into the database side of that equation in Supabase pricing explained.
Five practical levers, in priority order:
next/image — serve a pre-optimized WebP and skip the per-source charge.The whole-stack cost picture for a solo SaaS at this scale is laid out in SaaS cost at $1K MRR — Vercel is one line of seven or eight, and treating it that way keeps the budget realistic.
Hobby for hobbies, Pro at $20 for any paid product, Enterprise only when a customer is demanding it. Inside Pro, the fight is on the metered resources — bandwidth, image optimization, function compute. Set a spend cap, audit your routes for accidental dynamism, and offload heavy media to a cheaper CDN. Most solo founders should expect a $20–$80 monthly Vercel line at 1K–10K MAU; if you’re materially above that, you have an overage problem you can fix with a single afternoon of cleanup.
Vercel’s pricing isn’t deceptive — the limits are documented, the overage rates are public, and the spend-cap feature exists. The traps are all on the developer side: dynamic routes that should be static, heavy assets that should be on a CDN, image optimization that should be a build-time step. Fix those and Pro is a remarkably good deal.
The stack, prompts, pricing, and mistakes to avoid — for solo founders building with AI.