01
NVMe-class IOPS
Ethereum state DB hammers random reads. Cloud SSDs throttle. Our NVMe arrays sustain hundreds of thousands of IOPS — Erigon archive syncs finish in days, not weeks.
BLOCKCHAIN COMPUTE / ETHEREUM
Ethereum nodes that don't fall behind the head.
Geth, Nethermind, Erigon, Lighthouse, Prysm — pick your stack. Our dedicated NVMe arrays deliver the IOPS the state database actually needs, and the 3–10 Gbps lines keep you in sync through every epoch boundary.
BAREMETALSERVER.AI · 42U
01
BMS-01
AMD RYZEN 9950X
02
BMS-02
AMD EPYC 9354P
03
BMS-03
2x EPYC 7443
04
BMS-04
THREADRIPPER 7965WX
What is an Ethereum full node?
An Ethereum full node is a server that independently verifies every transaction and block on the Ethereum network by running both an execution client (Geth, Nethermind, Erigon, Reth, or Besu) and a consensus client (Lighthouse, Prysm, Teku, Nimbus, or Lodestar) since The Merge in 2022. The execution layer maintains the complete state trie, processes EVM transactions, and serves JSON-RPC queries; the consensus layer participates in Proof-of-Stake attestations and tracks the beacon chain. As of 2026, an archive node requires 16+ TB of NVMe storage with sustained random-read IOPS above 100,000 to keep up with the state database. A pruned full node still needs 1.5–2 TB of fast NVMe, 32 GB+ of RAM, and a stable 25 Mbps connection. Cloud-attached block storage cannot meet the IOPS budget — bare metal NVMe is the only economical way to run a synced node without lag during epoch boundaries.
GethNethermindErigonRethLighthousePrysmEVMBeacon ChainJSON-RPCEIP-4844
Jump to pricing Where IOPS matter more than core count.
02
Validator-grade uptime
Bare metal means no noisy neighbor steals your CPU during the attestation slot. Consistent performance is the whole game when slashing penalties exist.
03
Run any client
Full root access. Run Geth + Lighthouse, Erigon + Prysm, Nethermind + Teku, or your own custom build. We don't care which client wins the diversity wars.
Snap sync in 6 hours. Archive sync in 2 days. Hypervisors don't get to slow you down.
What Ethereum clients ask for.
Full node RAM
32–64 GB
Archive RAM
128+ GB
Storage
2–8 TB NVMe
Network
3–10 Gbps
Recommended hardware
All 29+ servers → Ethereum-ready hardware in stock.
Filtered to plans with 64GB+ RAM, sorted from validator-class to archive-class.
Server
CPU
RAM
Storage
Network
From
AMD EPYC 9124P
amd-epyc-9124p
16 cores
64 GB
2x NVMe 1TB
10Gbps
$711/mo
AMD Ryzen 9900X
amd-ryzen-9900x
12 cores
96 GB
2x NVMe 1TB
10Gbps
$449/mo
AMD Ryzen 9700X
amd-ryzen-9700x
8 cores
96 GB
2x NVMe 1TB
10Gbps
$449/mo
AMD Ryzen 7950X
amd-ryzen-7950x
16 cores
128 GB
2x NVMe 1TB
3Gbps
$449/mo
2x E5-2620v4
2x-e5-2620v4
16 cores
128 GB
2x SSD 250GB
3Gbps
$768/mo
2x E5-2630v3
2x-e5-2630v3
16 cores
128 GB
2x SSD 250GB
3Gbps
$878/mo
2x E5-2650v4
2x-e5-2650v4
24 cores
128 GB
2x SSD 250GB
3Gbps
$1032/mo
2x E5-2670v3
2x-e5-2670v3
24 cores
128 GB
2x SSD 250GB
3Gbps
$1164/mo
Answers before you ask.
What are the hardware requirements for an Ethereum full node?
An Ethereum full node needs at least 16GB RAM (we recommend 64GB+), 2TB of fast NVMe storage, and a stable 25Mbps+ link. Our 64–128GB plans exceed these with NVMe and dedicated 3–10 Gbps networking.
How much storage does an Ethereum archive node need?
An archive node currently needs 4TB+ of NVMe and growing. Our 128GB+ plans pair high RAM with multi-NVMe arrays. NVMe IOPS matters more than raw capacity for state database performance.
Can I run an Ethereum validator on bare metal?
Yes. Validators need 32GB+ RAM, 2TB SSD, and minimal downtime. Bare metal gives you consistent performance without hypervisor overhead — critical for avoiding slashing penalties. Servers deploy in 5–20 minutes.
Which Ethereum clients do you support?
You get full root access, so you can run any execution client (Geth, Nethermind, Besu, Erigon) and consensus client (Prysm, Lighthouse, Teku, Nimbus, Lodestar). Zero software restrictions.
How fast can I sync an Ethereum full node?
With NVMe storage and 3–10 Gbps dedicated networking, snap sync typically takes 6–12 hours. Erigon archive sync takes 2–3 days. Cloud instances with slower IOPS can take 2–5x longer.
Can I pay for Ethereum infrastructure with crypto?
Yes — USDT, USDC, BTC, and other major cryptocurrencies. No KYC theatre. Crypto-native infrastructure for crypto-native teams.
Ethereum node hosting compared
The four common ways to host an Ethereum execution + consensus node side by side. Pricing is indicative starting cost — vendor pricing changes; verify on the vendor site.
| Provider | Storage profile | Crypto payment | Deploy time | Root SSH | Starts at |
|---|---|---|---|---|---|
| BareMetalServer.ai | Dedicated NVMe arrays, 64–768 GB RAM | USDT, USDC, BTC | 5–20 min | Yes (full root) | $449/mo |
| Hetzner | Dedicated NVMe SSDs, up to 256 GB RAM | No (card / SEPA only) | ~minutes (auction); hours (managed) | Yes (full root) | ~€44–500/mo |
| OVHcloud | Dedicated NVMe / SSD, Advance/Rise lines | No (card / SEPA only) | 1–3 hours typical | Yes (full root) | ~€60–600/mo |
| AWS i4i (cloud) | Virtualized w/ NVMe instance store | No | Seconds | Yes (root in VM) | ~$1,700–4,500/mo |
Indicative monthly starting prices as of Q1 2026. Cloud pricing excludes egress and EBS charges, which dominate Ethereum RPC bills. Bare metal NVMe arrays sustain hundreds of thousands of random-read IOPS — the IOPS budget Erigon archive sync actually consumes.
Ready when you are
Stake, sync, serve — on metal that earns its slot.
Deploy in 5–20 minutes. Pay in USDC. Run any client. Full root access from minute one.
See recommended hardware