We've got a new update. We now offer our own Web Console. Open the console and type ssh root@your-server-ip to reach any server you own, right from your browser. No SSH app needed.
Run Bitcoin Core on a server that never sleeps, with a disk matched to the chain as it is today. A pruned node starts at $8.50 a month. A full node on a 1 TB NVMe VPS is $23.75. No ID, no card, pay in Bitcoin, Monero or USDT.
Figures from the Bitcoin Core documentation and a 2026 hardware survey, not from a sales sheet. Sources are listed at the bottom.
Prices are for Romania on a one-month term. A 12-month term takes 50% off. Choose by what the node is for, not by the biggest disk.
or $4.25/mo on a 12-month term (−50%)
Validates every block itself and keeps only the newest block files (about 12 to 22 GB), so a 60 GB disk is plenty. Cannot serve old blocks to other nodes.
Configure and orderor $11.88/mo on a 12-month term (−50%)
Holds the whole chain (about 760 GB in mid-2026, growing 60 to 70 GB a year). 1 TB leaves roughly three years of growth.
Configure and orderor $41/mo on a 12-month term (−50%)
For txindex, an Electrum server or a block explorer, which add tens of GB on top of the chain, and for years of headroom.
Configure and orderA node does the same job in all three setups: it downloads every block, checks every rule and refuses anything invalid. What changes is how much of the old data you keep afterwards.
Run a pruned node. It validates the whole chain, then throws away old block files and keeps the newest ones. With prune=10000 it stays around 22 GB. You trust nobody for your own balance, which is the point. What you give up is the ability to serve old blocks to other nodes and to rescan a wallet from a very old date without re-downloading. For this job the $8.50 plan is enough.
Run a full node that keeps every block. Helping new nodes sync, running BTCPay Server, or giving a Lightning node a complete backend all work best this way. A 1 TB NVMe VPS holds the chain (about 760 GB) plus the 12 GB chainstate with roughly 200 GB spare. At 60 to 70 GB of growth a year that is around three years. Put a disk alert at 85% and you will not be surprised.
These indexes add tens of gigabytes on top of the chain and want fast random reads. Take the dedicated Medium server: it has two 2 TB NVMe drives, so the chain sits on one drive with years of room and the index on the other.
The first sync is the heavy part. It reads and writes constantly for most of a day, which is why NVMe matters more than extra CPU cores. After that a node idles at a few percent of one core.
| Pruned | Full node | Full + indexes | |
|---|---|---|---|
| Disk in use | 12 to 22 GB | ~780 GB today | ~830 GB and up |
| Validates every block | Yes | Yes | Yes |
| Serves old blocks to peers | No | Yes | Yes |
| Rescan wallet from old dates | Slow | Fast | Fast |
| Electrum server or explorer | No | No (needs index) | Yes |
| Recommended build | 2 vCPU · 4 GB · 60 GB | 4 vCPU · 8 GB · 1 TB | Dedicated Medium |
| Price here (Romania, 1 month) | $8.50 | $23.75 | $82 |
Disk figures from the 2026 hardware survey and the Bitcoin Core docs. Exact usage depends on your Core version and settings.
Create the file as the user that runs the node (~/.bitcoin/bitcoin.conf). Check every option against the current Bitcoin Core release notes before you rely on it.
# Full node: keeps every block (the default)
server=1
dbcache=4000 # MB of RAM for the UTXO cache; speeds up the first sync a lot
maxconnections=40
# after the first sync you can lower dbcache to 1000 or less# Pruned node: validates everything, keeps about 10 GB of recent blocks
server=1
dbcache=2000
prune=10000 # MB. The minimum is 550# sudo apt install tor, then add your node's user to the debian-tor group
proxy=127.0.0.1:9050
listen=1
bind=127.0.0.1
onlynet=onion # slower first sync and fewer peers, but no clearnet IP exposuresudo ufw allow 8333/tcp # Bitcoin peer port
# never open 8332 (RPC) to the internetVerify the download first: get Bitcoin Core only from bitcoincore.org and check the signatures and checksums as that page describes. Our full tutorial covers the service file and the rest.
Your node is a public address on the Bitcoin network. Peers see its IP, and any wallet that connects to it tells it which addresses to watch. If that server is rented with a passport scan and a card, the account holder is one subpoena away from the node and from everything that wallet asked it.
That is the case for hosting where there is no identity file to hand over:
What it does not do: a server is not a vault. Keep spending keys on a hardware wallet, not on the VPS. The node only needs your watch-only data. And the host can always see that traffic exists, even if Tor hides who the peers are. Hosting without KYC lowers what a third party can learn about you. It does not make you invisible.
A full node needs about 760 GB for the blockchain as of mid-2026, plus around 12 GB of chainstate, and the chain grows 60 to 70 GB a year. Plan for at least 1 TB. A pruned node can run in 12 to 22 GB.
Yes. A VPS is a good home for a node because it is always online on a fast connection. Our largest NVMe disk on a VPS is 1 TB, which fits a full node today with about three years of growth. A pruned node fits on the smallest plans from $8.50 a month.
Yes. It downloads and checks every block against the consensus rules, exactly like a full node. It only deletes old block files afterwards, so it cannot serve history to other nodes. For checking your own wallet it is just as trustworthy.
On a cloud VPS with default settings, benchmarks from 2025 put a full initial block download at roughly 12 to 24 hours. A small VPS with little RAM takes longer. Setting dbcache to 4000 (MB) helps when the server has the memory.
A node that accepts inbound connections moves roughly 300 to 500 GB a month in total. A node that only connects out uses far less. Our VPS plans list unlimited transfer on a 1 or 2 Gbps port, so a node does not run into a quota.
Yes. A full Bitcoin Core node is the usual backend for LND or Core Lightning. See Lightning node hosting for sizes and a working config.
No. You create an account with a generated login, top up your balance with Bitcoin, Monero, USDT or other supported coins, and deploy. There is no ID check and no card. You remain responsible for what you run, under our terms.
Switch to a pruned node, or move to the dedicated Medium server, which has 2 TB drives. Moving is a copy of the data directory plus your config. A disk alert at 85% gives you months of notice.
Checked 19 October 2026. Chain sizes and software requirements change, so confirm against the source before you order.
Pick a size, pay in crypto, and log in as root within minutes. No ID, no card.
