Deploy Next.js without a usage meter.

Depfloy builds your Next.js app on your own server and starts it as a supervised process behind nginx. Bandwidth, builds and function invocations are not metered, because there is nothing to meter — you rent the machine.

Start free trial Read the docs
What runs on the server
Runtime
Node 24
Releases
Zero-downtime symlink flip
Rollback
One click; rebuild depends on runtime and retained releases
The deploy script Depfloy runs
npm ci
npm run build
DPM keeps the app running, and brings it back after a reboot

Node apps run under DPM, the process manager Depfloy installs on the server. It is registered as a systemd service and enabled at boot, and it keeps its process list in a local database — so a machine that restarts brings the app back up without anyone logging in to run a command. It restarts the app if it exits, and the memory figure next to the project is the one the process is actually using.

nginx handles TLS and static files

Certificates are issued and renewed automatically, and nginx serves the build output directly instead of proxying every asset through Node.

Env vars are on the server before the build

Variables are written to the server first, so anything the build reads at compile time is already there when npm run build starts.

Next.js on your own server behaves like Next.js anywhere else — the difference is that you choose the capacity and pay your provider for it. Provider charges may include storage and bandwidth. The app runs as a supervised process you can open a terminal to.

Replacing that process without dropping a request is the part worth reading about before you need it: how a zero-downtime Next.js deploy switches over walks through the standby port, the stability soak and what keeps serving when a release goes bad.

FAQ

Next.js questions

Do I need a separate host for the database? +
No. Provision PostgreSQL or MySQL on another server you own and connect over the private network, or run it on the same machine for smaller projects.
Does this support the App Router and server components? +
Yes. Depfloy runs the standard production server, so anything that works with next start works here.
What about environment variables? +
They are managed per project from the dashboard and written to the server before the build runs, so build-time variables are available.
We run these under PM2 today. What happens to those processes? +
Depfloy does not use PM2. Node apps run under DPM, and the DPM repository ships a migration script that reads the PM2 processes and Supervisor programs already running on the server and moves them across. It takes a --dry-run flag, so you can see what it would do before anything changes.
Is restarting the app zero-downtime? +
If the app runs more than one worker, DPM cycles them one at a time and the others keep serving. With a single worker there is nothing left to serve during the swap, so a restart is a short gap. A deploy is a different path — the new release is built next to the running one and goes live with a symlink flip.

9 other frameworks deploy the same way.

The release model is identical; only the build steps differ.

Laravel Nuxt Astro Remix React Router WordPress Symfony Statamic PHP

Deploy Next.js to your own server.

7 days free, no credit card. Your servers keep running exactly as Depfloy configured them.

Start free trial How releases work