Deploy Remix without renting a platform.
Depfloy builds Remix on your server and runs it as a supervised process behind nginx. Each deploy is a new release directory; going live is a symlink flip that never interrupts a request.
- Runtime
- Node 24
- Releases
- Zero-downtime symlink flip
- Rollback
- One click; rebuild depends on runtime and retained releases
The app is launched with exec instead of through a shell wrapper, so restarts, memory limits and graceful shutdown act on the Node process itself. The owner is DPM, the process manager Depfloy installs — a systemd service enabled at boot, which is what makes a reboot uneventful rather than a thing you find out about.
There is no function boundary and no invocation count — server code runs in the same long-lived process as the rest of the app.
nginx serves the build output directly, which keeps asset requests off the application process entirely.
Remix and React Router share a lineage, and on Depfloy they share a deployment model too: build on the server, run as a supervised process, flip a symlink to go live.
Remix questions
Is this the Remix app server or a custom one? + −
What happens to in-flight requests on deploy? + −
Can I use a database on the same server? + −
We run these under PM2 today. What happens to those processes? + −
9 other frameworks deploy the same way.
The release model is identical; only the build steps differ.
Deploy Remix to your own server.
7 days free, no credit card. Your servers keep running exactly as Depfloy configured them.