Next.js on Vercel
Vercel publishes its own guide for deploying Next.js.
React framework with file-based routing, server components and a build step that produces both static and server-rendered output.
What Next.js needs.
Every host claims to run Next.js, so the claim on its own decides nothing. These are the things Next.js actually requires from the platform underneath it, and what Vercel publishes about each. Vercel documents 6 of the 6.
Max request duration
Hobby: 300s default and maximum. Pro and Enterprise: 300s default, 800s maximum, and 1800s extended maximum
Server components and route handlers run per request. The wall-clock ceiling decides whether a slow upstream API or a model response can finish at all.
Sources (1) →Sources ↓
- Functions limitations — Vercel Docs ↗
“Default Maximum Extended maximum Hobby 300s (5 minutes) 300s (5 minutes) - Pro 300s (5 minutes) 800s 1800s (30 minutes) Beta Enterprise 300s (5 minutes) 800s 1800s (30 minutes) Beta”
Read 2026-09-13 · official docs
Streaming response limit
Edge runtime streaming: up to 300 seconds, provided the response starts within 25 seconds. For Node.js/Bun/Python runtimes the docs state that max duration covers streamed responses too (Pro: 300s default, 800s maximum). Not plan-differentiated for the Edge figure.
The App Router streams the dynamic parts of a page as they resolve. A host that buffers the whole response first removes the benefit.
Sources (1) →Sources ↓
- Vercel Functions Limits ↗
“Vercel Functions using the Edge runtime must begin sending a response within 25 seconds to maintain streaming capabilities beyond this period, and can continue streaming data for up to 300 seconds.”
Read 2026-09-05 · official docs
Edge network
Supported
Middleware runs on every matched request before the cache is consulted. Where it executes decides how much latency it adds.
Sources (1) →Sources ↓
- Vercel CDN overview ↗
“Vercel operates 126 Points of Presence (PoPs) across 51 countries.”
Read 2026-09-05 · official docs
Build allowance
No monthly build-minute allowance. Build CPU minutes are billed from $0.0035 each on Pro, against the plan's usage credit, and any single build is capped at 45 minutes.
A large Next.js app prerenders at build time, so the build allowance is a recurring cost rather than a one-off.
Sources (1) →Sources ↓
- Limits — Vercel docs ↗
“Build Time per Deployment (Minutes) 45 45 45 [...] Build CPU Minutes Starting at $0.0035 per CPU Minute [...] The maximum duration of the Build Step is 45 minutes. When the limit is reached, the Build Step will be interrupted and the Deployment will fail.”
Read 2026-09-06 · official docs
Git deployment
Supported
The Next.js workflow assumes a push builds and ships. A host without git-triggered deploys means wiring CI yourself before the first deploy, which is most of the setup cost.
Sources (1) →Sources ↓
- Deploying Git Repositories with Vercel — Vercel Docs ↗
“Vercel allows for automatic deployments on every branch push and merges onto the production branch of your GitHub, GitLab, Bitbucket, Origin, and Azure DevOps Pipelines projects.”
Read 2026-09-14 · official docs
Concurrent builds
Pro: up to 500 concurrent deployments with on-demand concurrency, or 3 if on-demand concurrency is off
Next.js builds are slow enough that queueing is felt. One build at a time is workable alone and becomes the bottleneck the moment two people merge in the same hour.
Sources (1) →Sources ↓
- Managing builds — Vercel Docs ↗
“Concurrency limits by plan Hobby: 1 concurrent deployment. Builds beyond this run sequentially. Pro: Up to 500 concurrent deployments with on-demand concurrency (3 if on demand is off). You are billed for the build minutes you use. Enterprise: Custom concurrency limits tailored to your organization's needs.”
Read 2026-09-14 · official docs
What Vercel documents.
Vercel publishes its own guide for deploying Next.js.
Next.js is a fullstack React framework for the web, maintained by Vercel.
Sources (1) →Sources ↓
- Next.js on Vercel ↗
“Next.js is a fullstack React framework for the web, maintained by Vercel.”
Read 2026-09-05 · official docs
Next.js features on Vercel
Capabilities Vercel documents specifically for Next.js, with the constraint it documents alongside each.
Image optimization
Supported
When deploying to Vercel, images are automatically optimized on demand, keeping your build times fast while improving your page load performance and Core Web Vitals.
Middleware
Supported
When deploying middleware with Next.js on Vercel, you get access to built-in helpers that expose each request's geolocation information. You also get access to the NextRequest and NextResponse objects, which enable rewrites, continuing the middleware chain, and more.
ISR / revalidation
Supported
Vercel's CDN provides fully managed caching and routing when you implement ISR with frameworks like Next.js, SvelteKit, Nuxt, and Astro.
Streaming SSR
Supported
When you deploy to Vercel, the static shell is served with Incremental Static Regeneration (ISR), while Vercel Functions renders the dynamic holes and streams the content back in the same response.
Sources (2) →Sources ↓
- Next.js on Vercel ↗
“When deploying to Vercel, images are automatically optimized on demand, keeping your build times fast while improving your page load performance and Core Web Vitals.”
Read 2026-09-05 · official docs
- Incremental Static Regeneration (ISR) ↗
“Vercel's CDN provides fully managed caching and routing when you implement ISR with frameworks like Next.js, SvelteKit, Nuxt, and Astro.”
Read 2026-09-05 · official docs
What it costs to run there.
- Entry paid plan
- $20 per developer seat / month (Pro)
- Pricing model
- Per-seat subscription plus metered resource usage; CDN charges cover requests, data transfer to visitors and Fast Origin Transfer, and vary by the region a request comes from.
- When you exceed a cap
- Billed automatically: extra usage beyond the included amount or Pro credit is charged, not throttled or suspended
- Regions
- 20 compute-capable regions, from Stockholm and Mumbai to Cleveland and Cape Town; functions default to iad1 (Washington, D.C.).
Sources (4) →Sources ↓
- Vercel Hobby Plan ↗
“Developer seats cost $20 per user / month, while Viewer seats are free”
Read 2026-09-05 · official docs
- CDN — Vercel Docs ↗
“CDN pricing covers CDN requests, data transfer to visitors, and Fast Origin Transfer. Pricing can vary by the region where requests originate. CDN requests appear as Edge Requests in Billing and on the Usage page.”
Read 2026-09-14 · official docs
- Pricing on Vercel ↗
“Some resources include an amount of usage your projects can use within your billing cycle. Pro teams also receive a monthly usage credit and can use many resources on demand. If you exceed an included amount or credit, Vercel charges for the extra usage.”
Read 2026-09-05 · official docs
- Regions — Vercel Docs ↗
“Vercel regions: Behind these PoPs, we maintain 20 compute-capable regions where your code can run close to your data. [...] Vercel Functions default to running in the iad1 (Washington, D.C., USA) region.”
Read 2026-09-14 · official docs
Whether it suits you.
Teams building on a framework the CDN understands natively, who want a predictable per-seat cost with metered usage on top. The Git integration covers GitHub, GitLab, Bitbucket and Azure DevOps, so it drops into an existing review workflow.
Consider something else if…
The team is large enough that $20 per developer seat dominates the bill rather than the metered usage underneath it.
Visit Vercel documentation