Delivery for Next.jss
Delivery in Next.js is the process of building the app and running it in production. next build compiles the routes, then the app runs on Vercel, a Node.js server, a Docker container or as a static export. Environment variables, caching behaviour and build output differ between these targets.
Stage: Production · Part of the Next.js roadmap · Last reviewed 19 November 2026
What to learn in Delivery
- Run next build and read the route summary it prints
- Deploy a Next.js app to Vercel from a Git repository
- Containerise the app with Docker using the standalone output mode
- Set production environment variables on the hosting platform
- Decide when a static export is enough and when a server is required
Delivery interview questions
What does next build produce, and how is it started?
It compiles the app into an optimised .next folder with prerendered pages, server bundles and static assets. You then run next start for a Node.js server, or use the standalone output to copy a minimal runnable folder into a Docker image.
When can a Next.js app be deployed as a static export?
When every page can be built ahead of time and nothing needs per-request server work. Features such as Server Actions, cookies based sessions, middleware and on-demand revalidation need a running server, so they are not available in a pure static export.
Where Delivery fits in the Next.js roadmap
Delivery belongs to the Production stage (advanced level), which takes about 12 hours. Test and deploy.
Other units in this stage
Back to the full Next.js roadmap