Versions and processes
The image ships the LTS line because that is what most production apps target. Anything newer is a version manager away, and pm2 will run several apps on one server without them fighting over a port.
What it saves you
No process babysitting
The thing that kills a hobby deployment is a crash at 3am with nothing to restart it.
TLS you did not configure
nginx and the certificate are in place; your app can listen on plain HTTP behind them.
Room for the build
Front-end builds are memory-hungry. Snapshot first, build, and roll back if a dependency breaks.
An API fits on the entry tier
A Node API with a database beside it runs happily on the smallest plan. The moment the same machine also builds your front end, the next tier up stops the build competing with the app.
From order to a working Node.js
Pick Node.js as the image
In the configurator, next to the plan and the region.
Push your code
Clone it, npm install, and tell pm2 the entry point.
Point a hostname
nginx routes it and the certificate is issued.
Save the process list
`pm2 save` so the app survives a reboot.
Straight answers before you deploy
Yes. pm2 runs each on its own port and nginx routes by hostname, so one server can carry several small services.
Not in the image. Both install cleanly on top of it if that is what your project uses.
Ready when you are.
Configure a server now. Your account is created right before payment, with the configuration saved.