8 Best Node.js Hosting Platforms in 2026
Which Node.js hosting should you pick when one host bills by the request, another by the second and a third by the server? And is the best Node.js hosting still Vercel or Render once your app has steady traffic?
The trouble is that these hosts don’t sell the same thing. Some run your app as a process that stays on. Others start it when a request arrives and stop it afterwards, and the bill follows that design.
So I compared 8 Node.js hosting platforms on their current plans and documentation, and sorted them by the job each one does best. My short answer:
- Cloudways Velocity for several always-on apps on one flat bill
- Vercel for Next.js front-ends and teams that work on preview URLs
- Render for 1 or 2 always-on services with the least setup
- Railway for prototypes and small projects billed by usage
- DigitalOcean App Platform for Docker apps that need autoscaling
- Fly.io for apps that must run close to users in several regions
- Hostinger for the lowest price on a small app
- xCloud for running Node.js on your own VPS
I haven’t run production apps on all 8. I host this site on a Hetzner VPS managed through xCloud, and I’ve hosted WordPress on Cloudways, so I know those 2 platforms from the inside. The rest I’ve judged on what each company publishes.
I’d pick the billing model before the brand. Usage pricing suits a quiet app, and a flat server price suits a busy one.
Quick Comparisons

The second column names the job, so you can jump straight to the host that fits yours. The “Stays on” column matters more than it looks, because it decides whether WebSockets, cron jobs and background work run without workarounds.
| Host | Best for | How you pay | Stays on | Entry price |
|---|---|---|---|---|
| Cloudways Velocity | Several always-on apps on one bill | Flat price per server | Yes | $20 a month for up to 5 apps |
| Vercel | Next.js and front-end teams | Per seat, plus usage | No, it runs per request | Free for personal use, then $20 a seat |
| Render | 1 or 2 always-on services | Per service | Yes, on paid plans | $7 a month for 512 MB |
| Railway | Prototypes and small projects | Usage, by the second | Yes, with optional sleep | $5 a month, with $5 of usage included |
| DigitalOcean App Platform | Docker apps and autoscaling | Per container | Yes | $5 a month for 512 MiB |
| Fly.io | Apps in several regions | Usage, by the second | Your choice | About $13 a month for 2 GB kept on |
| Hostinger | Lowest cost for a small app | Flat plan with a long prepay | No, it stops when idle | Under $3 a month on a 48-month term |
| xCloud | Your own VPS | VPS bill, plus the panel | Yes | Free for 1 server, plus the VPS |
These are each company’s list prices in USD. Promotions change often, so I’d check the order page before paying.
What Changes Between Node.js Hosts
Before the picks, I want to ensure 5 terms are clear, because every pricing page on this list uses them differently.
- Always-on: the app runs as a process that never stops, so WebSocket connections, cron jobs and background work behave normally.
- Scale to zero: the host stops the app when it’s idle and starts it on the next request. It is cheaper for a quiet app, and the first visitor waits for the cold start.
- Serverless functions: your code runs once per request with a time limit, and you pay for requests and CPU time.
- Autoscaling: the host adds copies of your app under load and removes them afterwards.
- Usage-based billing: you pay for the CPU, memory and data transfer the app uses, so the invoice moves with traffic.
Best Node.js Hosting Platforms
Each entry opens with the job that host does best and ends with who should look at a different one.
Cloudways Velocity
Cloudways Velocity is my pick when you run several always-on Node apps and want one fixed bill. It is a managed server from Cloudways, the host owned by DigitalOcean, and its $20 Starter plan runs up to 5 apps on 2 vCPU and 2 GB of RAM.
Cloudways Velocity
- Up to 5 apps on the $20 plan
- Apps stay on, with WebSockets and cron
- Cloudflare Enterprise CDN and firewall included
- No autoscaling and no SSH
Cloudways patches the server, issues SSL and runs backups. You deploy from GitHub, GitLab or Bitbucket, with presets for Next.js, Nuxt, Astro, Express and n8n. Every app gets its own domain, logs and process, and all of them share the server’s CPU and memory.
The math is what sets it apart. On Render, 5 small always-on services cost $35 to $125 a month depending on their size. Here they cost $20 until the server runs out of memory.
Velocity doesn’t autoscale, gives you no SSH and runs Node.js only. For traffic that spikes hard, I’d look at Render or DigitalOcean App Platform. My Cloudways Velocity review has the full plan table and the limits.
Vercel
Vercel is the best Node.js hosting for a Next.js app, which makes sense because Vercel builds Next.js. Your code runs as functions that start per request and scale by themselves, and every push gets its own preview URL on every plan.
Vercel
- Preview deployment for every push
- Scales automatically with traffic
- Free Hobby plan for personal projects
- Functions stop at 300 or 800 seconds
The Hobby plan is free and limited to personal, non-commercial use. Pro costs $20 a month per developer seat and includes $20 of usage. Anything above that is billed by requests, CPU time and data transfer.
These are the limits I’d check before putting a backend on it:
- A function stops after 300 seconds on Hobby and 800 seconds on Pro, and an open WebSocket closes with it.
- A request or response body can’t be larger than 4.5 MB.
- There is no persistent disk, and databases come from marketplace partners such as Neon and Supabase.
- A spend limit doesn’t pause your project unless you turn that option on.
I’d use Vercel for the front-end and keep a long-running API, a queue worker or a WebSocket server on a host that stays on, such as Render or Velocity.
Render
Render is the simplest way to put 1 or 2 always-on Node services online. You connect a repository, Render builds it and the service stays up on any paid instance, with zero-downtime deploys by default.
Render
- Always-on services from $7 a month
- Managed Postgres from $6 a month
- SSH and a web shell on paid services
- Free services sleep after 15 minutes
Pricing is per service. Starter is $7 a month for 512 MB, and Standard is $25 for 1 CPU and 2 GB. Background workers and cron jobs are separate services with their own price.
This is what a paid service comes with:
- Git deploys from GitHub, GitLab and Bitbucket, or from a Dockerfile
- Rollbacks to earlier builds, and full preview environments on the Pro workspace
- Autoscaling on the Pro workspace, which costs a flat $25 a month for the whole team
- 5 regions across the US, Frankfurt and Singapore
2 catches are easy to miss. The free tier spins a service down after 15 minutes without traffic and takes about a minute to wake, so it is for testing only. And the Hobby workspace includes just 5 GB of bandwidth a month, with extra data at $0.15 per GB.
Once you have 4 or 5 services, the per-service bill adds up. That is the point where I’d compare Render with Velocity or your own VPS.
Railway
Railway is my pick for a prototype, a side project or a small app with uneven use. It bills by the second for the memory and CPU your app actually uses, so a quiet app costs very little.
Railway
- $5 Hobby plan includes $5 of usage
- Postgres, MySQL, Redis and MongoDB templates
- An environment for each pull request
- No published uptime SLA
The Hobby plan is $5 a month and includes $5 of usage. Beyond that, memory costs $10 per GB a month and CPU costs $20 per vCPU, both prorated by the second. Outbound data is $0.05 per GB.
Here’s a worked example with made-up usage. An app that holds 512 MB of memory all month and uses a quarter of a vCPU costs about $10: $5 for the memory and $5 for the CPU.
Railway also adds a database from a template in one click, gives each pull request its own environment and lets a service sleep when idle. The first request to a sleeping service can fail with a 502 error while it wakes, so I’d leave sleep off for anything customer-facing.
It runs in 4 regions, publishes no uptime SLA and leaves database backups for you to switch on. For a production app with steady load, a fixed-price host is easier to budget.
DigitalOcean App Platform
DigitalOcean App Platform is the one I’d pick for a Docker-based app that needs to scale out. It runs your app as containers built from a Dockerfile or from buildpacks, in 12 regions.
DigitalOcean App Platform
- Containers from $5 a month
- Autoscaling on dedicated CPU plans
- Managed Postgres, MySQL, MongoDB and Valkey
- No persistent volumes
A shared container costs $5 a month for 512 MiB and $25 for 2 GiB, and each one includes a data transfer allowance. Autoscaling by CPU needs the dedicated plans, which start at $29.
The real reason to choose it is the rest of DigitalOcean. Managed databases, object storage and private networking sit in the same account, and you can roll back to any of the last 10 deployments.
The limits are specific:
- There are no persistent volumes, and the local disk is wiped on every deploy.
- A scheduled job can run at most once every 15 minutes.
- Node clustering isn’t officially supported.
- A managed database starts at about $15 a month, on top of the app.
For a single small app, Render is simpler. App Platform earns its place when you already use DigitalOcean or plan to grow into it.
Fly.io
Fly.io is the best fit when the same app has to run close to users in several parts of the world. It runs your app as small virtual machines in 17 regions and routes each visitor to the nearest one.
Fly.io
- 17 regions to place machines in
- Machines can stop when idle
- SSH into any running machine
- No free tier, and more setup
Machines are billed by the second. A shared 2 GB machine kept on all month costs about $13, and a stopped machine costs only its storage. By default a new app scales to zero, with a cold start of about 2 seconds, and you can turn that off.
Fly gives you more control than the other platforms here, and it expects more from you. You deploy from the command line or a Dockerfile, and preview apps, cron jobs and metric-based autoscaling are things you assemble from its guides.
Storage needs care too. A volume lives on one server in one region with no replication, and managed Postgres starts at $38 a month. I’d choose Fly when latency across regions matters to your app, and Render when it doesn’t.
Hostinger
Hostinger is the cheapest way to host a small Node.js app if you’re willing to prepay. Its Unlimited web hosting plan runs up to 5 Node.js apps beside your regular websites, with GitHub deploys and free SSL.
Hostinger
- Up to 5 Node.js apps on one plan
- GitHub and GitLab deploys
- Managed MySQL included
- No WebSockets or background workers
The low price needs a 48-month term, which brings the plan under $3 a month before it renews at about $17. Paid month to month, the same plan is about $19.
It supports Express, Fastify, NestJS, Next.js, Nuxt, Astro and SvelteKit on Node.js 18 to 24.
It is closer to shared hosting than to a server, and the limits show it:
- Inbound WebSockets aren’t supported.
- Background workers can’t run all the time.
- A request is cut off after 120 seconds.
- Hostinger’s docs say an app’s process stops after a period without traffic.
For a brochure site, a small API or a Next.js blog, that is fine. For a real-time app, I’d move to Hostinger’s VPS plans or to Velocity.
xCloud
xCloud is my pick when you want your own VPS without doing the server work by hand. It is a control panel that connects to a server at Hetzner, Vultr, DigitalOcean or another provider and deploys Node.js apps to it.
xCloud
- Free plan for 1 server
- Git push-to-deploy with PM2
- Free SSL and managed databases
- You pay the VPS provider separately
I manage this WordPress site’s Hetzner VPS through xCloud, so I know the panel well. On the Node.js side, you pick a server, connect a GitHub repository and xCloud sets up the app.
This is what it handles:
- Push-to-deploy from GitHub, with zero-downtime releases and one-click rollback on NGINX servers
- PM2 process management, which restarts a crashed app
- Environment variables, free SSL and PostgreSQL or MySQL
- A choice of Node.js version for each server
The free plan covers 1 server you bring yourself, without backups, monitoring or team members. Paid plans cost $5 per server a month for 2 to 5 servers, and the VPS bill is separate. A DigitalOcean Droplet with 2 vCPU and 2 GB is $18 a month.
You still own the server, so a full disk or a kernel update is yours to fix. If you’d rather not pay for a panel, Coolify is a free self-hosted alternative that also handles Git deploys and SSL. My Hetzner vs Vultr vs RackNerd comparison covers the hardware side.
How to Choose Node.js Hosting
3 questions settle most of the choice, and I’d answer them in this order.
Does the App Need to Stay On?
If it holds WebSocket connections, runs scheduled jobs or processes a queue, yes. That rules out pure serverless hosting and Hostinger’s web app plans. It points to Velocity, Render, Railway, App Platform, Fly.io or a VPS.
How Many Apps Will You Run?
For 1 or 2 apps, per-service pricing on Render or Railway is cheapest. From about 3 always-on apps, a flat server price on Velocity or your own VPS costs less, because the apps share one machine.
Who Will Look After the Server?
If nobody on the team wants to patch a server, I’d stay on a managed platform. A VPS with xCloud or Coolify gives you the most hardware for the money, and my guide to shared, VPS and dedicated hosting explains what you take on with it.
Hosts I Left Out
A few well-known names aren’t in the list, and each has a reason.
- Heroku: it moved to a sustaining engineering model in 2026, has no free tier and charges $7 a month for a 512 MB dyno.
- Netlify: its functions run per request with a 60-second limit. A long-lived Node server product is in early access, and it stops when idle.
- Cloudflare Workers: it is a different runtime with partial Node.js compatibility, so an Express app can’t simply listen on a port there.
- AWS, Google Cloud and Azure: they can run anything, and they need the most setup and cost monitoring of any option here.
FAQs on Node.js Hosting
What is the best Node.js hosting?
It depends on how the app runs. Vercel is the best fit for Next.js, Render for 1 or 2 always-on services and Cloudways Velocity for several apps on one flat bill. For full control at the lowest hardware cost, I’d use my own VPS with xCloud.
Is there free Node.js hosting?
Yes, with limits. Vercel’s Hobby plan is free for personal, non-commercial projects, and Render’s free web services sleep after 15 minutes without traffic. Railway gives a one-time $5 trial credit, and Fly.io has no free tier for new accounts.
Can I host Node.js on shared hosting?
Most shared hosting can’t run a Node.js process. Hostinger’s Unlimited and Cloud plans can, with limits: no inbound WebSockets, no always-running background workers and a 120-second request limit.
Do I need a VPS for Node.js?
No. Managed platforms such as Render, Railway and Cloudways Velocity run Node.js without a server to maintain. A VPS makes sense when you want root access or the most hardware for the money, and a panel such as xCloud or Coolify handles the deploys.
Which Node.js version should I deploy?
I’d use the newest LTS release that your host supports. Even-numbered Node.js versions become LTS each October, and some hosts add them late, so check the supported versions before you choose.
Final Remarks
If you’re still unsure, I’d start from how your app runs and how many apps you have. One Next.js site goes to Vercel, 1 always-on service goes to Render and a prototype goes to Railway.
Once you’re running 3 or more always-on apps, I’d move them to one server, either managed on Cloudways Velocity or on your own VPS with xCloud. Moving a Node app between these hosts takes an afternoon, so there’s no need to buy for a future you don’t have yet.
Best of luck.
Tell Google you want more of this.
Add Gaurav Tiwari as a preferred sourceOne tap, and this site shows up more often in your own Top Stories, AI Overviews and AI Mode. Remove it any time.
Disclaimer: This site is reader-supported. If you buy through some links, I may earn a small commission at no extra cost to you. I only recommend tools I trust and would use myself. Your support helps keep gauravtiwari.org free and focused on real-world advice. Thanks. - Gaurav Tiwari