How to Run a Solana Validator Node: Hardware vs. Cloud (2026)

Solana is the most hardware-intensive proof-of-stake chain to validate. 

While other networks tolerate modest servers, Solana’s sustained throughput demands, compounded by Firedancer’s tile-based architecture, which went live on mainnet in 2025, have raised the performance bar considerably. 

Most setup guides circulating in 2024 are now outdated, hence the need for a new guide, which is available below.

What Has Changed for Solana in 2026

Three developments have reshaped the hardware landscape as we enter 2026.

• Firedancer is live on mainnet, and its tile-based, NUMA-optimized architecture extracts significantly more performance from high-core-count CPUs and XDP-capable NICs than Agave ever did.
• SIMD-0256 has raised compute-unit limits to 60 million+ per block, increasing sustained CPU and I/O pressure.
• Note that SIMD-0286 might raise the CPU limits up to 100 million per block.
• NVMe Gen5 drives are now price-competitive with Gen4, making the upgrade calculus straightforward for new builds.

Everstake operates active validators across 35+ networks with 99.98% uptime. The specifications in this article reflect the hardware configurations that power our Solana mainnet validators.

Solana Validator Types: What You’re Actually Running

A production Solana mainnet validator in 2026 is one of two distinct node types, and the distinction has major hardware implications.

A consensus validator votes on blocks and earns inflation rewards plus MEV revenue via Jito-Solana. Missed votes translate directly into lost rewards, and vote latency is the primary performance metric, which requires the highest-tier hardware.

An RPC node serves API requests to wallets and decentralized applications. It does not vote or earn staking rewards; revenue comes from API access fees. RPC nodes require less CPU headroom but demand massive storage (10+ TB for full archive) and high memory bandwidth for query concurrency.

Critical rule: never run RPC and validator workloads on the same machine. RPC query loads interfere with time-sensitive consensus operations.

The 2026 client landscape has three active options:

• Agave (Rust, developed by Anza Labs): the stable, widely deployed default.
• Firedancer (C/C++, developed by Jump Crypto): the high-performance client, now carrying approximately 14% of mainnet stake.
• Jito-Solana (Agave fork with MEV): favored by validators optimizing for block engine revenue.

2026 Solana Hardware Requirements: The Full Spec Sheet

A production Solana mainnet validator in 2026 requires a minimum 24-core CPU at 3.5+ GHz, 384–512 GB ECC RAM, enterprise NVMe Gen4+ storage, and 10 Gbps symmetric networking. Each component is examined below.

CPU

The minimum viable spec is a 12-core/24-thread processor at 2.8 GHz; anything below this will struggle to meet vote deadlines. The recommended baseline for mainnet is 24+ cores at 3.5+ GHz.

AMD EPYC dominates the Solana HCL, namely, the EPYC 9354 and 9355 are the most widely deployed families. Threadripper PRO offers a competitive alternative for operators not running dual-socket configurations. Intel Xeon is viable, but AMD’s memory bandwidth and core density at comparable price points have made it the operator’s default.

Both single-thread clock speed and aggregate core count matter: high single-thread performance reduces vote latency, while Firedancer’s tile-based parallelism rewards total core count.

RAM

256 GB ECC DDR4 is the floor for consensus validators. The recommended configuration is 384–512 GB ECC DDR5. RPC nodes serving high-concurrency workloads should target 512 GB to 1 TB.

ECC (Error-Correcting Code) memory is non-negotiable. A single uncorrected memory error can corrupt the accounts database, causing missed votes or a full node restart. Mounting the accounts database as a RAMDISK delivers measurable latency improvements by eliminating NVMe seek overhead on the most frequently accessed data structure.

Storage

Consumer NVMe drives are disqualified for use as mainnet validators. The WD SN850 and Samsung 980 Pro, while excellent for desktop workloads, degrade under Solana’s sustained sequential and random write load, causing node stalls within days of deployment.

The minimum enterprise-grade spec is 2×2 TB NVMe Gen4. The recommended configuration uses 2×3.84 TB drives from the Micron 7450/7500 or Samsung PM9A3 families. Accounts and ledger must be mounted on physically separate drives. High TBW (Total Bytes Written) endurance ratings and 300K+ read IOPS are required.

For Firedancer-optimized builds, NVMe Gen5 (Micron 7500) is now cost-competitive and provides meaningful headroom for SIMD-0256’s increased compute-unit throughput.

Networking

1 Gbps connectivity is technically functional, but operators report that validators consistently struggle to maintain vote latency under burst conditions. 10 Gbps symmetric is the standard for competitive mainnet operation.

Dedicated public IP (no NAT) is mandatory, since Solana’s UDP-based gossip and QUIC transport layers do not tolerate NAT reliably. Solana networking is egress-heavy; cloud deployments face $900–1,200/month in egress fees alone. Low-latency peering with the Solana cluster entry points is critical for vote submission.

