Next.js · Deployment guide · Hosting

Deploy Next.js with the runtime made explicit.

SSR applications, API routes, static exports, and full-stack products backed by a managed database. Darwa AI connects the repository, runs npm run build, deploys the result on node.js server or static export, and keeps domains, HTTPS, releases, logs, and billing in the same workspace.

Node.js server or static export
Deployment model
npm run build
Build command
.next or out
Expected output
Web Hosting
Recommended Darwa product
Deployment contract

What a production Next.js deployment needs.

These are operational requirements, not a generic framework feature list. Confirm them in the repository before the first release.

01

Build

Use npm run build. Commit the lockfile and pin the runtime version so a rebuild installs the same dependency graph.

Review deployment docs →
02

Start

Production start: npm run start. The command must stay in the foreground and report a failed boot with a non-zero exit code.

Explore Web Hosting →
03

Artifact

Expected deployable output: .next or out. Generated artifacts should come from the build rather than being edited after release.

Configure the build →
04

Configuration

Store secrets and environment-specific values in the service environment. Do not commit production credentials or bake them into frontend bundles.

Manage configuration →
05

Health and logs

Expose a lightweight health endpoint, keep startup logs actionable, and verify the public endpoint after every release.

See runtime operations →
06

Known boundary

Edge runtime parity is not implied. Confirm every route's runtime and use Frontend Cloud only for a true static export.

Check a workload with Darwa →
Release path

From Next.js repository to a repeatable release.

A successful first deploy is not enough. The release must be reproducible, observable, reversible, and safe to scale.

Connect source01

Select the repository and production branch. Keep preview work isolated from the production service.

Detect and confirm02

Confirm node.js server or static export, the build command, output, and production start command instead of relying on a lucky default.

Add environment03

Set secrets and public configuration with the correct build-time or runtime scope.

Deploy and verify04

Watch the build, startup, and health checks; then exercise a real application path rather than only the homepage.

Attach the domain05

Point the domain after the generated endpoint is healthy. Managed HTTPS should complete before traffic is moved.

Plan rollback06

Keep the previous successful release available and make database changes backward-compatible before scaling replicas.

FAQ

Answers before you deploy.

Can Darwa AI host Next.js?+

Yes. SSR applications, API routes, static exports, and full-stack products backed by a managed database. The recommended starting product is Web Hosting, subject to the runtime boundary described on this page.

What build command should I use for Next.js?+

Start with npm run build. Keep the dependency lockfile committed and test the same command in a clean environment before deployment.

What starts Next.js in production?+

Use npm run start. A server deployment must listen on the assigned port, stay in the foreground, and exit when startup fails.

Can I connect a custom domain?+

Yes. Deploy to the generated endpoint first, verify health, then connect the domain and wait for managed HTTPS before moving traffic.

Where should secrets be stored?+

Use the service environment and keep production secrets out of Git, build logs, browser bundles, and image layers.

How do I deploy without downtime?+

Use health checks, backward-compatible data changes, a verified new release, and a retained previous release that can be restored quickly.