VPS-L · VPS
- AMD EPYC 7313P (6 vCPU)
- 16 GB DDR4 · 200 GB NVMe
- 1 Gbps · Unlimited bandwidth
Pruned node (~100 GB) with fast sync — a personal wallet backend at pocket price.
Using someone else's Monero node leaks your wallet's queries to strangers. Run monerod on no-logs offshore hardware, connect your wallets over Tor or SSH, and stop outsourcing the last metre of Monero's privacy.
Monero's cryptography hides amounts and parties on-chain — but the node your wallet talks to still sees your IP, your refresh height and which outputs you ask about. Public remote nodes are run by volunteers, and occasionally by adversaries. Your own monerod closes that gap: the wallet scans against hardware you rent anonymously, transactions broadcast through Tor, and the chain data sits in a jurisdiction that doesn't do fishing expeditions. At ~270 GB it's the most affordable serious node on this site.
Your seed never leaves your device — but your queries do. A personal node means nobody correlates your IP with your output requests.
monerod pushes outgoing transactions through Tor natively (tx-proxy). Your transactions enter the network with no origin IP.
270 GB full, ~100 GB pruned: VPS-L handles a pruned node, VPS-PRO a full public one. XMR-paid, naturally.
Open the restricted RPC and your box helps mobile users as a public remote node — or keep it firewalled to you alone.
Realistic sizing for a mainnet node in 2026 — chain size, memory, disk and bandwidth. Based on what actually runs in production, not on minimum specs that stopped being true two years ago.
| Client software | monerod 0.18.x |
|---|---|
| Chain size | ≈ 270 GB |
| Growth per year | ≈ 35 GB / year |
| Recommended RAM | 4–8 GB |
| Recommended storage | 400 GB+ NVMe |
| Initial sync | 12–48 h |
| Prunable | ✓ (~⅓ of full size) |
| P2P port | 18080 P2P · 18081 RPC |
Every plan ships with unlimited bandwidth, NVMe storage and full root access — the three things a node actually consumes. Deploy with a token, pay in the same coin your node secures.
Pruned node (~100 GB) with fast sync — a personal wallet backend at pocket price.
Full chain on 1 TB NVMe with years of growth headroom, 64 GB RAM, room for a public restricted-RPC service.
Bare metal for the maximalist: full node + p2pool + Tor broadcast on ECC hardware, with your Bitcoin node next door.
| Location | CPU | RAM | Storage | Uplink | Price | |
|---|---|---|---|---|---|---|
| Moldova Budget Offshore | 16 vCPU AMD EPYC 9124 |
64 GB DDR5 | 1 TB NVMe | 2 Gbps | $44.00/mo | Order |
| Russia Western-Proof | 16 vCPU AMD EPYC 9124 |
64 GB DDR5 | 1 TB NVMe | 2 Gbps | $44.00/mo | Order |
| Panama No Data Retention | 16 vCPU AMD EPYC 9254 |
64 GB DDR5 | 1 TB NVMe | 2 Gbps | $49.00/mo | Order |
| Romania Anti-Retention | 16 vCPU AMD EPYC 9254 |
64 GB DDR5 | 1 TB NVMe | 2 Gbps | $49.00/mo | Order |
| Netherlands Best Peering | 16 vCPU AMD EPYC 9354 |
64 GB DDR5 | 1 TB NVMe | 2 Gbps | $54.00/mo | Order |
| Iceland Free Speech Haven | 16 vCPU AMD EPYC 9454 |
64 GB DDR5 | 1 TB NVMe | 2 Gbps | $58.50/mo | Order |
| Switzerland Premium Privacy | 16 vCPU AMD EPYC 9474F (3.6 GHz) |
64 GB DDR5 | 1 TB NVMe | 2 Gbps | $58.50/mo | Order |
Need more disk, RAM or a custom RAID layout for your node? Contact →
From order to synced node. Commands are copy-paste ready for Ubuntu 24.04 — adapt paths if you run Debian or Rocky.
VPS-PRO in Switzerland or Iceland fits Monero's ethos; Moldova keeps it cheapest.
Key-only SSH, firewall open on 18080 (P2P) and optionally 18089 (restricted RPC), install Tor for the transaction proxy.
apt update && apt install -y tor
systemctl enable --now tor
Download the CLI bundle from getmonero.org, verify the signed hashes, install monerod.
wget https://downloads.getmonero.org/cli/linux64 -O monero.tar.bz2
tar xjf monero.tar.bz2 && install -m 0755 monero-x86_64-linux-gnu-*/monerod /usr/local/bin/
Bind the restricted RPC, route transaction broadcast through Tor with tx-proxy, optionally enable pruning. Start detached and let it sync (12–48 h).
# ~/.bitmonero/bitmonero.conf
p2p-bind-ip=0.0.0.0
rpc-restricted-bind-ip=0.0.0.0
rpc-restricted-bind-port=18089
tx-proxy=tor,127.0.0.1:9050,10 # broadcast txs over Tor
Feather, Monerujo (over Tor), Cake or the GUI: set your node — preferably its onion address — as the remote node and refresh privately from then on.
monerod --detach
monerod status
In mid-2026 the raw blockchain is ~270 GB and grows ~35 GB a year; pruning cuts storage to roughly a third while keeping full validation. RAM: monerod is comfortable at 4–8 GB. CPU barely matters after sync. What matters is disk latency (the LMDB database loves NVMe) and honest bandwidth: a public remote node serving mobile wallets pushes hundreds of GB monthly, which is why unmetered matters even for the smallest node on this site.
Firewalled to your own IPs (or Tor-only), the node is a pure personal backend: nobody knows it exists. Open the restricted RPC on 18089 and you're providing a public good — strangers' wallets refresh against you, seeing only what the restricted API allows. Both modes run on the same server; the difference is one firewall rule. If you serve the public, Iceland and Switzerland put your node under privacy-respecting law.
The tx-proxy flag sends your outgoing transactions through Tor or I2P, so the origin IP of a broadcast can't be tied to your server — let alone to you. Inbound, an onion service lets your mobile wallet reach the node without touching clearnet. Combined with an anonymously rented server there is no name anywhere in the chain: token → XMR payment → datacenter IP → Tor circuit.
A node is the prerequisite for p2pool — decentralized mining without trusting a pool operator. The spare cores on VPS-PRO or DS-1 run the p2pool software comfortably (real hashrate comes from your miners elsewhere). Plenty of operators run node + p2pool and pay the hosting from mining income — in XMR, on an XMR-paid server. Full circle.
About 270 GB unpruned in mid-2026, growing ~35 GB a year. A pruned node holds ~100 GB. Both validate fully — pruning only drops old data that other nodes can serve.
Pruned for a personal wallet backend — identical security for you. Full if you want to serve historical blocks or run analysis. VPS-L handles pruned; VPS-PRO takes the full chain with headroom.
Yes — Monerujo and Cake accept custom remote nodes, ideally your node's onion address (Monerujo pairs with Orbot natively). Refreshes stop leaking your IP to random public nodes.
Yes, in all our jurisdictions: a node relays a public network's data and holds no customer funds. Privacy coins face exchange delistings, not node prohibitions.
If you have the bandwidth (we do), it strengthens the ecosystem — the restricted RPC is designed for exactly that exposure. Rate-limit with the built-in flags, keep the unrestricted RPC on localhost, and the risk is minimal.
Run the p2pool node here and point external miners at it. CPU mining itself is rarely profitable on rented hardware, and on shared VPS tiers we care about neighbours — on dedicated tiers, your cores are yours to spend.
Related reading: Crypto Payments for Hosting: Monero vs Bitcoin vs USDT · The First Hour of VPS Hardening: A Checklist · Crypto nodes
Your node, reachable over Tor, on hardware rented with a token and paid in XMR. From order to private refreshes in a day.