| Region | Active CPU/hr | Memory/GB-hr |
|---|
| Cleveland (cle1) | $0.128 | $0.0106 |
| Portland (pdx1) | $0.128 | $0.0106 |
| Washington D.C. (iad1) | $0.128 | $0.0106 |
| Mumbai (bom1) | $0.140 | $0.0116 |
| Montreal (yul1) | $0.147 | $0.0122 |
| Singapore (sin1) | $0.160 | $0.0133 |
| Stockholm (arn1) | $0.160 | $0.0133 |
| Dublin (dub1) | $0.168 | $0.0139 |
| Seoul (icn1) | $0.169 | $0.0140 |
| Paris (cdg1) | $0.177 | $0.0146 |
| London (lhr1) | $0.177 | $0.0146 |
| San Francisco (sfo1) | $0.177 | $0.0147 |
| Sydney (syd1) | $0.180 | $0.0149 |
| Frankfurt (fra1) | $0.184 | $0.0152 |
| Hong Kong (hkg1) | $0.176 | $0.0146 |
| Tokyo (hnd1) | $0.202 | $0.0167 |
| Osaka (kix1) | $0.202 | $0.0167 |
| Cape Town (cpt1) | $0.200 | $0.0166 |
| Sao Paulo (gru1) | $0.221 | $0.0183 |
Memory is billed continuously while the instance is warm, even during idle periods. CPU only bills while code is actually executing. For an application with steady traffic, Provisioned Memory is typically the dominant cost line.
Side-by-side: Vercel vs Netlify vs Render
| Platform | Entry price | Free tier | Pricing model |
|---|
| Vercel Pro | $20/user/mo + $20 credit | Hobby free | Per-seat + usage |
| Netlify Pro | $20/mo (3K credits) | Free 300 credits | Credit-metered |
| Render Pro | $25/mo workspace | Hobby $0 | Workspace + per-service |
| Heroku Basic | $7/dyno | Eco $5/mo (limited) | Per-dyno |
| Railway Pro | $20/workspace/mo | Hobby $5/mo | Usage-based |
Vercel's per-seat model means team size drives the fixed cost line. Netlify's credit-metered model aligns cost with team usage. Render's workspace-plus-per-service model suits multi-service architectures. Heroku's per-dyno model is straightforward but scales linearly. Railway's usage-based model with included credits works well for variable workloads (Vercel docs; Netlify docs; Render docs; Heroku docs; Railway docs, 2026).
How to negotiate the best Vercel deal
Three negotiation levers for Vercel Enterprise contracts in 2026. First, time the deal to Vercel's fiscal quarter end (March, June, September, December). Sales teams have more flexibility to discount in the final two weeks of each quarter. Second, cite competing platforms — Netlify, Render, AWS Amplify, Cloudflare Pages all offer viable alternatives, and specific quotes consistently move Vercel pricing 10-20 percent.
Third, negotiate the add-on bundle. SAML SSO at $300/month, HIPAA at $350/month, and other Enterprise features can be bundled at lower combined pricing for multi-year commitments. Multi-year deals should include price-lock language for years 2-3 to protect against the platform's history of annual pricing increases (Vercel docs; Vercel blog, 2026).
What enterprise buyers should do next
Three actions for organizations evaluating Vercel in 2026.
- Set a realistic spend limit before launch. Default is $200 on-demand; configure a hard limit to prevent runaway costs during traffic spikes. Alerts fire at 80 percent and 100 percent of the budget.
- Pick the cheapest region that meets latency requirements. Cleveland and Portland are $0.128/hour Active CPU — 30-40 percent cheaper than San Francisco or Frankfurt. If your user base tolerates East Coast latency, the savings compound.
- Lock in Enterprise pricing with multi-year terms. Single-year Enterprise contracts are typically 15-25 percent higher than equivalent three-year commitments. Always negotiate price-lock language for years 2-3.
What to watch next
Three near-term datapoints. First, Vercel pricing changes — the platform has historically raised prices annually, and the credit-based model gives the vendor flexibility to adjust rates. Second, Fluid compute expansion to additional regions and ARM instances — ARM pricing tends to be 20-30 percent cheaper than x86 for comparable workloads. Third, the competitive landscape — Cloudflare Workers, Netlify Edge Functions, and Deno Deploy all offer per-request pricing models that can undercut Vercel for high-volume workloads.