KVM 2
KVM 2 · 1 vCPU · 2 GB RAM
$4.92
- 1 vCPU, 2 GB RAM, 40 GB NVMe
- 4 TB traffic, 1 Gbit/s port, 1 IPv4 + /64 IPv6
- Renews every 30 days from your crypto balance
- Kyun: $6.57 a month for 1 vCPU / 2 GB RAM / 40 GB SSD
Use case · Bitcoin and Lightning nodes
How much disk a pruned and a full Bitcoin node need in October 2026, which plan fits each, and what changes when you add Lightning.
Quick answer
Can I run a Bitcoin or Lightning node on a VPS?
Yes, you can run a Bitcoin or Lightning node on a VPS if it is pruned or the disk holds the whole chain. On OffshoreKVM, a pruned Bitcoin Core node fits KVM 2 ($4.92 for 30 days); KVM 4 ($8.25) leaves room for Lightning. A full archive node does not fit: the chain was about 779 GB on 28 October 2026. No KYC, pay in crypto.
| Block data | About 779 GB on 28 October 2026, without database indexes (blockchain.com chart) |
|---|---|
| Pruned node | prune=550 (MiB) is the minimum; Bitcoin Core says a pruned node can store as little as 10 GB in total |
| RAM | 2 GB minimum (bitcoin.org) |
| Initial sync | Every block is downloaded and checked once, pruned or not |
| Upload | Can reach 200 GB or more a month on a fast connection (bitcoin.org) |
| P2P port | 8333, open for inbound peers |
| Largest OffshoreKVM plan | KVM 16: 8 vCPU, 16 GB RAM, 320 GB NVMe, 20 TB traffic |
| Traffic rule | Every VPS has one dedicated IPv4 address and IPv6. Traffic quotas count outgoing data per 30-day period; over the quota there is never an automatic extra charge |
| Payment | Bitcoin on-chain and other coins: BTC, USDT, USDC, ETH, SOL, LTC, XMR. No Lightning, no KYC |
An unpruned Bitcoin Core node needs more than 779 GB today, because that was the size of the block data alone on 28 October 2026. The UTXO database, the OS and any optional index come on top. bitcoin.org still says "roughly 740 gigabytes", a figure the chain has already passed.
A pruned Bitcoin node checks every block like a full node, then deletes old blocks: Bitcoin Core's minimum prune target is 550 MiB. Pruning is not compatible with -txindex, so block explorers and Electrum-style servers need the full chain.
KVM 2 is the smallest plan for a pruned node, and KVM 4 is the right size with Lightning. No plan holds a full archive node. KVM 1 has 1 GB of RAM, half of bitcoin.org's 2 GB minimum.
| Plan | Resources | Pruned node | Pruned + Lightning | Full archive node |
|---|---|---|---|---|
| KVM 1 ($3.08) | 1 vCPU, 1 GB RAM, 20 GB NVMe, 2 TB traffic | ✗ | ✗ | ✗ |
| KVM 2 ($4.92) | 1 vCPU, 2 GB RAM, 40 GB NVMe, 4 TB traffic | Yes, prune=15000 | Tight | ✗ |
| KVM 4 ($8.25) | 2 vCPU, 4 GB RAM, 80 GB NVMe, 8 TB traffic | ✓ | Yes, prune=50000 | ✗ |
| KVM 8 ($13.50) | 4 vCPU, 8 GB RAM, 160 GB NVMe, 12 TB traffic | ✓ | ✓ | ✗ |
| KVM 16 ($20.62) | 8 vCPU, 16 GB RAM, 320 GB NVMe, 20 TB traffic | ✓ | ✓ | No: 320 GB is less than 779 GB |
prune is in MiB: 15000 keeps about 16 GB of recent blocks, 50000 about 52 GB. Add the UTXO database and the OS to size the disk.
A full archive node needs a server with about 1 TB of disk today, which few offshore VPS plans offer. Among the VPS plans we recorded at 36 active offshore hosts on 29 October 2026, only two had 800 GB of disk or more. Storage-only products were not counted.
A home computer with a 2 TB disk holds an archive node with room to grow. For other hosts, see the best offshore VPS in 2026.
| Host and plan | vCPU / RAM / disk | Fits 779 GB of blocks? | Price per month | Monero | ID at signup | Location |
|---|---|---|---|---|---|---|
| OffshoreKVM KVM 16 | 8 / 16 GB / 320 GB NVMe | No | $20.62 | ✓ | No | NL, IS, CH, RO |
| Privex V8-SE-HDD | 4 / 8 GB / 1,300 GB HDD, 8 TB traffic | Yes, with room to grow | $40.00 | ✓ | No | SE |
| Bacloud LINUX VDS 6 | 8 / 40 GB / 800 GB NVMe | Too tight once the OS and the UTXO database are added | €160 ($178.08) | — | In some cases | LT, NL, GB, US |
Prices checked on
Monthly prices read on each host's pages on 29 October 2026; 1 EUR = 1.1130 USD (ECB, 29 October 2026). OffshoreKVM KVM 16 is shown for comparison. OffshoreKVM publishes this table.
Yes, a Lightning node runs on a VPS, next to its own Bitcoin Core node. Core Lightning needs bitcoind 25.0 or later and supports a pruned node only partially. If bitcoind prunes a block before Core Lightning has processed it, Core Lightning gets stuck and cannot sync again.
So give a Lightning setup a large prune target, such as prune=50000 on KVM 4. Then compare the block heights from lightning-cli getinfo and bitcoin-cli getblockchaininfo. A Lightning node keeps its keys online on the server. Fund it only with what you accept to keep on a rented machine, and read what your VPS provider can see on your server.
The first sync downloads the whole chain once, about 779 GB. A running node can then upload 200 GB or more a month, per bitcoin.org. Every VPS has one dedicated IPv4 address and IPv6. Traffic quotas count outgoing data per 30-day period; over the quota there is never an automatic extra charge. So the initial download does not count against a OffshoreKVM quota; uploads do.
KVM 2's 4 TB quota covers bitcoin.org's 200 GB upload figure many times over. To cap upload, set maxuploadtarget in MiB per day; bitcoin.org suggests at least 144. blocksonly=1 cuts traffic to about 150 MB in and 1 MB out per day, but your node then sees transactions only once they are mined.
Install Bitcoin Core from bitcoincore.org (version 32.1 on 29 October 2026), set a prune target, open port 8333 and start the daemon. The initial sync takes a long time on any VPS, because every block is checked.
# Keep about 52 GB of recent blocks (value in MiB, minimum 550)
prune=50000
# Soft cap on upload, in MiB per day (bitcoin.org: at least 144)
maxuploadtarget=5000
# Start and check progress:
# bitcoind -daemon
# bitcoin-cli getblockchaininfo ("pruned": true, "verificationprogress")You can pay with Bitcoin on-chain, but not with Lightning. OffshoreKVM accepts BTC, USDT, USDC, ETH, SOL, LTC, XMR, with no KYC. According to OffshoreKVM's check of 29 October 2026, 4 of 36 active offshore VPS hosts accept Bitcoin Lightning: MyNymBox, TLDBunker, Bit.Hosting and VPSBG. TLDBunker had not opened orders yet. A Bitcoin payment sits on a public ledger: see whether paying for a VPS with Bitcoin hides who you are. The steps are in how to buy a VPS with Bitcoin, and every coin is compared in which offshore VPS providers accept crypto.
KVM 2 for a pruned node, KVM 4 or KVM 8 with Lightning. Every plan is on how much an offshore VPS costs at OffshoreKVM.
KVM 2 · 1 vCPU · 2 GB RAM
$4.92
Most popular
KVM 4 · 2 vCPU · 4 GB RAM
$8.25
KVM 8 · 4 vCPU · 8 GB RAM
$13.50
In every plan: Root access with your SSH key · NVMe storage · IPv4 + IPv6 · DMCA ignored · No logs · No KYC
Yes. A node on a VPS checks every block and rule itself, and helps the network with inbound connections on port 8333. The host controls the hardware, so keep wallet keys elsewhere and use the VPS node for validation and relaying.
bitcoin.org lists 2 GB of RAM, 7 GB of free disk with pruning, 400 kbit/s of upload and 6 hours a day online. A full node needs about 779 GB of disk for blocks alone, as of 28 October 2026.
Yes, with care. Core Lightning supports pruned nodes partially and gets stuck if Bitcoin Core deletes a block it has not processed yet. A large prune target, such as 50,000 MiB, gives it room.
No. Cryptocurrency mining is not allowed on any OffshoreKVM VPS. Running a Bitcoin, Lightning or Monero node is a different use and is fine. For Monero, see what VPS you need to run a Monero node.
No. A person creates your VPS once your payment is confirmed, and it is ready minutes later, never more than one hour after that confirmation; your dashboard shows the status, then the IP address once the VPS is running. Start the initial sync as soon as the IP shows, because it takes the longest.
Run your node on a KVM VPS
KVM 4: 2 vCPU, 4 GB RAM, 80 GB NVMe for $8.25 per 30 days. No KYC, crypto only.
From $3.08/month · no KYC
Deploy a VPS