Firedancer validators benefit from DoubleZero, a low-latency overlay network that reduces geographic latency penalties between validators.

OS and System Tuning

Ubuntu 22.04 LTS or 24.04 LTS is the operator standard. Key tuning steps include pinning threads to specific CPU cores using taskset/numactl, setting the I/O scheduler to none or mq-deadline for NVMe devices, enabling hugepages for large memory operations, and monitoring NVMe thermal throttling under sustained load.

Hardware Benchmark Table

Component	Minimum	Recommended	Firedancer-Optimized
CPU	12-core/24-thread, 2.8 GHz	24+ cores, 3.5+ GHz (EPYC 9354)	32+ cores, 3.8+ GHz (EPYC 9355 / Threadripper PRO)
RAM	256 GB ECC DDR4	384–512 GB ECC DDR5	512 GB ECC DDR5 + RAMDISK for accounts
Storage (accounts)	1×2 TB NVMe Gen4	1×3.84 TB enterprise NVMe (Micron 7450)	1×3.84 TB NVMe Gen5 (Micron 7500)
Storage (ledger)	1×1 TB NVMe Gen4	1×3.84 TB enterprise NVMe	1×3.84 TB NVMe Gen5
Network	1 Gbps symmetric	10 Gbps symmetric	10 Gbps + DoubleZero low-latency overlay
Est. bare metal cost	$400–600/mo	$800–1,200/mo	$1,200–1,800/mo

Firedancer: What Changes for Hardware

Firedancer is not simply a faster Agave. It is a ground-up rewrite in C/C++ with a fundamentally different execution model: one that has specific and significant hardware implications.

Tile-Based Architecture

Firedancer decomposes validator operations into discrete “tiles,” each pinned to a dedicated CPU core: network I/O, transaction verification, block production, and other functions run fully in parallel with no shared-memory contention. This architecture scales nearly linearly with core count and is highly sensitive to NUMA topology, i.e., memory latency between a tile’s core and its assigned memory zone directly affects throughput.

The practical implication: Firedancer rewards investment in high-core-count CPUs (32+ recommended) and NUMA-aware memory configuration (512 GB DDR5) more directly than Agave does.

Custom XDP Networking

Firedancer bypasses the Linux kernel networking stack entirely using XDP (eXpress Data Path), allowing a single core to handle 5.8 Gbps / 1.4 million TPS in published benchmarks. This requires a 10 Gbps NIC and a network driver that supports XDP. Most enterprise NICs (Mellanox/NVIDIA ConnectX, Intel E810) meet this requirement.

Performance Data (2025–2026)

Operator data from the 2025–2026 deployment period shows that Firedancer validators achieved +18–28 basis points of improvement in Skip Rate Reduction (SRR), 15% fewer missed voting credits, a vote latency of approximately 1.002 slots, and fuller blocks (averaging 47M versus 44.8M compute units under Agave). The storage requirements between Agave and Firedancer remain similar: enterprise NVMe endurance and IOPS requirements are driven by Solana’s ledger and accounts workload, which is client-agnostic.

Bare Metal vs. Cloud vs. Colocation

Infrastructure choice is the second-largest cost variable after vote transaction fees and directly impacts validator competitiveness.

Bare Metal (Dedicated Servers)

Bare metal is the standard choice for mainnet validators. Direct-attached NVMe eliminates virtualization overhead, there are no noisy-neighbor IOPS limits, and monthly costs run $800–1,200 for a well-specified server. The leading providers for Solana workloads include Cherry Servers, Hivelocity, Latitude, and Teraswitch, all of which explicitly permit cryptocurrency validator workloads in their ToS.

Cloud (AWS, GCP, Azure)

Cloud is convenient and appropriate for specific use cases such as testnets, RPC nodes, and temporary scaling, but is not competitive for mainnet validators. The primary problems: 

• Egress fees add $900–1,200/month on top of instance costs
• Provisioned IOPS on cloud storage (even at 16K IOPS) is routinely insufficient for validator workloads
• vCPU performance is variable under noisy-neighbor conditions 

The Agave documentation states explicitly that “running in the cloud requires significantly greater operational expertise to achieve stability.”

Colocation

Colocation offers the highest degree of hardware control: you own the physical servers, and the data center provides power, cooling, and network uplinks. Monthly rack and power costs run $300–500, but the upfront hardware investment is $20,000–50,000. This model is best suited to large-stake validators with multi-year operational commitments and in-house hardware management capability.

Provider Warning

Hetzner explicitly prohibits cryptocurrency workloads in its Terms of Service. Large-scale validator terminations have occurred without prior warning. Always audit the ToS of any hosting provider before deploying a validator, as this risk is non-trivial.

Cost Comparison Table

