Bottom line: a pruned Bitcoin full node runs comfortably on a 2 vCPU / 4 GB VPS with ~10 GB disk, and a Lightning node on top is feasible. A full unpruned node (600+ GB) is out of budget-VPS reach on storage, but pruned is the smart default for most hobby setups anyway.
Reality check: a VPS Bitcoin node is centralized-ish — you're renting someone else's hardware. For self-sovereignty that matters, run your own iron. For privacy, API access, and routing your own Lightning channels, a VPS is fine.
What each node type needs
| Node | RAM | Disk | Best on VPS? |
|---|---|---|---|
| Pruned full node | 4 GB | ~10 GB | ✅ Yes |
| Full unpruned node | 4 GB | ~600 GB | ⚠️ Storage gets pricey |
| Lightning node | 2–4 GB | 10–20 GB | ✅ Yes |
A 4 GB VPS is the sweet spot — that's why the how much RAM guide points mid-tier boxes at exactly these workloads.
Quick start: pruned node on a VPS
# on a 4 GB VPS
# install bitcoind, then run with pruning
bitcoind -prune=550 -datadir=/var/lib/bitcoin -daemon
# Lightning (if you want channels)
# install LND or Core Lightning, connect to your bitcoindSet up your SSH + firewall first — the VPS security checklist covers exactly the base you need before a node faces the internet.
Keep it cheap and predictable
- Use Uptime Kuma to watch your node's RPC/API stays up.
- Schedule self-hosted automation for channels and rebalancing.
- Pick a provider with real bandwidth — budget hosts that throttle hurt node sync. Compare providers.
Affiliate disclosure: we earn a commission on Vultr signups at no cost to you.