Deploy a Next.js app to production

Next.js apps deploy on DployHub with no configuration in most cases. When next is in your dependencies we treat the project as a Node.js server, run your build script and start the app with next start, so server components, API routes and server-side rendering all work as they do locally.

What gets detected

• Package manager from your lockfile: pnpm, yarn or npm.
• Build command: your build script, normally next build.
• Start command: your start script if you have one, otherwise npx next start.
• Port: taken from the start script if it sets one (for example next start -p 4000), otherwise 3000.
• Base image node:20-alpine with NODE_ENV=production.

A standard Next.js package.json needs nothing extra:

{
  "scripts": {
    "dev": "next dev",
    "build": "next build",
    "start": "next start"
  },
  "dependencies": {
    "next": "14.2.5",
    "react": "18.3.1",
    "react-dom": "18.3.1"
  }
}

Deploy steps

1. 1

   Create the app

   Go to New app, choose GitHub or a Public Git URL and select your repository and branch.

2. 2

   Keep auto-detection

   Leave "Figure it out for me" selected. For a monorepo, set Folder with your app, for example apps/web.

3. 3

   Add environment variables

   Add any API keys or database URLs your app needs. You can do this after creating the app in the Environment variables tab, then redeploy.

4. 4

   Pick resources and create

   Next.js builds can be memory-hungry; 1 GB of memory is a comfortable starting point for most apps.

Environment variables and builds

Environment variables are set separately for staging and live, are encrypted at rest and are shown masked until you click Reveal. Changes apply on the next deploy or restart, so redeploy or restart after saving. Use Copy from staging to bring a tested set of variables across to live. Keep secrets such as database URLs and API keys here rather than in .env files committed to the repository.

Static export

If you use output: 'export' and have no server, you can serve the generated out folder as a static site by choosing Static website or providing a small Dockerfile. Most Next.js apps should simply run as a server with next start.

Troubleshooting

• Build killed or exit code 137: raise memory in Settings, Resources. See App crashed: out of memory.
• App didn't answer on the port: check that the port in Settings matches what next start uses. See Port and health checks.
• Health check returns 5xx: point the health check path at a page that renders without external services.

The short version of this guide is at /deploy/nextjs. If something still fails, raise a ticket with the deployment attached.