Skip to content
OrbixPanel OrbixPanel Tutorials

Deploy a Next.js app on OrbixPanel

Next.js deploys as a Node server app: OrbixPanel builds it, runs next start behind a reverse proxy, and your domain points at it.

Requirements in your repo

Your package.json needs the standard scripts:

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

OrbixPanel runs npm ci → npm run build → npm start. Because a start script exists, it’s served as a live Node process (SSR, API routes, and app router all work).

The $PORT rule

next start automatically listens on the PORT environment variable, which OrbixPanel sets for you — so there’s nothing to configure. (If you use a custom server, make it listen on process.env.PORT.)

Deploy it

  1. Push your app to Git.
  2. In Apps → Deploy from Git, enter the repo URL and branch.
  3. Deploy. Watch the build log through building → active.
  4. Add your domain and request SSL.

See Deploy from Git for the full walkthrough.

Environment variables

Put API keys and database URLs in environment variables. Remember Next.js only exposes variables prefixed NEXT_PUBLIC_ to the browser — keep secrets unprefixed.

Just a static site?

If you use output: 'export' (no SSR, no API routes), Next.js produces a static out/ folder. That deploys as a static site — cheaper and faster, but you lose server features.

Troubleshooting

  • Builds but won’t go live → a custom server not reading process.env.PORT.
  • Build fails on memory → large Next builds are RAM-hungry; see disk & memory.

Running OrbixPanel? Next.js deploys straight from Git. OrbixPanel.com → — the free, self-hosted, AI-powered hosting control panel.