CryptoServers

Monero full node on offshore hardware

Run monerod with port 18080 open and serve as a public remote node — exactly what the network needs more of.

No KYC, ever DMCA ignored No traffic logs Live in 60 seconds
1 Tbps
DDoS absorption
41s
Median deploy
3
Recommended locations
$26.99
Entry plan / month
Built for the workload

Why Monero full node runs better here

Specific technical alignment, not generic copy. Each point below is something the workload needs and we provide by default.

Inbound 18080 / 18089 open. Public remote nodes welcomed — the network needs more.
~180 GB chain. Fits on Growth+ NVMe with room for a Tor and I2P companion.
I2P + Tor peering supported on the same daemon. anonymous_inbound config is standard.
AES-NI accelerates the RPC layer. ringsize/decoy lookups are the typical bottleneck.
No traffic shaping on the p2p wire. Default privacy-coin policy = leave it alone.
Workload notes

What you should know about Monero full node on Cryptoservers

Monero's chain is smaller than Bitcoin's (~180 GB) but the wallet-syncing load on a public remote node is heavier per query. If you're running a public remote node (which the network desperately needs more of), expect 5–20 GB/day of egress per 100 active wallets and CPU spikes during ringsize/decoy lookups. vps-growth handles a small public node; vps-business is the comfortable tier.

Monero supports I2P and Tor peering natively (anonymous_inbound). We allow both; you can run a clearnet+Tor+I2P node from the same box with no special routing. Inbound port 18080 (and 18089 for restricted RPC) are open by default; mark your node public via the daemon config and it shows up in the .onion directory automatically.

Plans

Plans sized for Monero full node

Pre-filtered by CPU, memory and bandwidth profile. Pick the cheapest that fits your projected load — you can hot-resize later without downtime.

Sysadmin FAQ

Monero full node — questions answered

Will you tolerate me running a public Monero node here?
Yes — that's an explicit use case we welcome. We don't throttle the daemon, don't cap connections, and don't inspect traffic. Public remote nodes are a net good for the network.
How much bandwidth does a popular public node use?
5–20 GB/day per 100 active wallet syncs, plus 1–3 TB/month for normal p2p block propagation. All our VPS uplinks are unmetered at advertised rates so this stays inside the plan.
Can I run monerod, a Tor instance, and an I2P router simultaneously?
Yes. monerod's anonymous_inbound config takes care of the wiring; you just need both Tor and I2P running locally. vps-growth has plenty of CPU for all three; vps-business is comfortable if you're also serving a public RPC.
Is Monero-specific in your chosen jurisdiction any different from Bitcoin?
Legally no — none of our four jurisdictions distinguishes Monero from Bitcoin. Operationally, the bandwidth pattern is different (more frequent small queries from wallets, less p2p block traffic). Pick by network reach to your users, not jurisdiction.
Will you cooperate with chain-analysis subpoenas about my node?
We don't store anything that would let us. We have no logs of which IPs queried your RPC, no record of wallet syncs, no list of accepted ringsize candidates — that data isn't generated, period. See /privacy/ for the full retention policy.

Monero full node — deploy in 60 seconds

No email, no ID, no account. Pick a plan, pay in crypto, get root.