Docs

Deploy Next.js on Deployxa.

Deploy Next.js with the App Router, Server Components, API routes and middleware, running as a long-lived Node.js server with HTTPS and health checks.

All frameworks

01 / Quickstart

Deploy from your terminal.

Install the CLI and deploy the Next.js project in your current directory, or connect the repository in the console for push-to-deploy.

  • Typical database: PostgreSQL with Prisma or Drizzle
  • Build and start commands can be overridden
  • Secrets stay out of build logs
Read the docs
deploy · nextjs
$ npm install -g @deployxa/cli$ deployxa login$ deployxa deploy

02 / Guide

How Next.js goes to production.

  1. 01 /

    Connect the repository

    Deployxa finds next.config.js and installs dependencies with npm, pnpm or yarn based on your lockfile.

  2. 02 /

    Build

    next build runs in an isolated sandbox. Set output: "standalone" for a smaller runtime image.

  3. 03 /

    Attach data

    Add a managed PostgreSQL database; DATABASE_URL is injected for Prisma or Drizzle.

  4. 04 /

    Go live

    The release is health-checked, served over HTTPS and gets a deployxa.online URL or your own domain.

03 / Configuration

Environment variables.

Set these in project settings. Values are never written to build logs.

Recommended environment variables for Next.js
VariablePurposeExample
NODE_ENVRuntime modeproduction
NEXT_PUBLIC_API_URLPublic API endpoint exposed to the browserhttps://api.example.com
DATABASE_URLConnection string for Prisma or Drizzlepostgresql://...

04 / Included

What every deploy gets.

  • Stack detection

    Deployxa reads your repository and picks the runtime, build and start commands. Override any of them in project settings.

  • Isolated builds

    Every push builds in its own sandbox with cached dependencies and layers.

  • Managed databases

    Attach PostgreSQL, MySQL or Redis and the connection details are injected as environment variables.

  • HTTPS by default

    Every deploy gets a deployxa.online URL with a Let's Encrypt certificate; custom domains too.

  • Health-checked releases

    Traffic only switches to a release that passes its health check, and earlier releases stay available for rollback.

  • Push to deploy

    Connect GitHub, GitLab or Bitbucket and each push to your branch ships a new release.

05 / FAQ

Next.js questions.

Are the App Router and Server Actions supported?

Yes. Your app runs as a Node.js server, so the App Router, React Server Components, Server Actions, route handlers and middleware work as they do locally.

Is there a function timeout?

No per-request function timeout applies. The app is a persistent Node.js process rather than serverless functions.

Ready when you are

Ship your Next.js app.

Connect a repository and get a live HTTPS URL.

See pricing