Runtime and processes
Check Node applications with a long-running process, dependency builds, environment variables, reverse proxying, logs, restarts, and possibly workers or queues.
Node application hosting
Run your Node.js application as a managed process on your own VPS. Configure environment variables, logs, ports and restarts for production.
Hosting options
Shared hosting for websites, email and PHP applications, with Virtualmin included.
See Web hosting →02Help moving websites, databases and email. We agree on the scope and cutover details before the move.
See Migration help →03Register or transfer a domain and manage DNS. Registration and renewal prices depend on the extension.
See Domains →04Tell us what you need to host and when it needs to be ready.
See Ask about your project →Your requirements
Check Node applications with a long-running process, dependency builds, environment variables, reverse proxying, logs, restarts, and possibly workers or queues.
Identify databases, uploads, volumes, configuration and secrets that cannot be rebuilt from the application code. Back them up and test a restore.
List the ports that must be public and those that should remain private. Configure authentication, TLS and firewall rules before accepting traffic.
Check how the service starts after a reboot, where logs are stored and who applies updates. Test a deployment and rollback without changing live customer data.
Field guide
Node runs JavaScript on a single main thread per process, so one blocked event loop stalls every request that process serves. Use a process manager such as PM2 or systemd to restart crashes, and run one process per CPU core in cluster mode or as separate instances when a single process stops scaling.
Memory limits matter because Node raises its heap ceiling only when told to, and an out of memory kill looks like a random restart. Set the max old space size deliberately, watch the event loop lag in your metrics, and keep node_modules builds reproducible with a lockfile so a deploy never depends on live package resolution.
Track event loop delay alongside CPU and memory. Rising lag with low CPU points at synchronous work such as large JSON parsing or crypto running on the main thread.
Restart the process on every deploy and confirm the new process ID is serving traffic. Long running Node processes keep old code in memory indefinitely.
Decide whether the proxy buffers request bodies for uploads. Mismatched buffering and timeout settings between proxy and app cause failed large uploads.
Planning
Confirm the current product specifications and service responsibilities. Record who can approve a change and how to recover the service if it goes wrong.
Use the detailed checklist to plan setup, access, migration and recovery with your team.
Download PDF →Send us the software you use, your storage needs and your launch or moving date.
Ask about hostingYour current site stays online until your new one is ready. You approve the copy first, and if anything is not right we switch you back right away. The price you pick is the price you renew at.