Solana's 400 ms slots and parallel runtime turn every node into a small supercomputer: the accounts database hammers NVMe continuously, snapshots arrive at multi-gigabit speed, and RAM below 256 GB means falling behind the cluster. Most VPS offerings aren't in the conversation. This page maps Solana's official requirements onto bare metal that actually meets them — and onto a testnet tier for learning the ropes without burning validator money.
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.
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.
From order to synced node. Commands are copy-paste ready for Ubuntu 24.04 — adapt paths if you run Debian or Rocky.
Netherlands for peering density, or Iceland for clean cheap power under an indifferent jurisdiction.
Mount ledger and accounts on separate NVMe drives, raise file-descriptor limits, set the CPU governor to performance.
One installer script pins the current release; verify it and add the binaries to PATH.
sh -c "$(curl -sSfL https://release.anza.xyz/stable/install)"
export PATH="/root/.local/share/solana/install/active_release/bin:$PATH"Pull the latest snapshot from known validators and start agave-validator in RPC mode — or with your vote account if you're joining consensus.
# mount ledger and accounts on separate NVMe drives
agave-validator \
--ledger /mnt/ledger --accounts /mnt/accounts \
--limit-ledger-size 50000000 \
--only-known-rpc --no-voting # RPC modesolana catchup confirms you're at the head; wire the monitor output into your alerting. Validators: fund the vote account and watch your credits.
solana catchup --our-localhost
agave-validator --ledger /mnt/ledger monitorThe published minimums for a voting validator: 24+ high-clock cores, 256 GB RAM, separate NVMe for ledger and accounts, 1 Gbps minimum bandwidth with 10 recommended. RPC nodes servicing real traffic want 512 GB to 1 TB RAM and even more NVMe. The rolling ledger self-prunes (--limit-ledger-size), so disk is about IOPS and parallelism more than raw capacity — four independent NVMe devices beat one big one every time.
A validator earns inflation commission and priority-fee share on the stake it attracts — and pays roughly 1 SOL per day in vote fees regardless. Break-even therefore depends on attracting delegation, not on hardware alone. What hardware does control is skip rate: a DS-4 at spec with 10 Gbps keeps your produced-block rate competitive, so the stake you attract compounds instead of leaking. Start on testnet with the Starter tier, prove your operations, then commit.
Public Solana RPCs are rate-limited to uselessness for bots, indexers and serious dapps. A private RPC node — no voting, known peers only, full account index if you need it — answers getProgramAccounts without quotas and keeps your query patterns (your strategy) off shared infrastructure. For trading workloads, pair it with our Netherlands location for the lowest ping to the major peering hubs.
Agave releases land frequently: follow the release feed and restart in your low-traffic window — restarts resume from local state in minutes. Watch disk wear: the accounts NVMe takes sustained writes, and we swap drives proactively on SMART signals. Snapshots make disaster recovery boring — any fresh DS-4 is back at the cluster head in hours. Keep identity and vote keys backed up off-box; they are the only unrecoverable part.
Related reading: VPS vs Dedicated Server for Privacy-Critical Workloads · The First Hour of VPS Hardening: A Checklist · Crypto nodes
Bitcoin Node Hosting
Ethereum Node Hosting
Monero Node Hosting
Litecoin Node Hosting
TRON Node Hosting