VM1
Sold out
$ 13,455/ mo
- 1 vCPU
- 1 GB RAM
- 15 GB SSD
- 1 static public IP
- Unmetered transfer (fair use)
- Windows or Linux
- Physical location: Argentina
Node.js VPS
Node.js VPS: your application running as a service
A Linux VPS with root where you pick the Node version, put the application under a process manager that brings it back on its own, and publish it on your domain with a certificate. No platform layers between your code and the server.
The short answer
A Node.js application needs three things to be in production: the Node version the project expects, something that brings it back if it crashes or the server reboots, and a server in front answering on 443 with a certificate. On a VPS that is three commands —nvm, pm2 and Caddy— and it all stays under your control, with no limits on processes or concurrent connections. At SISArgentina the VPS ships with Ubuntu 24.04 LTS, root SSH access and a static Argentine IP from our Buenos Aires datacenter. We suggest the VM2 for one application and its database; the VM3 or VM4 if you build on the server. Installing and running it is on you.
- Node.js 24 LTS
- nvm
- pm2
- Caddy
- HTTPS
- Express
- Next.js
- NestJS
- PostgreSQL
- Redis
- Git
What you get
The version your project asks for
With nvm several versions live on the same server and each application uses its own. One that cannot jump to the latest yet does not hold the others back.
If it falls over, it comes back
pm2 watches the process, restarts it when it exits badly and brings it back after a server reboot. It also keeps the logs and shows memory and CPU per application.
No process or connection caps
The plan’s resources are yours: you can run several applications, workers, scheduled jobs and a database on the same server, without paying per instance.
Next to the database and the site
The database runs on the same VPS or on another of ours, and the application reaches it over the internal network. Less travelling than crossing the internet for every query.
A static Argentine IP
One address for the allowlists of the APIs you talk to, and low latency for users who are here.
Node.js VPS plans
These are the usual Cloud VPS plans, and the cart opens with the system already selected. Monthly prices, final price. USD amounts are the official store list; local invoicing is issued in pesos.
Most chosen
VM2
$ 26,910/ mo
- 2 vCPU
- 2 GB RAM
- 30 GB storage
- 1 static public IP
- Unmetered transfer (fair use)
- Windows or Linux
- Physical location: Argentina
VM3
$ 40,365/ mo
- 3 vCPU
- 3 GB RAM
- 45 GB storage
- 1 static public IP
- Unmetered transfer (fair use)
- Windows or Linux
- Physical location: Argentina
VM4
$ 53,820/ mo
- 4 vCPU
- 4 GB RAM
- 60 GB storage
- 1 static public IP
- Unmetered transfer (fair use)
- Windows or Linux
- Physical location: Argentina
Your app in production in three steps
-
Install Node.js
Log in as root with the IP and password you receive by email and install nvm, which is what nodejs.org recommends for Linux. With --lts you get the long-term support version, today the 24.
apt update && apt upgrade -y && apt install -y curl git curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.40.7/install.sh | bash . ~/.nvm/nvm.sh && nvm install --lts && node -v -
Put the application under pm2
Clone your repository, install the dependencies and start the application with pm2. pm2 save freezes the process list and pm2 startup installs the service that brings it back when the server reboots: that last command prints one more line, which you run exactly as printed.
npm install pm2@latest -g git clone https://github.com/tu-usuario/tu-app.git /opt/tu-app && cd /opt/tu-app npm ci --omit=dev && pm2 start app.js --name tu-app && pm2 save && pm2 startup -
Publish it on your domain over HTTPS
Point an A record for the domain at the VPS IP and install Caddy from its official repository. The two-line Caddyfile sends traffic to your application, and Caddy requests and renews the certificate on its own.
apt install -y debian-keyring debian-archive-keyring apt-transport-https curl curl -1sLf 'https://dl.cloudsmith.io/public/caddy/stable/gpg.key' | gpg --dearmor -o /usr/share/keyrings/caddy-stable-archive-keyring.gpg curl -1sLf 'https://dl.cloudsmith.io/public/caddy/stable/debian.deb.txt' > /etc/apt/sources.list.d/caddy-stable.list apt update && apt install -y caddy printf 'app.tudominio.com.ar {\n reverse_proxy 127.0.0.1:3000\n}\n' > /etc/caddy/Caddyfile && systemctl reload caddy
Read on: Primeros pasos al recibir un VPS: la checklist de seguridad · Cuánta RAM necesita tu VPS
Frequently asked questions
Why not use the Node.js Ubuntu ships?
Because the Ubuntu 24.04 package stays on an older version and does not move for the whole life of the distribution. With nvm you choose the version, change it when your project asks for it, and can keep two applications on different versions on the same server.
pm2 or a systemd service?
Both work. pm2 is quicker to set up and brings logs, per-process metrics, zero-downtime reload and a cluster mode to use every core. systemd is one dependency less and fits better if you already run the server with your own units. With no strong preference, start with pm2.
Which plan do I need?
The VM2 (2 vCPU, 2 GB, 30 GB) is enough for one application and its database under normal traffic. If you build on the server —a Next.js build, say— the VM3 or VM4 pays off, because that is the part that asks for the most memory. Moving up a plan needs no migration or reinstall.
Can I run several applications on one VPS?
Yes. Each one listens on a different 127.0.0.1 port, pm2 watches them all, and the Caddyfile gets one block per domain. The limit is the plan’s memory, not anyone’s licence.
How do I deploy a new version?
The usual routine is git pull, npm ci --omit=dev and pm2 reload your-app, which reloads without dropping in-flight connections. If your repository triggers the deploy, the VPS has a fixed IP: you can allow the webhook against that address and keep everything else closed.
Is the server managed?
No. VPS plans and cloud servers are delivered unmanaged: we provide the server with a clean operating system, the static IP and root access, and from there on installing, configuring, updating, securing and backing it up are yours. The commands on this page are the ones in the tool’s official documentation, verified on Ubuntu 24.04, and they are enough to get it running; support for the tool itself is its own documentation and community. If you get stuck with something on the server, write to us and we will lend a hand. And if you would rather not deal with it, our software factory builds custom work on this same infrastructure. Shared hosting with a control panel is a different story: that one we do install and maintain.