Vercel has become the default deployment platform for Next.js projects, and it is increasingly popular for other frameworks too. But their pricing page raises more questions than it answers for most teams. What actually counts toward your bandwidth limits? When does the free tier stop being enough? Is the Enterprise plan worth the sales conversation?
Let us break down what you actually get at each tier and where the costs can surprise you.
The Tier Structure
Vercel's pricing has three main tiers: Hobby (free), Pro ($20/user/month), and Enterprise (custom pricing). Each tier has different limits on builds, bandwidth, serverless function execution, and team features.
| Feature | Hobby (Free) | Pro ($20/user/mo) | Enterprise |
|---|---|---|---|
| Bandwidth | 100 GB | 1 TB (then $40/100GB) | Custom |
| Build minutes | 6,000 min/mo | 24,000 min/mo | Custom |
| Serverless function execution | 100 GB-hours | 1,000 GB-hours | Custom |
| Team members | 1 (personal) | Unlimited ($20 each) | Unlimited |
| Preview deployments | Yes | Yes + comments | Yes + SSO/SAML |
| Commercial use | No | Yes | Yes |
That "commercial use" row is worth highlighting. The Hobby tier explicitly prohibits commercial use. If you are building anything for a business... even a small one... you need Pro at minimum. This catches freelancers and startups who think they can run a client site on the free tier.
When Hobby Is Enough
The Hobby tier is genuinely useful for:
- Personal projects and portfolios. Your blog, your side project, your open-source documentation site. As long as it is not generating revenue.
- Learning and prototyping. Trying out Next.js, testing a new framework, building proof-of-concept apps.
- Open source projects. Vercel is generous with open-source. Many popular projects run on Hobby or have sponsored accounts.
The 100 GB bandwidth limit sounds low, but for a personal site it is plenty. A well-optimized static site might use 1-2 MB per page load. At that rate, 100 GB covers roughly 50,000-100,000 page views per month. If your personal blog is getting that much traffic, congratulations... and also, upgrade to Pro.
Pro: Where Most Teams Land
The Pro tier at $20/user/month is where most professional teams operate. The per-user pricing means costs scale linearly with team size, which is predictable but can add up. A team of five developers is $100/month before any usage overages.
What you get beyond Hobby that actually matters:
- Commercial use rights. You can legally run business sites. This alone forces the upgrade for any professional project.
- Team collaboration. Multiple team members with role-based access. Preview deployment comments for design and content reviews. This is genuinely useful for agency workflows where clients review deployments.
- Higher limits. 1 TB bandwidth, 24,000 build minutes, 1,000 GB-hours of serverless execution. For most sites, these limits are generous.
- Password-protected deployments. Preview deployments that require authentication. Important for client work and pre-launch reviews.
The catch is overages. If you exceed the included limits, you pay per-unit overage charges. Bandwidth overages at $40 per 100 GB can add up fast if you have a traffic spike or a heavy site. Serverless function execution overages can surprise you if you have an API-heavy application.
Enterprise: When You Need the Conversation
Enterprise pricing is not published because it is negotiated. What you get is primarily about compliance, security, and support:
- SLA guarantees. Uptime commitments with financial penalties for downtime. The Pro tier has no SLA.
- SSO and SAML. Enterprise identity provider integration. If your company requires SSO for all vendor tools, this is the tier you need.
- Dedicated support. Named account manager, priority support channels, faster response times. Pro support is adequate but not personalized.
- Custom limits. Negotiated bandwidth, build minutes, and execution limits that fit your usage pattern without overage surprises.
- Advanced security. SOC 2 compliance, audit logs, IP allowlisting, and deployment protection features.
The honest question to ask: does your organization require SLA guarantees or SSO? If yes, Enterprise is unavoidable. If no, Pro probably covers your needs. The features between Pro and Enterprise are mostly about corporate procurement requirements, not developer capabilities.
Hidden Costs to Watch For
Vercel's pricing is transparent in structure but the total cost depends on usage patterns that are not always obvious at the start:
- Serverless function cold starts and execution. If your Next.js app uses API routes or server-side rendering heavily, serverless execution costs can exceed the included allocation. Monitor your usage dashboard monthly.
- Image optimization. Vercel's image optimization counts against your usage. If you are serving a lot of images, this can be a significant cost driver. Consider whether a dedicated image CDN (Cloudinary, imgix) is more cost-effective for image-heavy sites.
- Build frequency. If your CMS triggers a rebuild on every content change and your content team publishes frequently, build minutes add up. Incremental static regeneration or on-demand revalidation can reduce build frequency significantly.
- Edge functions. Middleware and edge functions have their own limits and pricing. If you are using middleware for A/B testing, personalization, or geo-routing, factor in edge function invocations.
Alternatives Worth Considering
Vercel is excellent but it is not the only option. Depending on your requirements, alternatives might be more cost-effective:
- Netlify has a similar tier structure with different tradeoffs. Their Pro tier is $19/user/month and includes different limits. Worth comparing side-by-side for your specific usage pattern.
- Cloudflare Pages is free for unlimited bandwidth on static sites and has a generous free tier for serverless functions. If your site is static-first, this can be dramatically cheaper.
- AWS Amplify or self-managed infrastructure gives you more control over costs at the expense of operational complexity. For large-scale deployments, the per-unit costs are lower but the management overhead is real.
How We Think About Hosting Decisions
At Last Rev, we deploy on Vercel frequently, but we do not default to it for every project. The right hosting decision depends on the architecture, the traffic pattern, the team's operational capacity, and the budget.
For Next.js projects with server-side rendering, Vercel is often the best fit because the integration is seamless. For static sites, we evaluate whether a simpler CDN deployment makes more sense. For projects with specific compliance requirements, the hosting conversation is part of the architecture planning, not an afterthought.
The key is matching the hosting cost structure to your usage pattern. A site with steady traffic and infrequent builds has very different hosting economics than a site with spiky traffic and frequent content updates. Pick the pricing model that aligns with how your site actually operates.
Need help evaluating hosting options for your project? Let's walk through the tradeoffs together.