Vercel review: when Hobby is enough, and what Pro really costs
Vercel is the easiest way to deploy a Next.js or other front-end app: push to Git and it is live worldwide. The free Hobby plan is generous, but it is for personal, non-commercial use only. Anything that earns money needs Pro: $20 per developer a month, including $20 of usage credit, then pay-as-you-go.
This review explains what Hobby includes, how Pro's usage billing works, and how to keep the bill predictable. The calculator estimates a month for your project.

What Vercel is
Vercel is a hosting platform for web front-ends and the server code behind them. Connect a Git repository and every push builds and deploys automatically, with a preview link for each branch, a global CDN and serverless functions. It is made by the company behind Next.js, and it is especially smooth for Next.js, although it supports most front-end frameworks.
Prices below come from Vercel's pricing page and documentation in November 2026, in US dollars excluding tax.
Hobby: free, but not for business
The Hobby plan is free with no time limit. Each month it includes 100 GB of data transfer, 1 million CDN requests, 1 million function invocations, 4 hours of active CPU, 360 GB-hours of memory, 5,000 image transformations and 50,000 Web Analytics events. It has one developer seat, up to 200 projects and 100 deployments a day.
Two rules matter more than the numbers:
- Hobby is for personal, non-commercial use only. Vercel's documentation says so plainly, and its terms require Pro or Enterprise for any commercial use. A client project, a company website, a shop or a SaaS product counts as commercial, even with tiny traffic.
- You can't buy more. If you hit a Hobby limit, you usually have to wait until 30 days have passed before you can use that feature again.
Pro: $20 a seat, plus usage
Pro costs $20 per developer seat a month, and each month includes $20 of usage credit. Viewer seats (people who review previews but don't deploy) are free. After the credit, usage is billed as you go, for example:
- Function invocations from $0.60 per million.
- Active CPU from $0.128 per hour, and memory from $0.0106 per GB-hour.
- Image transformations from $0.05 per 1,000.
- Build minutes at $0.007 a minute.
Data transfer and CDN requests on Pro are covered by Vercel's Flat Rate CDN option, a fixed monthly CDN price. New Pro teams get a default on-demand budget of $200, which you can change, so a traffic spike doesn't turn into an unlimited bill. Pro also adds team features, email support, 6,000 deployments a day, longer function durations and bigger build machines. Password protection for a project costs $20 a month extra.
Enterprise adds a 99.99% uptime SLA, multi-region compute with failover, SCIM and advanced support, at a custom price.
What Vercel would cost you
Strengths and weak spots
What Vercel does well
- Deploys are effortless: Git push, preview links per branch, instant rollbacks.
- First-class Next.js, from the team that builds it.
- Viewer seats are free, so designers and clients can review previews at no cost.
- Spend management with a default budget limits surprise bills.
What to watch
- Hobby isn't for business, even for a tiny commercial site with almost no traffic.
- Usage billing takes attention. Heavy server-side rendering, image optimisation or chatty APIs can grow the bill; watch the usage dashboard.
- Per-seat pricing means every developer who deploys costs $20 a month.
- Long-running back-end work (queues, databases, big jobs) is usually better hosted elsewhere and called from Vercel.
Who Vercel is for
Personal projects: Hobby. Anything for a client or a business: Pro, and set a spending budget on day one.
Vercel suits front-end teams, agencies and startups that want fast, low-maintenance deploys, especially with Next.js. A mostly static company site with modest traffic usually stays close to one $20 Pro seat a month, because the usage credit covers light use. Apps with heavy server work or very high traffic should model usage first, and compare Netlify, Cloudflare Pages or a plain server.
What to look for
- Decide if the project is commercial. If it is, budget for Pro from the start.
- Count deploying developers; reviewers can be free viewers.
- Set a spend limit and usage alerts before launch.
- Cache and pre-render what you can: static pages and cached images cost far less than functions.