Node.js on a VPS
Node.js on a box that answers to you
Apps, APIs and bots on a KVM VPS with the root account included. Choose the Node release, supervise it with PM2 or Docker, and get fixed CPU and RAM on NVMe disks. The price tag starts at $13.52/mo.
$9.99
what a Node VPS costs you here
Full root
deploy on your own terms
Any version
choose whichever Node build you fancy
NVMe
quick disks across the range
Why Buy Here
The bits that begin to matter the day you go live
The root password is yours
Install the Node build, the global CLIs, the compilers and whatever system packages the project asks for. Nothing on the box is fenced off.
CPU and RAM with your name on them
KVM gives the event loop a fixed slice of cores and memory, which is why a neighbour's traffic spike never shows up in your response times.
DDoS filtering at no extra charge
Junk traffic gets scrubbed off out on the network, well before the server sees it, so APIs, sockets and bots carry on answering when somebody turns nasty.
One IPv4 address, all yours
Each server arrives with an IPv4 of its own, which means a clean sending reputation, space for your certificates, and webhook endpoints that stay where they are.
Live inside a minute
Debian, CentOS or Ubuntu comes up in under sixty seconds. Clone the repository, start the process, and requests are being served.
NVMe disks throughout
NVMe is what every tier writes to, so package installs finish fast, builds keep moving, and database reads come straight back.
Whose Server It Is
Root access hands the runtime straight to you
Shared hosting leaves the provider choosing your Node version and half the configuration besides. Root on a VPS lifts that ceiling off. Pull the exact release your app was built against using nvm, add whichever global CLIs and build tools you lean on, and supervise the process with PM2 or with Docker, whichever you prefer. One machine, arranged the way you want it.
- The root account, no asterisks
- Install any Node.js release
- PM2 or Docker, your call
- SSH in and push your code
Price Tags
Node.js VPS plans, with the cost attached
First API or a busy real-time backend, the list below reads the same way: root access, NVMe storage and a dedicated IPv4 on every tier.
1 Core Unmanaged VPS
First step up the ladder: a server that is yours alone
$13.52/mo
the renewal price is the same
- vCPU cores
- 1
- RAM
- 1 GB DDR4
- SSD disk
- 25 GB
- Root access
- Full
- Root access, with nothing fenced off
- KVM virtualisation underneath
- 24 Linux and BSD builds on the shelf
- Pick your counter: London or Dallas
- 1 Tbps+ DDoS filtering sits in front
- 20 Gbps uplink on every hypervisor
- SSD disk space included in the price
- Add cPanel at the counter if you want it
- Snapshot backups, yours to switch on
- Extra SSD disks whenever you need them
- Reboot, rebuild and console from the panel
- No setup fee at all, so nothing leaves your pocket up front
- Real people answer, round the clock
Orders are rung up on Hosting Cheap, which is the billing platform behind our checkout.
2 Core Unmanaged VPS
Room on the shelf for a real workload
$20.28/mo
the renewal price is the same
- vCPU cores
- 2
- RAM
- 2 GB DDR4
- SSD disk
- 50 GB
- Root access
- Full
- Root access, with nothing fenced off
- KVM virtualisation underneath
- 24 Linux and BSD builds on the shelf
- Pick your counter: London or Dallas
- 1 Tbps+ DDoS filtering sits in front
- 20 Gbps uplink on every hypervisor
- SSD disk space included in the price
- Add cPanel at the counter if you want it
- Snapshot backups, yours to switch on
- Extra SSD disks whenever you need them
- Reboot, rebuild and console from the panel
- No setup fee at all, so nothing leaves your pocket up front
- Real people answer, round the clock
Orders are rung up on Hosting Cheap, which is the billing platform behind our checkout.
4 Core Unmanaged VPS
Stocked for busy apps and small fleets
$33.81/mo
the renewal price is the same
- vCPU cores
- 4
- RAM
- 4 GB DDR4
- SSD disk
- 75 GB
- Root access
- Full
- Root access, with nothing fenced off
- KVM virtualisation underneath
- 24 Linux and BSD builds on the shelf
- Pick your counter: London or Dallas
- 1 Tbps+ DDoS filtering sits in front
- 20 Gbps uplink on every hypervisor
- SSD disk space included in the price
- Add cPanel at the counter if you want it
- Snapshot backups, yours to switch on
- Extra SSD disks whenever you need them
- Reboot, rebuild and console from the panel
- No setup fee at all, so nothing leaves your pocket up front
- Real people answer, round the clock
Orders are rung up on Hosting Cheap, which is the billing platform behind our checkout.
6 Core Unmanaged VPS
For stacks that ask for more memory
$67.63/mo
the renewal price is the same
- vCPU cores
- 6
- RAM
- 8 GB DDR4
- SSD disk
- 100 GB
- Root access
- Full
- Root access, with nothing fenced off
- KVM virtualisation underneath
- 24 Linux and BSD builds on the shelf
- Pick your counter: London or Dallas
- 1 Tbps+ DDoS filtering sits in front
- 20 Gbps uplink on every hypervisor
- SSD disk space included in the price
- Add cPanel at the counter if you want it
- Snapshot backups, yours to switch on
- Extra SSD disks whenever you need them
- Reboot, rebuild and console from the panel
- No setup fee at all, so nothing leaves your pocket up front
- Real people answer, round the clock
Orders are rung up on Hosting Cheap, which is the billing platform behind our checkout.
8 Core Unmanaged VPS
Production weight, steady under load
$108.22/mo
the renewal price is the same
- vCPU cores
- 8
- RAM
- 16 GB DDR4
- SSD disk
- 200 GB
- Root access
- Full
- Root access, with nothing fenced off
- KVM virtualisation underneath
- 24 Linux and BSD builds on the shelf
- Pick your counter: London or Dallas
- 1 Tbps+ DDoS filtering sits in front
- 20 Gbps uplink on every hypervisor
- SSD disk space included in the price
- Add cPanel at the counter if you want it
- Snapshot backups, yours to switch on
- Extra SSD disks whenever you need them
- Reboot, rebuild and console from the panel
- No setup fee at all, so nothing leaves your pocket up front
- Real people answer, round the clock
Orders are rung up on Hosting Cheap, which is the billing platform behind our checkout.
10 Core Unmanaged VPS
The back room: serious, sustained demand
$270.57/mo
the renewal price is the same
- vCPU cores
- 10
- RAM
- 32 GB DDR4
- SSD disk
- 400 GB
- Root access
- Full
- Root access, with nothing fenced off
- KVM virtualisation underneath
- 24 Linux and BSD builds on the shelf
- Pick your counter: London or Dallas
- 1 Tbps+ DDoS filtering sits in front
- 20 Gbps uplink on every hypervisor
- SSD disk space included in the price
- Add cPanel at the counter if you want it
- Snapshot backups, yours to switch on
- Extra SSD disks whenever you need them
- Reboot, rebuild and console from the panel
- No setup fee at all, so nothing leaves your pocket up front
- Real people answer, round the clock
Orders are rung up on Hosting Cheap, which is the billing platform behind our checkout.
Throughput
The event loop stays level on KVM and NVMe
Node stays quick right up until the CPU runs short. What KVM allocates is real cores and real memory, not a slice that other tenants are tugging at, and that is what keeps the event loop answering under load. Put NVMe disks underneath for fast installs and database reads, and the numbers you measured during testing turn out to be the numbers your users actually get.
- Cores and memory that are guaranteed
- NVMe disks on every tier
- A 1 Gbps network uplink
- Nothing oversold behind the scenes
Common Orders
What people actually run on these boxes
Backends and APIs
Express, Fastify, NestJS, a GraphQL layer, and headroom left for whatever traffic an actual launch throws at it.
Sockets, chat and bots
WebSocket servers, chat backends, Discord or Telegram bots: all of them keep their connections open overnight.
Containers and microservices
Ship one image, bring up a small compose stack, or sit several services side by side on a single root box.
Staying Online
An IP of your own, and DDoS filtering at the door
An API is worth exactly what its uptime is worth. DDoS filtering at network level keeps endpoints answering while hostile traffic pours in at the door, and a dedicated IPv4 gives webhooks and outbound calls a stable reputation that nobody else is sharing. One tenant lives on the server, and that tenant is you, which also means SSH hardening, the firewall and TLS are yours to set up however you see fit from the start.
- Attack traffic scrubbed on the network
- An IPv4 address nobody else uses
- One tenant on the machine: you
- Free SSL, managed by you
Growing Into It
From the first deploy to steady traffic
Begin on whichever tier suits this month, and step up when the app has earned it. Upgrading leaves your code, your databases and your process setup untouched; the resources underneath are the only thing that shifts. As traffic climbs, more CPU, RAM, storage and bandwidth sit a couple of clicks away, with no reinstall to sit through and no migration to schedule.
- Move up a tier in a few clicks
- Storage from 30 GB to 250 GB
- Bandwidth from 125 GB to 1 TB
- Your data stays exactly where it is
How It Goes
Bare server to running app
- 1
Take a tier off the shelf
Size the machine against the traffic and memory you expect. Root access and NVMe disks arrive with every plan, whether large or small.
- 2
Install Node your way
Pull whichever release you need via nvm or the official binaries, then pass the process to PM2, or wrap the lot up inside Docker.
- 3
Go live, then grow into it
Stand Nginx in front for TLS and proxying, aim your domain at the IP, then step up a tier once the numbers tell you to.
In The Box
Standard on every Node.js VPS here
- The root account on your own VPS
- CPU and memory guaranteed by KVM
- NVMe disks from the smallest tier up
- An IPv4 address reserved for you
- Whichever Node.js release you install
- PM2 and Docker both supported
- Room for an Nginx reverse proxy
- SSH, Git and the usual build tools
- DDoS filtering on the network
- Support staffed through the night
The Whole Stack
What actually sits behind a running Node app
Each piece a production deployment leans on, all of it sitting on your own root-access VPS.
The runtime
nvm or the official tarballs will hand you whatever release you name. Production usually wants current LTS; a bundle already compiled wants the exact build it was made with.
A process manager or a container
PM2 holds the process up and revives it after a crash. Docker with a compose file does that same work inside a container. Having root makes either route simple to take.
Your database, near or far
Drop Postgres, MongoDB or Redis onto the same box and speak over localhost, or reach out to a managed instance elsewhere. Either is fine.
Nginx in front, TLS on top
End TLS on a free certificate that renews itself, proxy back through to Node, and answer on port 443 exactly as any production site does.
Enough memory to work with
Node keeps plenty in RAM. Budget on 2 GB for a modest API, and 4 GB or more once the app gets genuinely busy.
Somewhere to grow
Response times climbing and memory running tight is your signal to move up. Extra cores, RAM and disk sit a couple of clicks away.
FAQ
Straight answers on Node.js hosting
Which Node.js version will I be running?
Whichever one you install; that choice never leaves your hands. Every plan is a KVM VPS with the root account included, so no shared server gets to dictate the build you end up with. Most people go through nvm: install it, pull the release the project wants, and that is the job done. Perhaps that means the current LTS branch for production work, perhaps the specific version your build was tested against. Not an nvm habit? Grab the official Node binaries, or the packages your distribution ships. Several versions can sit on one box at the same time, and an .nvmrc file in each project pins it to the right one, which helps a great deal when a server carries more than one app. A new LTS lands, and you upgrade on your own timetable rather than ours. Version, package manager, whether npm, pnpm or yarn, and the update schedule are all yours to set.
Do PM2 and Docker both work here?
Both, and neither one needs any special arrangement, because root is yours. For a plain Node process, PM2 is the usual pick: it holds the app up, restarts it after a crash, forks a worker per CPU core when you want every core earning its keep, and rotates its own logs. Run pm2 start, then pm2 startup and pm2 save, and the app returns by itself after a reboot. Containers more your style? Install Docker and run your image, or bring a small stack up with docker-compose, the app in one container and Postgres and Redis sitting alongside it. Mixing the two happens often enough: Docker for the dependencies and PM2 for the app, or the other way about. Since the machine belongs to you, a plain systemd unit is every bit as valid if that is how you prefer to work. We look after the VPS, the network and the DDoS filtering; supervising processes is your call.
Are these servers managed or unmanaged?
Unmanaged. That is a decision, not an oversight. Hand somebody an unmanaged box and it becomes affordable to give them the root account, the Node version they prefer and a process setup of their own choosing, which is the trade at this price. Draw the line at the operating system: above it sits your runtime, PM2 or Docker, the reverse proxy, the databases and the deploy routine, arranged as the project wants. Below it we hold the hardware, the KVM layer, the London datacentre network and the DDoS defences, so nothing you cannot see lands on your plate. Round the clock, support handles infrastructure, provisioning and network questions, resizes a plan on request, or hunts down a route behaving badly. Not what you signed up for? Ask about managed cover. Many teams simply keep a developer of their own on the application side while the VPS stays quick, reachable and defended.
Can I run a database and a reverse proxy on that same box?
Yes, and that is what most people end up doing. Because root is yours, Postgres, MongoDB or Redis can go straight onto the VPS, which lets the Node app reach them over localhost: latency drops, and there is one fewer network hop in the way. Sessions, caching and job queues generally land on Redis; the core data sits in Postgres or MongoDB. One of them, all three, whatever the RAM on your tier will carry. Ahead of the app, Nginx is the usual reverse proxy. It ends TLS on a free self-renewing certificate, answers on port 443, spreads requests over your PM2 workers or Docker containers, and hands out static files without disturbing Node at all. Nginx outward, Node behind, databases within reach: an ordinary production deployment looks exactly like that. Prefer your data on a separate managed database? Dial out to it. Sharing the machine is not compulsory.
What holds the app up once I close my terminal window?
A process manager does. Nobody runs node server.js by hand in production, because that dies the instant the shell closes or the process throws. PM2 is the usual answer here. It daemonizes the app, brings it back after a crash, and paired with pm2 startup and pm2 save it restores everything following a reboot without you logging in at all. Cluster mode forks a worker per core, so one app can use the whole tier, and the built-in logs make an incident far easier to unpick afterwards. Containers instead? Docker restart policies cover the same ground, and a systemd unit is a perfectly good native alternative. Around all that, guaranteed KVM cores and NVMe disks mean your app is never elbowing a stranger for CPU, and DDoS filtering at network level keeps it reachable while an attack is running. Process manager plus dedicated resources, and the uptime you measured in testing is the uptime your users see.
Will somebody help me deploy, or carry an existing app over?
Yes. With the order through, raise a ticket and the team gets you moving: server provisioned, SSH and your dedicated IPv4 confirmed as working, plus a sensible steer on the operating system and the firewall. On the application side a normal deploy goes like this. Clone the Git repository onto the server, install dependencies, set the environment variables, build if the project wants building, then start it under PM2 or Docker. We are glad to walk through each of those with you. Coming from another host? We can help carry the code, the environment settings and a local database over, so the app behaves on the new VPS as it did on the old one. Stage and test on the dedicated IP first, move DNS afterwards, and the switch stays clean. Wanting a heavier hand on the application layer? Ask about managed cover. Otherwise the 24/7 team keeps its attention on infrastructure and network.
More hosting worth a look
The whole application catalogue
One-click installs by the shelf-load in the panel, covering CMSes, forums and shop software.
VPS Hosting
Those same root-access KVM servers sit under every Node plan: choose a distro, then build it out yourself.
Business Hosting
Managed accounts carrying SSH, Node.js and Python, for when running a server isn't your job at all.
PHP Hosting
Root-access servers aimed at PHP work, with release and extensions left to your judgement.
Laravel Hosting
Composer, queues and the entire Artisan toolchain, running on a server whose keys you hold.
Get your Node.js app onto the counter today.
Root access, the Node release of your choosing, PM2 or Docker on NVMe disks — and people to ask whenever something needs a second pair of eyes.
Browse Node.js PlansNode deserves better than a laptop and a hope. Give it a process that stays up, a port that is proxied properly and a console you can deploy from. The hardware underneath belongs to Hosting Seller: NVMe drives, LiteSpeed out front, and a network desk staffed at every hour of the day.
We built it for JavaScript developers shipping apps and APIs, so the extras most hosts charge for are simply included: certificates, site transfers, daily copies and answers from people who run the servers.
Node apps without renting a whole server
Create a Node application from the panel, choose the version, set the entry point and let the process manager keep it alive and restart it if it falls over. npm and Git are at the SSH prompt, environment variables live in the panel, and the app is served behind LiteSpeed with the certificate already fitted.
The hardware does the heavy lifting: 100% NVMe storage, LiteSpeed serving over HTTP/2, and a 99.9% uptime SLA our monitoring desk answers for. Quick pages keep visitors and search engines equally content.
What running Node here costs
There is no second price waiting in year two. What the tag says is what the invoice says, this term and the next, and any introductory rate carries its renewal figure beside it. Every hosting plan carries a 30-day money-back guarantee, so trying us out costs you an afternoon at worst.
You do not need a platform seat at $50 a month to put an API online. Node runs on the business shared plans, and when the app wants root or more memory, a KVM VPS from $13.52 takes it.
How Node runs on the platform
Node processes run on NVMe-backed accounts in our London datacentre, restarted automatically if they exit and watched by monitoring that reaches an engineer before it reaches you.
Nobody here waits for a customer to report an outage. Monitoring watches the fleet minute by minute and wakes an engineer first, so you usually hear about the fix rather than the fault.
- Several Node versions, chosen per application
- Process manager with automatic restarts
- a 99.9% uptime target credited against the SLA
- Daily backups with self-service restores
Worth Knowing
What else you get in the box
Deploy the way you already do
Pull from Git, run npm install, restart the app — the same commands you use locally, over SSH.
A panel that makes sense
Everything you need day to day is two clicks away, and none of it is hidden behind a higher tier.
Move up without moving out
Bigger plans are one confirmation away, and you only pay the difference from the day you switch.
Nothing holding you here
Standard backups and standard panels mean you can leave whenever you like. Most people simply do not.
Quick from the first request
Your app sits on NVMe storage behind LiteSpeed caching — quick before you touch a single setting.
HTTPS on the house
Certificates are issued and renewed automatically on every domain, and never appear on an invoice.
Starting Out
From order to live in three steps
- 1
Choose your tier
Take a business tier, or a VPS if the app wants root.
- 2
Bring your domain
Point the domain; the certificate is fitted for you.
- 3
Open for business
Push the code, set the entry point and start the process.
On the Shelf
Also included, no extra charge
- Every hosting plan comes with 30 days to change your mind
- Node applications managed from the panel
- SSH, Git and npm at the command line
- LiteSpeed servers with HTTP/2 switched on
- DDoS filtering at the network edge
- WHOIS privacy free wherever the registry allows it
- 240+ applications on the one-click installer
- Account live within minutes of checkout
Still Asking
Other questions that keep coming up
Can I run a bot or a worker as well as a web app?
Yes. The process manager keeps a long-running script alive next to your web application, and cron covers anything scheduled. If the workload needs a lot of memory or its own queue service, that is the point where a VPS at $13.52 a month is the better buy.
Is there a wait after I order?
You will be logging into the panel within minutes. If your app lives somewhere else today, we copy it here first, test it, and only then move the DNS.
Is there a charge for certificates?
Free, fitted and self-renewing. The only reasons to buy a certificate here are a wildcard or a validated seal for procurement.
What if Node.js hosting is not the right fit?
There is a 30-day money-back guarantee on the plan. Ask inside the month and you get your money back: no exit interview, and nobody transferring you to a team whose job is talking you out of it.
Read next
Business Hosting
Shared plans with SSH, Node and Python on the shelf.
VPS Hosting
KVM cloud servers with root from $13.52/mo.
PHP Hosting
PHP 5.6–8.4, OPcache, a version per site.
Pulled from the Resource Library
Best Web Application Hosting
Hosting criteria when you run apps, not brochure sites.
How to Deploy with Git
Repeatable deploys when the code changes often.
What is an API?
Defining the interfaces your app actually lives on.