Node.js & Next.js Hosting for Your Apps and APIs

Next.js Deployment Example: Build, Run and Verify

For a standard Next.js project, commit your source and lockfile to Git and configure the build and start commands below. This example uses npm; use the package manager that matches your lockfile. Confirm the target branch and deployment integration with our team before your first release.

package.json scripts

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

Build and start commands

npm ci
npm run build
npm run start -- --hostname 0.0.0.0 --port 3000

Set the application port to 3000 and keep secrets in environment variables. Check the home page and a server-side route after deployment, review logs, then verify your domain and HTTPS. A successful build alone does not prove a working database or persistent uploads.

Check Plan Fit Before You Deploy

• CPU and RAM: use the plan limits below for your running workloads. Builds can need more memory than an idle app; confirm build capacity before choosing a small plan.
• Runtime: use a supported Node.js LTS release that your Next.js version supports. Confirm native dependencies, background workers and any required ports during onboarding.
• Storage and databases: arrange a persistent volume or external storage for uploads and application data. Confirm mount paths, database access and restore procedures; do not rely on a container write layer surviving a redeploy.
• Backups and staging: Builder and higher plans list these features. Confirm retention, restore scope and staging resource usage before treating them as your recovery plan.

If a Build or Deployment Fails

For out-of-memory builds, review build logs and memory needs before upgrading. If the app is unreachable, check its start command, port and 0.0.0.0 binding. If API requests fail, verify environment variables and database connectivity. For missing uploads after a release, check the persistent storage mount.