Node.js hosting with the room to run real apps

Yes, the choice is completely yours. Because every plan is a full-root KVM VPS, you are not tied to whatever version a shared host happens to offer. Most people install nvm and pull down the exact release their app needs — the current LTS line for production stability, or a specific version their build was tested against — and switch between versions per project on the same server. If you prefer, you can install the official Node binaries or your distro's packages instead. You can also keep several versions side by side and pin each app to its own with an .nvmrc file, which is handy when you host more than one project. When a new LTS lands, you upgrade on your own schedule rather than waiting on us. Nothing about the runtime is locked down: you decide the version, the npm or pnpm or yarn package manager, and when to update.

Both work well because you hold root. For a plain Node process, PM2 is the common choice: it keeps your app running, restarts it if it crashes, can fork several instances to use every CPU core, and rotates logs for you. A single `pm2 start` plus `pm2 startup` and `pm2 save` is usually all it takes to have the app survive a reboot. If you would rather containerise, install Docker and run your image directly, or bring up a small stack with a docker-compose file — an app container alongside Postgres and Redis, for example. Some people combine the two, running Docker for dependencies and PM2 for the app, or the reverse. Since the server is yours, you can also use systemd units if that suits your workflow better. We keep the underlying VPS, network and DDoS protection healthy; how you supervise your processes is entirely your call.

These are self-managed VPS plans, and that is deliberate — keeping the server unmanaged is exactly what makes root access, custom Node versions and your own process setup possible at this price. You own everything above the operating system: the Node runtime, PM2 or Docker, your reverse proxy, databases and deploys are yours to configure however your app needs. What we manage is the foundation beneath it — the physical hardware, the KVM virtualisation, the tier-3 datacentre network and DDoS protection — so you never worry about the parts you cannot see. Our support team is available 24/7 for infrastructure, provisioning and network questions, and can help you resize a plan or troubleshoot connectivity. If you would rather not administer the server yourself, managed options are available on request, and many teams bring in a developer for the application layer while we keep the VPS fast, online and protected.

Yes. With full root you can install Postgres, MongoDB or Redis directly on the VPS and have your Node app talk to them over localhost, which keeps latency low and avoids an extra network hop. Redis is a popular companion for sessions, caching and job queues, while Postgres or MongoDB holds your primary data — run one, or all three, sized to the RAM your tier provides. In front of the app it is standard to put Nginx as a reverse proxy: it terminates TLS with a free auto-renewing SSL certificate, serves the public 443 endpoint, load-balances across your PM2 or Docker instances, and can cache static assets. That is the classic production layout — Nginx on the edge, Node behind it, databases alongside. If you would rather keep data on a separate managed database, you can simply connect out to it instead; nothing forces the database onto the same box.

A bare `node server.js` stops the moment the terminal closes or the process crashes, so on a real server you run it under a process manager. PM2 is the usual answer: it daemonises the app, restarts it automatically after a crash, and with `pm2 startup` plus `pm2 save` brings everything back after a reboot. Its cluster mode can fork one worker per CPU core so a single app uses all the resources your tier gives it, and built-in log handling makes issues easier to trace. If you containerise instead, Docker's restart policies do the same job, and systemd is a solid native option when you prefer it. On top of that, guaranteed KVM resources and NVMe storage mean the app is not fighting noisy neighbours for CPU, and network-level DDoS protection keeps it reachable under attack. Between a process manager and dedicated resources, the same uptime you see in testing is what your users get.

Yes. After you sign up, open a ticket and our team helps you get set up — provisioning the server, confirming SSH and your dedicated IPv4, and pointing you in the right direction on the OS and firewall. For the app itself, a typical deploy is to clone your Git repository onto the server, install dependencies, set your environment variables, build if needed, and start the process under PM2 or Docker — and we are happy to advise on that flow. If you are moving from another host, we can help you bring across your code, environment configuration and any local database so the app runs the same on the new VPS. You can stage it and test on the dedicated IP before you switch DNS, so the cutover is smooth. Managed assistance for the application layer is available on request if you would like a heavier hand; otherwise our 24/7 team stays on the infrastructure and network side.