Deploy React Router to your own server.
Depfloy builds your React Router app on the server and runs it as a supervised Node process behind nginx. A failed build is never linked, so the previous release keeps serving while you read the log.
- Runtime
- Node 24
- Releases
- Zero-downtime symlink flip
- Rollback
- One click; rebuild depends on runtime and retained releases
The serve command runs with exec, so DPM — the process manager Depfloy installs on the server — tracks the actual Node process. Memory figures are real and a stop signal reaches the app rather than a shell. DPM is a systemd service enabled at boot and keeps its process list on disk, so a reboot restores what was running.
Each project gets its own port and nginx site, so a single machine can carry a marketing site, an admin app and a staging copy without interfering.
Certificates are requested and renewed automatically per domain, including the ones you add later.
This site runs on the same model it describes: a React Router app was the previous generation of depfloy.com, deployed to a Depfloy-managed server.
React Router questions
Does this support the framework mode with SSR? + −
Can I deploy a SPA build instead? + −
How are deploys triggered? + −
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 React Router to your own server.
7 days free, no credit card. Your servers keep running exactly as Depfloy configured them.