Hardware Requirements

Hardware Requirements for Flux Nodes

Running a Flux node requires dedicated hardware that meets or exceeds the minimum specifications for your chosen tier. The Flux network enforces these requirements through periodic benchmarks that run every six hours, meaning your hardware must consistently perform — not just pass once at setup. This guide covers the exact specifications, recommended configurations, and practical considerations for each node tier.

Node Tiers and Minimum Specifications

Flux operates a three-tier node system. Each tier requires a different level of hardware and a corresponding collateral stake. Higher tiers contribute more compute to the network and earn proportionally higher rewards.

Recommended Specifications

Experienced node operators consistently recommend exceeding the minimums. The table below shows recommended specs that provide comfortable headroom for passing benchmarks reliably and maintaining eligibility for Progressive Node Rewards (PNR).

SSD vs NVMe Considerations

The Flux benchmark measures SSD write speed, and this is one of the most common causes of benchmark failure. Standard SATA SSDs can pass benchmarks but often provide inconsistent I/O performance, especially on shared VPS platforms where disk resources are oversubscribed. NVMe drives are strongly recommended because they deliver significantly higher and more consistent IOPS (Input/Output Operations Per Second), typically 3-5x faster sequential write speeds compared to SATA SSDs, and are less susceptible to I/O contention in shared environments.

CPU Requirements

Flux benchmarks measure CPU performance using an EPS (Events Per Second) metric. Server-grade processors such as AMD EPYC and Intel Xeon families are ideal because they deliver consistent performance under load and typically do not throttle. Consumer-grade CPUs (Intel Core i-series, AMD Ryzen) can work in bare-metal setups but may exhibit boosting and throttling behavior that leads to inconsistent benchmark scores. On VPS platforms, the underlying host CPU matters — providers using EPYC 7xx3 (Milan) or newer generally deliver the best EPS scores.

Bandwidth and Network Considerations

The bandwidth requirement refers to sustained throughput, not burst speed. Your server must maintain the required bandwidth consistently, as Flux nodes serve application data, sync blockchain data, and communicate with the network continuously. Benchmarks test both download and upload speeds. Be aware that many VPS providers advertise "1 Gbps" ports but throttle sustained throughput or impose monthly transfer caps. Ensure your provider offers unmetered or generously metered bandwidth at the required sustained rate.

IPv4 and Networking

Each Flux node requires a unique, dedicated public IPv4 address. You cannot run multiple Flux nodes behind the same IP address using different ports. If you plan to run multiple nodes, you need multiple servers or a server with multiple IPv4 addresses assigned. IPv6-only configurations are not supported — the node must be reachable on a public IPv4 address.

Recommended Hosting Providers

The Flux community has identified several hosting providers that consistently deliver reliable performance for node hosting. The right choice depends on your tier, budget, and geographic preferences.

• •Hetzner — Popular for European operators. Offers excellent hardware at competitive prices, with dedicated server options using AMD EPYC processors. Their auction servers provide outstanding value.
• •OVH / OVHcloud — Wide range of dedicated and VPS options across Europe, North America, and Asia-Pacific. Known for unmetered bandwidth on dedicated servers.
• •Contabo — Budget-friendly VPS and dedicated servers with generous RAM and storage allocations. Quality can vary by data center, so verify benchmark performance early.
• •Vultr — Cloud-based VPS with global data centers. "High Frequency" compute instances with NVMe storage work well for Cumulus and Nimbus tiers.

Dedicated vs Shared Hosting

For Cumulus nodes, well-provisioned VPS instances from reputable providers generally work fine. For Nimbus nodes, a VPS can work but you should select plans with dedicated CPU cores (not shared/burstable) and NVMe storage. For Stratus nodes, dedicated bare-metal servers are strongly recommended. The high resource requirements and the need for consistent benchmark performance make shared environments risky for Stratus operations.

ArcaneOS Compatibility

ArcaneOS is the custom Flux operating system that enables hardware attestation and is mandatory for Progressive Node Rewards (PNR). ArcaneOS requires a bare-metal server or a VPS that supports nested virtualization and custom ISO booting. Not all providers support ArcaneOS — verify compatibility before purchasing. Providers like Hetzner (dedicated servers) and certain OVH dedicated ranges support custom ISO installation, making them suitable for ArcaneOS deployment.