The numbers reflected in this table are approximate and may be time-dependent and flexible.

Cost Dimension	Bare Metal	Cloud (AWS/GCP)	Colocation
Monthly server/instance	$800–1,200	$1,500–3,000+	$300–500 (rack + power)
Egress/bandwidth	Included or ~$50–100	$900–1,200/mo	Included
Vote transaction fees	~$5,000/mo (~1.1 SOL/day)	Same	Same
Hardware CapEx	None (rental)	None	$20,000–50,000 upfront
Annual TCO estimate	$69,000–85,000	$110,000–180,000+	$65,000–90,000
Best for	Most mainnet validators	Testnets, RPC, scaling bursts	Large-stake, long-term operators

Note that vote transaction fees (~$60K/year at current SOL prices) are the largest single cost category regardless of hosting model.

Step-by-Step: From Hardware to Live Validator

The following checklist covers the provisioning sequence for a new mainnet consensus validator. The list is merely an operational overview, so please refer to docs.solanalabs.com and docs.anza.xyz for detailed CLI commands and configuration flags.

• Provision server. Verify: CPU supports the AVX2 instruction set, NVMe drives are correctly allocated (separate accounts and ledger volumes), a 10 Gbps NIC is present, and a dedicated public IP is assigned.
• Install Ubuntu 22.04 or 24.04. Apply system tuning: disable swap, enable hugepages, set the NVMe I/O scheduler to none/mq-deadline, and configure NUMA pinning.
• Install Solana CLI. Choose your client: Agave for stability, Firedancer for performance, Jito-Solana for MEV revenue optimization.
• Generate validator identity keypair. Fund the vote account (0.027 SOL for rent-exemption plus approximately 1.1 SOL/day for ongoing vote transaction fees).
• Configure startup flags: specify the ledger path, the accounts path, known validators for snapshot sync, the expected-genesis-hash, and the RPC port settings.
• Set up monitoring: Solana CLI metrics endpoint, Grafana dashboards for skip rate and vote credits, alerts for delinquency and missed votes.
• Stake delegation: bootstrap with self-stake or apply to the Solana Foundation Delegation Program (SFDP) to establish initial stake weight.

Everstake – A Reliable Solana Node Validator

Everstake offers a fully managed Solana validator-as-a-service (Vaas) option for teams that want mainnet exposure without the operational overhead of bare-metal provisioning, NUMA tuning, and 24/7 skip-rate monitoring. The service runs on the same AMD EPYC, 512 GB ECC DDR5, enterprise NVMe Gen4+ infrastructure documented in this guide, with Jito-Solana and Firedancer client support, backed by SOC 2 Type II and ISO 27001 certification and Everstake’s 99.98% uptime record across its Solana mainnet operations.

We are also offering SWQoS Solana RPC Access and Shredstream products as a part of our Solana stack. 

FAQ

Question	Answer
What hardware do I need for a Solana validator in 2026?	24+ core CPU at 3.5+ GHz (AMD EPYC recommended), 384–512 GB ECC RAM, 2×3.84 TB enterprise NVMe Gen4+, and 10 Gbps symmetric networking. For Firedancer, add 32+ cores and DDR5.
Is cloud or bare metal better for Solana validators?	Bare metal. Cloud adds $900+/mo in egress costs, virtual storage bottlenecks, and performance variability. The Agave docs note that cloud deployments require “significantly greater operational expertise to achieve stability.”
Does Firedancer need different hardware than Agave?	Firedancer benefits from more cores (32+) and 10 Gbps NICs due to its tile-based parallelism. RAM and storage requirements are similar — enterprise NVMe and 512 GB ECC DDR5 remain the standard.
How much does it cost to run a Solana validator?	$69K–$180K/year depending on hosting model. Vote transaction fees (~$60K/year at current SOL prices) are the largest single expense regardless of infrastructure choice.
Can I run a Solana validator on Hetzner?	No. Hetzner prohibits cryptocurrency workloads and has terminated validators en masse. Use vetted providers such as Latitude, Hivelocity, Cherry Servers, or Teraswitch instead.
What NVMe drives work best for Solana validators?	Enterprise-grade only: Micron 7450/7500 or Samsung PM9A3. Consumer SSDs (WD SN850, Samsung 980 Pro) degrade under Solana’s sustained write load, leading to node stalls.
How does Everstake run Solana validators?	Dedicated bare metal, AMD EPYC CPUs, 512 GB ECC DDR5, enterprise NVMe Gen4+, and 10 Gbps networking. Infrastructure is SOC 2 Type II and ISO 27001 certified, with 99.98% uptime across 40,000+ validators.
What is the Solana Hardware Compatibility List?	solanahcl.org is a community-maintained registry of tested CPU, storage, and datacenter configurations verified for Agave, Frankendancer, and Firedancer validators.