A VPS for your Bitcoin node. The whole chain, from $8.09 a month.
Run Bitcoin Core, an Electrum server or a Lightning node on a Storage VPS with room for the full blockchain, an NVMe cache in front of RAID-10 disks and 8 TB of traffic a month. Paid in bitcoin, with no ID.
From a deposit to a syncing node
One top-up, one order, one configuration file. The initial download is the only part that takes time.
-
01
Create an account with an e-mail address
No name, phone number or document, and nothing is charged until you top up.
-
02
Top up in BTC
Fund the balance from $25, credited after one confirmation. At $8.09 a month, ST-1 runs three months on the minimum top-up.
-
03
Deploy and start bitcoind
Pick a Storage plan in Frankfurt, Helsinki or New York with Ubuntu 24.04, download and verify Bitcoin Core, and start the initial block download.
- About 890 GBFull node todayBlocks, undo data and chainstate, without txindex
- 1 TBStorage on ST-1RAID-10 hard disks behind a 40 GB NVMe write-back cache
- 8 TB a monthTrafficRoom for the first sync (about 0.8 TB) and a listening node
- NoneIdentity checksPay in BTC, ETH, XMR or USDT
Storage VPS plans for a full node
RAID-10 hard disks behind an NVMe write-back cache, in Frankfurt, Helsinki and New York. ST-1 holds a full node today and will be tight within about a year; ST-4 holds one with indexes for many years.
| Plan | vCPU | RAM | Storage | Traffic | Monthly | Order |
|---|---|---|---|---|---|---|
| ST-1In stock | 2 vCPUAMD EPYC | 4 GBDDR5 ECC | 1 TB HDD+ 40 GB NVMe cache | 8 TB1 Gbps | $8.09/mo | Order |
| ST-2 | 2 vCPUAMD EPYC | 8 GBDDR5 ECC | 2 TB HDD+ 80 GB NVMe cache | 12 TB1 Gbps | $13.69/mo | Sold out |
| ST-4PopularIn stock | 4 vCPUAMD EPYC | 16 GBDDR5 ECC | 5 TB HDD+ 160 GB NVMe cache | 20 TB1 Gbps | $28.99/mo | Order |
| ST-8Low stock · 3 left | 8 vCPUAMD EPYC | 32 GBDDR5 ECC | 10 TB HDD+ 320 GB NVMe cache | 32 TB1 Gbps | $53.09/mo | Order |
Sizing a Bitcoin node honestly
A full Bitcoin Core node takes about 890 GB today: 774 GB of blocks, about 108 GB of undo data and a 12 GB chainstate. It grows by roughly 94 GB a year, and a transaction index adds about 66 GB. Many guides still quote 600 GB; that is out of date. ST-1 holds a full node today, though it will be tight within about a year; ST-4, with 5 TB, holds a full node, its indexes and an Electrum server for many years.
Hard disks are slow at the random reads and writes the chainstate needs and fine at appending blocks. Storage plans put a 40 GB NVMe write-back cache in front of the RAID-10 array, so the 12 GB chainstate stays on flash while blocks stream to the disks. Give Bitcoin Core as much dbcache as the plan allows during the first sync, and expect that sync to take from many hours to several days, depending on memory, disk and bandwidth. Once synced, a node needs very little.
If the node only backs your own wallet, you do not need the whole history on disk. A pruned node verifies everything in the same way and keeps about 12 GB, so it fits on a VPS-1 for $3.29 a month. It cannot serve old blocks or feed an Electrum server, and Lightning runs on it with caveats: LND supports a pruned backend at some cost in speed and bandwidth, Core Lightning only partially. For Sparrow, Electrum or a block explorer on your own server, run a full node. Our step-by-step guide covers both.
What people run on a node VPS
- Bitcoin CoreA fully validating node for your own wallets, reachable on port 8333 to serve the network.
- LightningLND or Core Lightning beside an always-on bitcoind on the same server, with port 9735 open to peers.
- Electrum serverselectrs (about 7% of the block data, no txindex) or Fulcrum (needs txindex) for Sparrow and Electrum wallets.
- Wallet privacyYour wallet asks your own node about its addresses instead of a public server.
- Explorers and APIsA block explorer or mempool view for your team, behind a password or a VPN.
- DevelopmentSignet and testnet nodes to test payment code before it touches mainnet.
Everything a server needs, nothing to add on
- KVM, full rootReal virtualisation with your own kernel. Any OS from our images, or your own ISO.
- Dedicated NVMeLocal NVMe Gen4 in RAID-10. Your disk is not a shared network volume.
- DDR5 ECC memoryError-corrected memory on every node. No ballooning, no overselling of RAM.
- 1 Gbps portGenerous monthly traffic, then unmetered at 100 Mbps. Never a surprise bill.
- SnapshotsTake a snapshot before every change and roll back in seconds. Two included.
- Private networkFree VLAN between your servers in the same location, plus floating IPs.
- IPv4 + /64 IPv6One clean IPv4 and a /64 IPv6 block per server, reverse DNS editable.
- DDoS protectionAlways-on volumetric filtering up to 3 Tbps, at no extra cost.
Same price in all 6 locations
- Core network site
- Data center
Europe3
FRAFrankfurtGPU
AMSAmsterdamGPU
HELHelsinki
North America2
NYCNew YorkGPULAXLos Angeles
Asia-Pacific1
SINSingaporeGPU
Other ways to pay, other things to rent
Bitcoin, Ethereum, Monero or Tether fund one USD balance. Each coin has its own page with confirmation times, fees and pitfalls.
Bitcoin node hosting questions, answered
How much disk does a Bitcoin full node need in 2026?
About 890 GB without indexes as of October 2026, growing by roughly 94 GB a year; about 960 GB with txindex, and more with an Electrum server. A pruned node needs about 12 GB. ST-1 (1 TB) holds a full node today but will be tight within about a year; ST-4 (5 TB) holds one with indexes for many years.
Is a hard disk fast enough for Bitcoin Core?
For a node, yes, with a cache in front of it. The chainstate needs fast random access; the blocks are mostly appended and rarely read. Storage plans keep hot data on a 40 GB NVMe write-back cache in front of RAID-10 hard disks, so the 12 GB chainstate stays on flash. The first sync is slower than on all-NVMe storage, and a large dbcache helps most.
How long does the first sync take?
From many hours to several days. About 0.8 TB has to be downloaded and verified, and memory (dbcache), disk speed and peers set the pace. Published benchmarks on large NVMe machines with a big cache finish in 7 to 12 hours; a 4 GB plan with hard disks takes longer. Once synced, keeping up needs very little.
Can I run a pruned node on a smaller plan?
Yes. With prune=550 a node keeps about 12 GB and fits on VPS-1 for $3.29 a month. It validates every block like a full node and works as a wallet backend; it cannot keep a transaction index, serve old blocks or back an Electrum server, and Lightning implementations support it only with caveats.
How much traffic does a node use?
The first sync downloads about 0.8 TB. After that, bitcoin.org notes that full nodes on fast connections commonly upload 200 GB a month or more; maxuploadtarget caps it. ST-1 includes 8 TB a month, and past the allowance the port slows to 100 Mbps; nothing is billed.
Is running a node allowed?
Yes, on every plan: full nodes, Lightning nodes and Electrum servers are welcome. What the acceptable-use policy forbids on VPS plans is mining, which is allowed on dedicated and GPU servers.
From the people who run the racks
GuidesHow to run a Bitcoin full node on a VPS in 2026A full node is about 890 GB now, not 600. How to size the server, install Bitcoin Core from verified binaries and run it as a service, pruned or full.
SecurityThe first hour on a new Ubuntu VPS: a hardening checklistKeys only, a firewall that defaults to deny, automatic patches and a few kernel knobs: the twelve steps we wish everyone did before deploying anything.
GuidesA WireGuard hub for your whole team on a $3 VPSA hub-and-spoke VPN with per-device keys, split tunnelling and IPv6, in twenty lines of config and one systemd unit. Your VPS from $8.09 a month, online in under a minute.
Top up from $25 in BTC, ETH, XMR or USDT. Your balance never expires and unused funds are refundable.