A VPS gives you a whole Linux server for your Node.js app: full control, root access, any software you like, and every bit of maintenance is yours. Managed app hosting gives you a place to push code: the provider runs the server, the Node.js runtime, process restarts, SSL and deploys, and you give up low-level control. The monthly price is only part of the comparison; the bigger cost is usually your own time spent on setup, patching and fixing things at inconvenient hours. This guide lists exactly what a VPS asks of you so you can put a real number on it.
What you do on a VPS
Getting a Node.js app running properly on a fresh VPS involves a fairly standard list:
One-off setup
- Create a non-root user, set up SSH keys and disable password login.
- Configure a firewall (for example
ufw allow OpenSSH,ufw allow 'Nginx Full',ufw enable). - Install Node.js from a maintained source and pick an LTS version.
- Install a process manager (systemd service or PM2) so the app restarts on crashes and reboots.
- Install and configure Nginx as a reverse proxy.
- Install Certbot and issue Let's Encrypt certificates, and confirm auto-renewal works.
- Set up a deploy method: a Git hook, a CI job that SSHes in, or a script.
- Install and secure a database, or connect to a managed one.
- Set up backups for files and database, stored off the server.
- Set up log rotation and some form of monitoring or uptime alerting.
If you have done it before, it goes quickly. The first time, expect to spend real time reading documentation and fixing mistakes.
Ongoing maintenance
This is the part people underestimate:
- Operating system security updates, including the occasional one that needs a reboot. Unattended upgrades help, but someone still needs to check they run.
- Node.js upgrades. Each LTS line has an end-of-life date (Node.js 20 has already reached it). Moving to the next LTS means testing your app and upgrading the server. The schedule is on nodejs.org.
- Dependency and package updates for Nginx, OpenSSL, the database server and anything else installed.
- Disk space. Logs, old releases and database growth fill disks; a full disk takes the app down.
- Certificate renewal failures, which usually happen when a config change breaks the renewal challenge.
- Incidents. When the app stops responding, you investigate: process crashed, out of memory, disk full, DNS, firewall, upstream API.
- Restores. Backups are only useful if you have tested restoring them.
Security is ongoing, not a one-off
A public server is scanned constantly by automated bots looking for weak SSH passwords, outdated software and exposed admin panels. The risk on a VPS is not that Linux is insecure; it is that security depends on someone keeping up. A server that was well configured two years ago and not touched since is a liability.
What managed hosting takes off your plate
With managed Node.js hosting, the provider handles the server, operating system, runtime, process supervision, routing, SSL and platform security. Your job shrinks to:
- your code and its dependencies (
npm audit, updates) - your environment variables and secrets
- your app's own security (auth, validation, rate limits)
- choosing the right plan size
On NewHost, for example, you connect a GitHub or GitLab repository, set install, build and start commands, and each push deploys. SSL is free Let's Encrypt, backups are automatic (weekly or daily depending on plan) and restores are done by the support team.
Side-by-side comparison
| VPS | Managed app hosting | |
|---|---|---|
| Control | Full root access | App-level only |
| Setup time | Hours to days | Minutes |
| OS and runtime patching | You | Provider |
| Process restarts | You configure | Built in |
| SSL | You set up and monitor | Automatic |
| Deploys | You build the pipeline | Git push |
| Backups | You design and test | Included per plan |
| Non-HTTP services, custom daemons | Yes | Usually not |
| Docker, custom system packages | Yes | Usually not |
| Predictable monthly cost | Yes, plus your time | Yes |
Putting a number on your time
The honest way to compare is to add your hours to the VPS price. Use your own figures:
VPS true monthly cost =
VPS price
+ (setup hours / months you'll keep it) x your hourly rate
+ monthly maintenance hours x your hourly rate
+ expected incident hours per month x your hourly rate
As an illustration only: if your time is worth R500 an hour, and you spend two hours a month on updates, checks and small fixes, that is R1,000 a month of your time before any incident. For an agency, the same calculation applies per server, and it grows with every client site you run yourself.
If you enjoy server work, or you have a DevOps colleague whose job includes it, that time may be well spent. If you are a developer or a small business who would rather ship features, it usually is not.
When a VPS is the right choice
A VPS is genuinely the better option when you need:
- Custom system software, such as specific binaries, headless browsers with unusual dependencies, or a self-hosted service stack.
- Non-HTTP protocols or ports, for example raw TCP or UDP services.
- Docker Compose setups with several containers you want to run together.
- Full control for compliance or architectural reasons.
- Learning. Running your own server is an excellent way to understand how the web works.
When managed hosting is the right choice
Managed hosting usually wins when:
- your app is a standard web app or API (Next.js, Nuxt, Express, Fastify, NestJS)
- you want push-to-deploy and preview URLs without building a pipeline
- nobody on the team wants to be on call for the server
- you run many small apps, where per-server maintenance adds up fast
- you want predictable costs in rand for yourself or your clients
A middle path
You do not have to choose one for everything. Many teams run their web apps and APIs on managed hosting and keep a small VPS for the one component that needs custom software. Just keep the database and app close together, ideally in the same South African location.
Frequently asked questions
Is a VPS cheaper than managed Node.js hosting?
On the invoice, sometimes. Once you add the hours spent on setup, updates, backups and incidents, managed hosting is often cheaper for small teams. Work it out with your own hourly rate.
Is a VPS more secure than managed hosting?
Neither is automatically more secure. A VPS is as secure as its maintenance. Managed hosting shifts server patching to the provider, so your effort goes into your application's security.
Can I move from a VPS to managed hosting later?
Yes. If your app reads its port and settings from environment variables and starts with npm start, moving is mostly a matter of connecting the repository, copying environment variables and switching DNS.
Do I need Docker for managed hosting?
No. Managed hosting builds and runs your app from its package.json scripts. Docker is a VPS-style tool you only need if the platform requires it or you choose it.
For the production basics that apply on either route, read how to host a Node.js app and Node.js hosting in South Africa. If you would rather not maintain a server, NewHost Node.js hosting starts at R99 a month, and the pricing page compares every plan.