Hosting for Next.js apps

What this page covers

• SSR / App Router
• .next and next start
• next dev server port vs production PORT
• Node version + packageManager
• ENV and NEXT_PUBLIC_*
• HTTPS on Node Pro

How to deploy

1. ZIP or public GitHub with package.json and a Next.js project.
2. Add required ENV (API secrets, DATABASE_URL, etc.) — we set PORT for you.
3. Deploy → npm/pnpm/yarn install + build + start → HTTPS on *.deployka.dev.

Production scripts in package.json

Merge scripts into your existing package.json and keep dependencies. Build first, then use next start; next dev is not the production server. The platform supplies PORT in the environment.

{
  "scripts": {
    "build": "next build",
    "start": "next start --hostname 0.0.0.0"
  }
}

ENV you need

• PORT — system var, set automatically.
• NEXT_PUBLIC_* — public client variables.
• Server secrets (API keys, DATABASE_URL) — dashboard ENV only, never in the repo.

Package managers and stack

• npm
• pnpm
• yarn — detected from the lockfile in the project root

Common failures

• Build fails on missing module — check the lockfile and that runtime deps are in dependencies, not only devDependencies.
• App listens on localhost / wrong PORT — Deployka sets PORT; your start script must read it.
• Do not run the Next.js dev server in production: use next build, then next start with the platform PORT and a 0.0.0.0 bind.
• Runtime ENV errors — open Deploy Doctor or dashboard logs before redeploying.

Pricing

For Next.js / Nuxt / SSR we usually recommend Node Pro — $8.78/mo (2 vCPU, 1.5 GB RAM). Fixed price, no surprise bandwidth fees.

Useful links

See also