Deploying Next.js – Node.js Server, Docker Container, Static Export, and Platform Adapters

Next.js can be deployed as a Node.js server, Docker container, static export, or adapted to platform-specific infrastructure. This article explains each deployment method, feature support, development tips, and how to upgrade to the latest or canary versions of Next.js..

Next.js deploymentNode.js serverDocker containerVersion upgrade

~2 min read · Updated Oct 25, 2025

Deployment Options in Next.js


Next.js supports multiple deployment strategies:

Deployment MethodFeature Support
Node.js serverFull
Docker containerFull
Static exportLimited
AdaptersPlatform-specific

Deploying as a Node.js Server


To deploy on any Node.js-compatible provider, ensure your package.json includes:

{
  "scripts": {
    "dev": "next dev",
    "build": "next build",
    "start": "next start"
  }
}

Run npm run build to build and npm run start to launch the server. This method supports all Next.js features.


Recommended platforms: Flightcontrol, Railway, Replit


Deploying with Docker


Next.js can run in any Docker-compatible environment, including Kubernetes or cloud providers.


Note for development: On Mac and Windows, use npm run dev for better performance during development.


Recommended platforms: Docker, DigitalOcean, Fly.io, Google Cloud Run, Render, SST


Deploying as a Static Export


Next.js can be exported as a static site or SPA and hosted on any server that serves HTML/CSS/JS files.


Recommended platforms: AWS S3, Nginx, Apache, GitHub Pages


Limitation: Server-dependent features are not supported in this mode.


Deploying with Platform Adapters


Next.js can be adapted to run on specific platforms. Refer to each provider’s documentation for feature support:

  • AWS Amplify Hosting
  • Cloudflare
  • Deno Deploy
  • Netlify
  • Vercel

A Deployment Adapters API is in development to support custom adapters across platforms.


Upgrading Next.js


Latest Stable Version


To upgrade to the latest stable version:

npx @next/codemod@latest upgrade latest

Or install manually:

pnpm i next@latest react@latest react-dom@latest eslint-config-next@latest

Canary Version


To upgrade to the canary version:

npm i next@canary

Features available in canary:

  • Caching: "use cache", cacheLife, cacheTag, cacheComponents
  • Authentication: forbidden, unauthorized, forbidden.js, unauthorized.js, authInterrupts

Conclusion


Next.js offers flexible deployment options. Whether you choose Node.js, Docker, static export, or platform adapters, you can tailor deployment to your infrastructure and keep your project up-to-date with the latest features.


Written & researched by Dr. Shahin Siami

Related Articles

Advanced Client-Side Routing and Performance Hooks in Next.js

Next.js provides a rich set of client-side hooks and caching utilities that empower developers to build dynamic, responsive, and secure applications. From reading route parameters to tracking navigation state and reporting performance metrics, this guide walks you through the most important tools available in the App Router.

Continue

Handling Authorization and Caching in Next.js: A Developer’s Guide

Next.js introduces powerful experimental features for access control and smart caching. This guide covers the unauthorized() function for custom 401 handling, unstable_cache for persistent memoization, updateTag for instant cache invalidation, and useLinkStatus for inline navigation feedback. Learn how to use these tools to build secure, performant, and responsive applications.

Continue

redirect and refresh in Next.js — Smart Redirects and Client Refreshing via Server Actions

The redirect function in Next.js allows you to navigate users to a new route, returning either a 307 or 303 HTTP response depending on context. It works in Server Components, Client Components, Route Handlers, and Server Actions. The refresh function is used exclusively within Server Actions to refresh the client router. This article explains how both functions work, with practical examples and key considerations.

Continue

NextRequest and NextResponse in Next.js — Managing Cookies, Headers, Redirects, and Rewrites

Next.js extends the native Web Request and Response APIs with NextRequest and NextResponse, offering powerful tools for managing cookies, headers, redirects, rewrites, and JSON responses. These utilities simplify server-side logic and improve control over routing, personalization, and security. This guide walks through their capabilities with practical examples and best practices.

Continue

headers, ImageResponse, notFound, and permanentRedirect in Next.js — Request Handling, Dynamic Images, Errors, and Redirects

Next.js offers powerful tools for handling HTTP requests and responses in Server Components. The headers function lets you read incoming request headers. ImageResponse allows you to generate dynamic images using JSX and CSS. The notFound function renders a custom 404 page, and permanentRedirect enables permanent redirection to another route. This article explains how to use each feature with practical examples.

Continue

A Complete Guide to Using metadata and generateMetadata in Next.js

In modern versions of Next.js, managing page metadata is more powerful and intuitive than ever. Metadata is automatically injected into the <head> of your pages and plays a vital role in SEO, social sharing, and user experience. This guide explains the two main ways to define metadata: using the static metadata object and the dynamic generateMetadata function.

Continue