Run a Node on a VPS in India

Run a Node on a VPS in India

Published
AuthorDevansh

Yes, you can run a blockchain node on a VPS from India, and for most operators it is the simplest way to start. A VPS gives you a fixed IP address, power and internet that stay on while you sleep, and bandwidth you do not have to manage yourself. The job is to pick the right region and machine size for your chain, install a supported Ubuntu LTS release, lock the server down, and watch the first sync until the node is healthy. Get those steps right and the node mostly looks after itself afterwards.

This post walks through those steps with India in mind: where to host, how to pay, and what to check before you commit to a provider. It follows the same approach as our Ubuntu validator guide. If you have never run a node at all, start on a testnet first with our testnet setup guide, where mistakes cost nothing.

VPS or home server: which fits a node?

A home server works when you have stable power, a reliable connection, and a public IP address you can keep. In practice, most Indian homes do not have all three. Power cuts restart the machine, home broadband IPs change, and upload speeds are often far lower than download speeds, which matters because a node uploads as much as it downloads. A VPS removes all three problems for a predictable monthly cost, and you can rebuild or resize it without touching hardware.

The trade-off is control. On a VPS you rent the machine, so you cannot add a disk yourself, and you depend on the provider's network and support. For a first node, that trade is usually worth it. A home lab makes more sense later, when you know your chain's real disk and bandwidth use and want a second machine for redundancy.

Pick the region first, then the machine

Latency decides how fast your node hears about new blocks and answers peers. A node hosted far from the network sees blocks later, and a validator that sees blocks late attests late. For operators in India, the practical choice is a region in or near India, such as Mumbai where your provider offers it, or Singapore as the next closest hub. Check your provider's region list on the day you sign up, and test latency yourself with ping and mtr before you commit to a long contract.

Machine size comes second, and it depends on the chain. As a starting point that fits most mainstream chains, look for at least 4 vCPUs, 16 GB of RAM, and NVMe SSD storage with generous headroom above the chain's current size. Always check the chain's official hardware docs on the day, because requirements move with every major release. Chains with heavy state, such as Solana, need far more than this, and an archival node needs terabytes, which is a different decision covered in our archival node setup guide. Two things to refuse outright: spinning disks instead of SSDs, which cannot keep up with chain tip, and a plan whose disk you will outgrow in a few months, because migrating chain data later is slow and painful.

Bandwidth: the cost that surprises people

The first sync downloads the whole chain, which can be hundreds of gigabytes, and a healthy node keeps uploading to peers afterwards. Some VPS plans include generous bandwidth, others charge for overages, and a few throttle after a limit. Read the bandwidth terms before you buy, and prefer unmetered or clearly priced transfer over a cheap plan with a small allowance. Set a billing alert on day one so a sync spike never becomes a surprise invoice.

Start from a supported Ubuntu LTS

Use a long-term support (LTS) release of Ubuntu, not an interim release, because a node server should not need a full OS upgrade every nine months. As of 2026-11-08, Ubuntu 24.04 LTS is the safe default: standard security updates run until May 31, 2029, and most node software publishes packages for it. Ubuntu 26.04 LTS was released in April 2026 with support until May 2031, and upgrades from 24.04 to 26.04.1 opened in late September 2026, so it is a real option if your client software already supports it. Ubuntu 22.04 LTS ends standard support in May 2027, so do not start a new node on it. Whatever you pick, confirm the dates on Canonical's release page on the day, and keep the OS patched with unattended upgrades.

Most VPS providers let you pick the OS image at creation time. Choose Ubuntu 24.04 LTS, set a strong root password or SSH key, and note the IP address and login details somewhere safe. If the provider offers a network-level firewall, enable it now and open only SSH and the chain's peer-to-peer port. Everything else stays closed.

Lock it down before you install the node

A node server is a public machine with open ports, so harden it before the chain data goes on. Create a non-root user and give it sudo. Copy your SSH public key to that user and disable password login for SSH entirely. Enable the firewall and allow only SSH and the node ports. Enable automatic security updates. If you run SSH on the default port, consider fail2ban to slow down password guessing, though key-only login already makes that attack fail.

Our SSH and firewall guide for nodes walks through each of these steps with commands. Do not skip this because the node is only a testnet node: testnet machines get scanned just like mainnet ones, and a compromised server can attack others even if it holds no real funds.

Install the node and watch the first sync

With the server hardened, install the node the way the chain documents it. Docker Compose is the simplest path for most operators: one compose file holds the image, the ports, and the volume that stores chain data, and upgrades become a one-line image change. Keep chain data on a Docker volume or a mounted disk, never inside the container's writable layer, or you will lose it on the next rebuild. If the chain recommends a binary install, follow its docs exactly and run the node as a systemd service so it restarts after a reboot.

The first sync is the longest step. A full node can take hours to days depending on the chain and disk speed, and an archive sync takes far longer. Watch the logs until the node reports it is synced, then confirm against a public explorer: compare your block height with the chain tip and check the gap is closing, not growing. Our guide on checking if your node is synced covers the exact checks. Only after sync should you connect a wallet, an app, or a validator key to it.

Paying from India and watching the bill

Payment options vary by provider. Some global VPS providers accept Indian cards and UPI, others accept only international cards, and a few Indian providers bill in rupees. Check the payment page before you create the account, and confirm whether the plan is billed monthly or hourly, because hourly billing makes a short test cheap but a forgotten test server expensive. VPS prices change often, so compare providers on the day you buy, not from a blog post.

Set two alerts on day one: one for bandwidth or disk use, and one for the monthly bill. Disk growth is the quiet cost driver, because chain data grows every week and a full disk stops the node. Our validator cost guide explains the full monthly model, including the hidden costs of monitoring and your own time.

When a VPS is the wrong answer

A single VPS is wrong for three jobs. First, archival nodes, which need terabytes of fast NVMe storage that most VPS plans do not offer at a sane price. Second, very high-throughput chains where the CPU and disk needs exceed what a shared virtual machine can deliver. Third, setups that need hardware you cannot rent, such as a hardware security module for key management. In those cases a dedicated server or a home machine with enterprise NVMe drives is the honest answer, and a VPS can still serve as your second, redundant node.

A VPS in India is a good first node because it removes power, IP, and uptime problems in one step. Pick a region near your users, size the machine from the chain's official docs, start on Ubuntu 24.04 LTS, harden the server, and watch the first sync to completion. If your team would rather have setup, monitoring, and upgrades handled for you, see our blockchain node setup and node operations pages, or start with a free infra audit and we will review your VPS choice along with the rest of the stack.

Disclaimer: This post is educational only, not financial advice. Figures are listing or project data as of 2026-11-08 and may change - always confirm version numbers, requirements, and dates in the official docs before acting on them.

Related Articles

DevOps & Infrastructure Services

Need hands-on help? We build and manage the infrastructure behind the concepts covered in this article.

DevOpsBy Assistant

How can we help?

Select a topic to get started: