# Next.js on Vercel

Canonical: https://inetgeek.com/stacks/nextjs-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 requires from the platform underneath it, and what Vercel publishes about each. Vercel documents 6 of the 6.

| Requirement | Vercel | Why it matters |
| --- | --- | --- |
| 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. |
| 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. |
| Edge network | Supported | Middleware runs on every matched request before the cache is consulted. Where it executes decides how much latency it adds. |
| 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. |
| 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. |
| 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. |

- Max request duration source: https://vercel.com/docs/functions/limitations
- Streaming response limit source: https://vercel.com/docs/functions/limitations
- Edge network source: https://vercel.com/docs/cdn
- Build allowance source: https://vercel.com/docs/limits
- Git deployment source: https://vercel.com/docs/git
- Concurrent builds source: https://vercel.com/docs/builds/managing-builds

## What Vercel documents

> Next.js is a fullstack React framework for the web, maintained by Vercel.

Source: https://vercel.com/docs/frameworks/full-stack/nextjs

### Next.js features on Vercel

- **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. ([source](https://vercel.com/docs/frameworks/full-stack/nextjs))
- **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. ([source](https://vercel.com/docs/frameworks/full-stack/nextjs))
- **isr**: Supported — Vercel's CDN provides fully managed caching and routing when you implement ISR with frameworks like Next.js, SvelteKit, Nuxt, and Astro. ([source](https://vercel.com/docs/incremental-static-regeneration))
- **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. ([source](https://vercel.com/docs/frameworks/full-stack/nextjs))

## What it costs to run there

|  | Vercel |
| --- | --- |
| 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.). |

- Entry paid plan source: https://vercel.com/docs/plans/hobby
- Pricing model source: https://vercel.com/docs/cdn
- When you exceed a cap source: https://vercel.com/docs/pricing
- Regions source: https://vercel.com/docs/regions

## 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.

Written by Palash Bagchi on 2026-09-05. This is a recommendation, not a sourced fact — it carries no citation because it is an opinion.

## Related

- Best hosting for Next.js: https://inetgeek.com/stacks/nextjs/
- Vercel: https://inetgeek.com/hosting/vercel/