Deploy Nuxt to your own machine.

Depfloy builds your Nuxt app on the server and runs the Nitro output as a supervised process behind nginx. Releases go live with a symlink flip, so a failed build never replaces the running site.

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
The Nitro server is started directly

Depfloy launches the server with exec rather than through an npm wrapper, so DPM — the process manager it installs on the server — watches the real Node process. That is what makes its memory reporting accurate and its shutdown signal actually reach the app. DPM runs as a systemd service enabled at boot, so a reboot brings the Nitro server back on its own.

nginx serves the static output

Public assets are served by nginx instead of being proxied through Node, and TLS certificates are issued and renewed for you.

Roll back to a selected commit

Nuxt rollback queues a new deployment that rebuilds the selected commit. Allow time for the build and check that your current environment and database are compatible with the target code.

Nuxt runs on Depfloy the way it runs on any Node host — the difference is that you choose the server capacity. Depfloy charges a flat plan; bandwidth and storage costs depend on your hosting provider.

FAQ

Nuxt questions

Does this work with server-side rendering? +
Yes. The Nitro node-server output is what gets run, so SSR, server routes and middleware behave as they do locally.
Can I run more than one Nuxt app on a server? +
Yes. Each project gets its own port, process and nginx site, and they are managed separately from the same dashboard.
How do I set runtime config? +
Environment variables are managed per project and written to the server before the build, so both build-time and runtime config 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 on the server and moves them across, with a --dry-run flag to show the plan first.

9 other frameworks deploy the same way.

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

Laravel Next.js Astro Remix React Router WordPress Symfony Statamic PHP

Deploy Nuxt 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