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 3 of the 4.
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 ↓
- Vercel Functions Limits - Vercel Docs ↗
“Maximum duration | Hobby: 300s default and maximum. Pro and Enterprise: 300s default, 800s maximum, and 1800s extended maximum .”
Read 2026-09-05 · 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 minutes
Not documented
A large Next.js app prerenders at build time, so the build allowance is a recurring cost rather than a one-off.
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
- When you exceed a cap
- Billed automatically: extra usage beyond the included amount or Pro credit is charged, not throttled or suspended
- Regions
- 126 PoPs across 51 countries
Sources (3) →Sources ↓
- Vercel Hobby Plan ↗
“Developer seats cost $20 per user / month, while Viewer seats are free”
Read 2026-09-05 · official docs
- Vercel CDN overview ↗
“CDN pricing covers three billable resources: Edge Requests, Fast Data Transfer, and Fast Origin Transfer.”
Read 2026-09-05 · 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
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