Hosting a Node.js app takes a few clear steps. Follow them and your app runs reliably for real users rather than just on your laptop.
To host a Node.js app, pick a VPS or cloud plan, install Node, run the app with a process manager, add a database and SSL, then put it behind a reverse proxy.
What a Node.js app needs
A Node.js app runs your JavaScript on the server. Unlike a static site, it runs a live process that must stay up, restart on crashes, and handle many requests at once. Your host has to support that.
The good news is the steps are the same across most hosts. Get them right once and your app runs steadily for users around the clock.
Pick the right host
Node apps run best on a VPS or cloud plan where you control the environment. Shared hosting rarely supports a long-running Node process. Our guide to the best hosting for Node.js apps covers plans that fit.
- Full server access. You install Node and manage the process yourself.
- Enough memory. Node apps use memory per connection, so size the plan to your load.
- A managed database. Keeps your data safe without extra admin.
Step one, set up the server
Start with a clean server on your VPS or cloud plan. Update the system, create a non-root user, and lock down access. Install the version of Node your app was built for, ideally using a version manager so upgrades stay simple.
Copy your code onto the server, or better, deploy it from Git so releases are repeatable. Install your dependencies and confirm the app starts by hand before you go further.
Never run a production app as the root user. A dedicated user limits the damage if your app is ever compromised, which is a simple and free layer of safety.
Step two, keep the app running
If you start your app by hand, it stops the moment the terminal closes or the app crashes. A process manager fixes that. It keeps your app alive, restarts it after a crash, and starts it again when the server reboots.
- Auto restart. The manager relaunches your app if it crashes.
- Boot on reboot. Your app comes back after a server restart.
- Log capture. Output is saved so you can debug issues later.
Step three, add a database
Most Node apps store data in a database such as PostgreSQL or MongoDB. Use a managed database where you can, so backups and patching are handled for you. Connect it with an environment variable rather than hard-coding the details.
Keep secrets out of your code. Store the database URL, API keys, and tokens in environment variables so they never end up in your Git history.
Step four, put it behind a reverse proxy
A reverse proxy such as Nginx sits in front of your app. It handles incoming traffic, serves your SSL certificate, and passes requests to Node on an internal port. That keeps your app off the public port and adds a layer of control.
- SSL. The proxy terminates HTTPS so user data travels safely.
- Load handling. It can spread traffic across several app processes.
- Static files. It serves images and assets faster than Node.
Step five, add SSL and go live
Install a free SSL certificate so your app runs over HTTPS. Point your domain at the server, confirm the proxy passes traffic to Node, and test the live app end to end.
Check logins, forms, and any API calls work in production, not just on your machine. Once everything holds up, your app is live for real users.
Keep it healthy
Hosting an app is not a one-time job. A little upkeep keeps it fast and safe over time.
- Monitor uptime. Get alerts the moment the app goes down.
- Watch memory. Node apps can leak memory, so track usage.
- Keep Node current. Update to patched versions for security.
- Back up the database. Confirm backups run and restore cleanly.
For a wider view of running an app in production, see our roundup of the best hosting for saas and our guide on how to scale a SaaS app once traffic grows.
A quick pre-launch checklist
Before you send real users to your app, run through a short list. Ticking these off catches the issues that most often trip up a fresh deploy.
- Process manager running. The app restarts on crash and starts on reboot.
- Environment variables set. Database URL, keys, and secrets are out of the code.
- SSL active. Every page loads over HTTPS with a valid certificate.
- Database connected. The app reads and writes cleanly, with backups on.
- Logs captured. Output is saved so you can debug problems in production.
Work through the list in order and nothing slips through the cracks. A calm, checked launch beats a rushed one where you discover a missing SSL certificate or a broken database link only after users start complaining.
What to do after launch
Getting the app live is the start, not the finish. A little routine care keeps it fast and safe as real users arrive and traffic grows over the weeks that follow.
Watch your logs for errors, keep an eye on memory use, and update Node to patched versions when they land. Test your database restore now and then so you know it works, and set uptime alerts so you learn about problems before users do. With those habits in place, your Node app runs quietly in the background while you focus on building features.
Frequently asked questions
Can I host a Node.js app on shared hosting?
Rarely. Shared hosting seldom supports a long-running Node process. A VPS or cloud plan gives you the control to install Node, run a process manager, and keep your app alive around the clock.
Why do I need a process manager?
A process manager keeps your app running. It restarts the app after a crash, brings it back after a server reboot, and captures logs. Without one, your app stops the moment the terminal closes or it crashes.
Do I need a reverse proxy for a Node app?
It is strongly recommended. A reverse proxy like Nginx handles SSL, serves static files, and passes traffic to Node on an internal port. That keeps your app off the public port and adds control.
Where should I store database passwords?
In environment variables, never in your code. That keeps secrets out of your Git history and makes it easy to change them without a redeploy. The same goes for API keys and tokens.
How do I keep a Node app running after reboot?
Use a process manager set to start on boot. It relaunches your app when the server restarts, so a reboot or crash never leaves your app offline for long.
