Vercel Pricing Calculator
Estimate your real monthly Vercel bill in seconds — and see what the same workload costs on every other platform.
1. Pick a workload
Choose the preset closest to your project. You can fine-tune the numbers in step 2.
2. Customize (optional)
Tweak the assumptions to match your real numbers.
Vercel Pro
Estimated monthly cost
Same workload, all providers
Estimated monthly cost — sorted cheapest first
Costs are estimates only. Tweak the workload above to see how each provider scales with your traffic. Think something is wrong?
What Vercel excels at
- Zero-configuration Next.js deployment — every new framework feature works on day one.
- Preview deployments for every pull request, out of the box.
- Fluid Compute: pay only for active CPU time, not wall-clock duration — I/O wait is free.
- 1 TB bandwidth included on Pro before any overage kicks in.
- Built-in Skew Protection prevents version mismatch errors on deploys (Pro+).
How Vercel pricing works in 2026
Vercel's Pro plan starts at $20/month per developer seat and meters managed infrastructure on top of that base. The big line items are Fast Data Transfer (1 TB included, then $0.15/GB in US regions), Edge Requests (10M included, then $2 per million), Fast Origin Transfer (no included tier; $0.06/GB in US regions), function Invocations (1M included, then $0.60 per million), and the Fluid Compute pair — Active CPU at $0.128/CPU-hour and Provisioned Memory at $0.0106/GB-hour, both with no included tier on Pro.
The number that surprises most teams is Edge Requests. They count every CDN hit — your HTML page, every JS chunk, every CSS file, every font, every image. A single page view on a modern Next.js app typically generates 25–40 edge requests. At 250k monthly visitors averaging 8 page views each with 35 assets per page, that's 70M edge requests — 60M of overage at $2/M = $120 before any function code runs.
The second surprise is Fluid Compute. Vercel replaced the old GB-Hour model with two separate dials: Active CPU (only billed while your code is running on a CPU — I/O wait doesn't count) and Provisioned Memory (billed for the full instance lifetime in GB-hours, including I/O wait). The split is friendlier for I/O-bound apps than the old model, but neither has an included tier on Pro — you pay from byte one.
How this calculator works
Pick a workload preset (or fine-tune the numbers under the advanced panel). The calculator estimates bandwidth as visitors × page views × page weight, edge requests as visitors × page views × assets-per-page + API requests, and the function cost as a combination of invocations, Active CPU (assumed at 40% of duration for typical I/O-bound routes), and Provisioned Memory. Build cost is deploys × build minutes × $0.0035/CPU-min on the default Elastic machine type.
Caveats
Pricing verified as of May 2026. Vercel revises its rate card periodically — confirm current rates on vercel.com/pricing before making a procurement decision. This calculator excludes ISR writes/reads, Image Optimization, Edge Config, WAF inspections, Speed Insights, Observability Plus, and Enterprise add-ons — they can add 10–30% on image- or ISR-heavy apps. Regional rates apply for non-US regions; we model US rates (iad1 / pdx1 / cle1).
MakerKit is built for Vercel
Next.js 16 App Router, ISR, edge middleware, and one-click Vercel deploy all pre-configured. Push to deploy.
Compare with other hosting providers: