EN
Client area
Sign Up

Get started

What brings you here?

Hosting for Node.js® apps · KVM VPS · full root

Put your Node.js® app on a server of its own.

For developers shipping APIs, web apps, bots and background workers. We hand you a KVM VPS already set up with the Node.js® LTS line you choose, a process supervisor and HTTPS, and from there it's yours: full root, no per-request billing, no platform deciding what your app may do. Servers in India, the US or Germany.

See plans & pricing

Runs on our Standard KVM VPS · nodejs.org ↗

Plans & pricing

Longer terms cost less per month. The price shown is per month at the term you pick, with the amount billed underneath.

Every plan includes 1 IPv4 + 1 IPv6

L-1

For one small app or API

₹1,095/mosave 17%

billed ₹13,142 per year

  • 2 vCPU
  • 2 GB RAM
  • 20 GB NVMe SSD
  • 1 TB bandwidth
  • 1 IPv4 + 1 IPv6
  • Note: Full root · KVM · self-managed
Choose L-1

L-2

For an app and its database

₹1,643/mosave 17%

billed ₹19,717 per year

  • 2 vCPU
  • 4 GB RAM
  • 40 GB NVMe SSD
  • 2 TB bandwidth
  • 1 IPv4 + 1 IPv6
  • Note: Full root · KVM · self-managed
Choose L-2

L-4

For busy production apps

₹3,444/mosave 17%

billed ₹41,323 per year

  • 8 vCPU
  • 12 GB RAM
  • 140 GB NVMe SSD
  • 4 TB bandwidth
  • 1 IPv4 + 1 IPv6
  • Note: Full root · KVM · self-managed
Choose L-4

L-5

The most cores, memory and storage

₹4,892/mosave 17%

billed ₹58,701 per year

  • 12 vCPU
  • 16 GB RAM
  • 180 GB NVMe SSD
  • 5 TB bandwidth
  • 1 IPv4 + 1 IPv6
  • Note: Full root · KVM · self-managed
Choose L-5
  • Seamless migration from your current host
  • No lock-in, cancel anytime
  • SLA-backed 99.9% uptime
  • Plan prices exclude 18% GST, added at checkout for billing addresses in India

Each plan renews for the same term at the price in force then, shown before you pay. Promo codes apply to the first term only.

What Node.js® is

Node.js® is the runtime that lets JavaScript run outside a browser: in its own words, a free, open-source, cross-platform JavaScript runtime for building servers, web apps, command-line tools and scripts. In practice it is what your API, your Express or Next app, your Discord bot or your queue worker is actually running on. It is MIT-licensed and free, and it is the ordinary answer for a team that already writes JavaScript and would rather not write the back end in something else. What it is not is a thing you install and log into: nobody has "a Node.js" the way they have a WordPress site. You have an app. This page is about running it.

The software is the open-source project from nodejs.org. We run the server it sits on; we are not affiliated with the project.

How your Node.js app runs on a server Traffic arrives over HTTPS at a reverse proxy. Behind it your app is a long-lived process that a supervisor keeps alive and restarts after a reboot, holding open sockets and timers, with a database beside it on the same machine. Traffic Browsers · API clients · sockets that stay open HTTPS Your VPS · root is yours Reverse proxy · TLS Your app, still running A supervisor restarts it, and after a reboot too Node.js® LTS you chose Your database Sockets, timers, state: kept No cold start, no per-request meter
  • v24 LTS Supported to Apr 2028
  • MIT Open source, free
  • Root It is your machine

  • One language, both ends

    The same JavaScript your front end is written in, running the server too. The reason it won is not benchmarks; it is that a team stops context-switching.

  • Good at waiting

    Node is built around doing other things while it waits for the network or the disk. That is why it suits APIs, chat, streams and anything holding a lot of connections that are mostly idle.

  • npm, for better and worse

    The largest package ecosystem there is, which means you rarely start from nothing, and means the machine needs to actually build native modules when you install them.

  • LTS lines you can plan around

    Even-numbered releases become long-term support and get years of fixes; odd-numbered ones never do. v24 is an LTS line supported into 2028, and it is what we set up unless you ask otherwise.

  • It expects to keep running

    A Node app is a long-lived process holding state, connections and timers. It is not a script that starts and stops per request, which is precisely where shared hosting and it fall out.

Why it wants a server

A Node app is a process, and a process needs somewhere to live. It holds open sockets, keeps timers, caches things in memory and expects to still be there in an hour, none of which survives a host that starts a fresh interpreter for every request. It also needs to compile native modules at install time, hold a build step, and be restarted on its own terms. Give it a machine with root and a supervisor and all of that is unremarkable. Try it anywhere else and you spend your week fighting the platform instead of shipping.

Why run it with us

Alive

Your app stays up

The process supervisor restarts your app if it crashes and brings it back by itself after a server reboot, so one unhandled exception does not leave the site down until somebody notices.

OS

Ubuntu, by preference

We set up Node on Ubuntu unless you need something else: it's what we know best and support fastest. AlmaLinux and Debian are fine too; tell us before we build and we'll match it.

LTS

The version you choose

Run the long-term-support (LTS) version you've tested with, not whatever the host happened to install. Keep it, and move up when you're ready, not when someone else decides.

Real

Whatever you built, it runs

Live connections, background jobs, a build step, scheduled tasks: whatever the app does, it runs on a machine where you hold root and install what it needs.

Human

An engineer answers

Our helpdesk answers first and passes anything technical straight to an engineer, so when the problem is the server and not your code, you reach someone who understands both.

How it works

  1. 01

    Choose your plan

    Pick the size that fits the app; you can move up later without rebuilding anything.

  2. 02

    We set the machine up

    Your VPS arrives with the Node.js® LTS line you asked for, a process supervisor, a reverse proxy and TLS in place. A database beside it if you want one.

  3. 03

    Ship your app

    Deploy it however you already do: git, rsync, a CI pipeline, a container. It is your machine and you have root; we will wire the deploy up with you if you would rather not.

  4. 04

    Yours to run

    From handover it is a self-managed VPS with full root: OS and Node.js® updates, security hardening and backups are yours, and you decide what runs beside the app. Hardware, network and the virtualisation layer are on us. If you would rather not look after a Linux box, add paid Server Management at checkout.

Questions

Which Node.js® version do I get?

The one you ask for. By default we set up v24 LTS (supported into April 2028), because an LTS line gets security fixes for years rather than months. If your app is pinned to v22 we set up v22 (it is in maintenance until April 2027). We would steer you away from odd-numbered releases: they never become LTS, so they are a support cliff you do not need.

Is this a PaaS like Vercel or Render?

No, and it is worth being clear about the trade. Those give you a slick deploy and take decisions away from you: pricing that scales with usage, limits on what a process may do, cold starts. This is a plain server with root, a supervisor and a reverse proxy: less magic, no surprises on the bill, no ceiling on what your app is allowed to be. If you want the magic, use the magic. People come here when it has started to chafe.

Are backups included?

Backups are part of running the server, so on this self-managed line they are yours to arrange. The simplest route is the “Offsite Backups for Data” option at checkout, which adds offsite copies of your data. If you would rather backups were simply handled, Managed Cloud VPS includes daily best-effort backups to separate storage.

Can I run a database on the same box?

Yes. Postgres, MySQL or MariaDB, Redis, whatever the app needs, on the same machine when it is small, or on its own when it is not. It is your server; nothing about it is fenced off.

What happens if my app crashes?

The supervisor restarts it, and it comes back on its own after a reboot too. If it starts crash-looping, that is a bug worth chasing rather than a problem the restarts have solved. If you want our engineers watching the server for you, that is what paid Server Management adds.

Should I choose Managed Cloud VPS instead?

Choose this plan if you, or someone on your team, is happy running a Linux server: you get root and it costs less. Choose Managed Cloud VPS if you would rather not be the sysadmin: our engineers hold root and do the provisioning, hardening, patching, tuning and incident response, with 2 engineer hours a month included.

What if my app outgrows its plan?

Move up a tier: talk to us and we resize the server with minimal downtime. If even the largest tier is not enough, Managed Cloud VPS can be built to a custom size, and a dedicated server gives you a whole machine.

Node.js® is a registered trademark of the OpenJS Foundation. IndicHosts is not affiliated with, endorsed by, or sponsored by the OpenJS Foundation, and is not certified under any of its marks. We use the name only to refer to the runtime our hosting is built to run.

Not sure which size your app needs?

Tell an engineer what the app does and how busy it gets, and we'll point you at the right tier, or tell you honestly if Managed Cloud VPS is the better fit.

Talk to us See the Standard KVM VPS