NulNetBest VPS for a Monero Node in 2026 — Sizing for monerod
monerod wants NVMe, RAM and P2P 18080 open. Ranger $12.50 prunes comfortably; a 1 TB Storage SKU holds the archive. XMR billing, restricted RPC, no KYC.
Size the node to the chain: Ranger ($12.50) fits a pruned monerod, Warden ($19.00) or a 1 TB Storage SKU holds the archive — P2P 18080 open, RPC restricted, the invoice paid in XMR.
21 locations · 16 coins · SLA 99.95% · no KYC · public canary
VPS from $3* (fund $50+), storage 1–5 TB NVMe from $24/mo annual-eff, dedicated with IPMI from $30.80/mo. Crypto invoice, no KYC.
Launch nowWhat monerod actually needs
| Mode | Disk | RAM | NulNet fit |
|---|---|---|---|
| Pruned (~2/3) | ~70 GB | 4–8 GB | Ranger $12.50 (120 GB NVMe) |
| Full node | ~200 GB and growing | 8–16 GB | Warden $19.00 / Depot 1 TB $30 |
| Node + wallet RPC | same + wallet | 16 GB comfy | Warden |
Ports: 18080 P2P (open), 18089 restricted RPC if you serve others. A from-scratch sync on NVMe finishes in hours; pruning keeps the box permanently small.
Host ranking for Monero nodes
| # | Host | Why | KYC |
|---|---|---|---|
| 1 | NulNet | XMR-native billing, NVMe, unmetered, node-friendly AUP | None |
| 2 | NovaVPS | XMR on a 16-coin invoice; NVMe, unmetered ports; brand new in 2026 | None |
| 3 | Privex | Crypto-native culture | None |
| 4 | FlokiNET | Privacy posture, 4 locations | None |
| 5 | 1984 Hosting | Iceland, small specs | None |
Privacy note worth stating
Running a public Monero node serves the community — the network’s decentralization grows with it. Put that node on an XMR-paid, no-KYC VPS and its existence stays unlinked from its operator: precisely the property Monero was built to protect.
monerod sizing and peer ports
monerod wants steady disk and open P2P (TCP 18080). Ranger ($12.50) suits pruned or lighter roles; Warden ($19.00) runs a longer-lived public node comfortably. Reykjavik pairs naturally with XMR-paid infrastructure; any of the twenty-one flags works technically. Install from the official getmonero downloads; never run random third-party binaries.
Paying the VPS in Monero while operating monerod is consistent opsec — but the node's public IP stays public. Bind RPC in restricted mode. Unrestricted RPC never faces the world. A remote node assists wallets; it replaces no wallet-side hygiene.
Snapshots before upgrades. Unmetered ports ease the initial sync. Storage SKUs help when large chaindata lives beside other datasets.
Bind RPC to localhost or a WireGuard interface. Take official binaries and verify hashes. Leave free disk for chain growth. Warden at $19.00 is the calm public-node tier; Ranger covers personal remote-node duty. Pair Reykjavik with XMR billing for narrative consistency, though all twenty-one locations run monerod — choose for latency to your wallet users, not folklore alone.
Operational footnote: official binaries, restricted RPC, Ranger or Warden sizing, XMR to settle the VPS bill, 18080 open for peers. A remote node assists wallets; wallet hygiene still decides spend privacy. Snapshots before upgrades rescue weekends.
Final note: official monerod, restricted RPC, Ranger or Warden, 18080 open, XMR for the VPS bill, Reykjavik optional for narrative fit. Remote nodes assist wallets; spends still rest on wallet hygiene. Snapshots before upgrades.
Bind RPC privately. Verify downloads. Keep free disk for growth. Public node IPs are public — plan on that.
Closing: official monerod with restricted RPC, Ranger or Warden sizing, peers on 18080, XMR covering the VPS bill, snapshots before upgrades. Remote nodes assist wallets; spends still demand wallet hygiene.
Verify binaries, leave free disk, treat public node IPs as public.
Extra: check disk growth monthly, keep RPC private, and verify upgrades against getmonero.org guidance. Ranger or Warden with an XMR-paid VPS aligns node operations with payment-privacy goals without conflating the two.
Also: run a second pruned node elsewhere when uptime matters, and never expose unrestricted RPC beyond WireGuard.
Keep peer counts healthy and refuse random third-party monerod builds.
Node limits
Your spends still require a correct wallet. A node is infrastructure — never a mixer.
RPC binding and binary discipline for monerod
Install strictly from official getmonero downloads. Keep RPC bound to localhost or WireGuard and open 18080 for peer traffic; Ranger ($12.50) covers personal remote-node duty, Warden ($19.00) buys a calmer public node. Settle the VPS in XMR for narrative consistency; the node IP stays public regardless. Verify hashes, leave free disk for growth, snapshot ahead of upgrades. A remote node assists wallets - it is no mixer.
Pruned monerod sizing in the field
A pruned chain (~2/3 kept) sits comfortably on Ranger ($12.50, 120 GB NVMe, 8 GB ECC); full archival belongs on Warden or Depot 1. Open 18080 for P2P; keep restricted RPC on WireGuard. Paying the VPS in XMR matches the network’s privacy posture. Bucharest or Zurich for the facility story; the same SKN invoice either way.
Recommended setup
Plan: Ranger — 4 vCPU, 8 GB ECC, 120 GB NVMe, $12.50/mo, running pruned full-validation. Full archival → Depot 1 ($24/mo, 1 TB). Location: Bucharest — no mandatory retention, solid EU transit. Playbook: Monero node on NulNet.
Monero-node VPS from $12.50/mo — pay in XMR.
Launch nowMore rankings and guides
- Best Monero VPS 2026
- Best VPS for a Bitcoin node
- How to pay a VPS with Monero
- Best crypto-only VPS
- Best storage VPS 2026
- Best privacy jurisdictions 2026
Can wallets connect to my node?
Yes — publish restricted RPC on 18089 behind TLS, or keep it private and reach it over WireGuard; unrestricted RPC never faces the internet.
Does a node need a public IP?
For P2P yes — every NulNet server has a dedicated IPv4.
Pruned vs full for privacy?
Both verify fully; pruning only limits serving old chain data.
Is there an official guide?
Use the getmonero.org VPS node guide and downloads - linked wherever citations are set.
Is Sentry enough?
Tight for a busy public node; Ranger is the realistic minimum.
Primary sources
Ready to launch?
Build the box — VPS, storage or bare metal — create the password, pay the invoice that follows.