Dedicated nodes
Execution and consensus clients on one machine, both yours. Five execution clients and five consensus clients to choose from, an Erigon archive at roughly 3 TB rather than 20, and blob headroom sized for the chain as it is now.
We are not asking you to take our word for any of this. In the last 24 hours this site took 612,568 measurements of public endpoints across 3 chains from 4 regions, against a method we publish in full. Your node is measured by the same probes.
The reasons a shared endpoint disappoints on this chain specifically — and what a dedicated machine changes about each.
A Geth archive is roughly 18–20 TB. The same history on Erigon's flat state is around 2–3.5 TB. That single choice is the difference between an archive priced like a node and one priced like a rack — which is why our archive plans default to Erigon and say so rather than quietly charging you for the difference.
Post-Dencun, a full node retains blob sidecars for a rolling window. A machine sized for Ethereum as it was two years ago runs out of disk and starts falling over in a way that looks like a client bug. Our plans are sized for the chain as it is.
Running a validator against a shared execution endpoint means your attestations depend on a service you do not control and cannot see into. Every validator plan here includes a dedicated execution client on the same machine.
Configured before handover unless it says otherwise. Where something is optional, the page says optional.
Geth, Nethermind, Erigon, Reth or Besu on the execution side; Lighthouse, Teku, Nimbus, Prysm or Lodestar on consensus. Running a minority client makes the network more robust and costs you nothing here — ask and we will set one up.
On archive plans the tracing namespaces are on and uncounted. This is the reason most people want an archive node, and metering it would defeat the point.
Including none. Relay choice is a policy decision with censorship implications and we do not make it for you. Slashing-protection databases are backed up before any move, and we will not start a second instance of your keys.
Signing keys are loaded for the validator client; the withdrawal credentials stay with you. We cannot exit or drain your validator, which is a property of how it is set up rather than a promise about our conduct.
A dedicated node is chosen on what software runs on it. This is the part a shared endpoint cannot offer at all.
Per month, exclusive of tax. The machine each one runs on is named, so you can check the hardware is what we say it is.
A dedicated Ethereum full node — execution and consensus clients, both yours, with blob storage headroom.
$990.00
per month · $9,900.00 a year
New York · Dallas · Frankfurt · Amsterdam · Singapore
Order this node →Full historical state from genesis, on Erigon — which is what makes an archive node affordable rather than a 20 TB problem.
$1,390.00
per month · $13,900.00 a year
New York · Frankfurt
Order this node →Beacon node and validator client, operated for you. Keys stay yours; we never hold withdrawal credentials.
$890.00
per month · $8,900.00 a year
New York · Frankfurt
Order this node →Whichever chain you came for.
This site exists because we measure public RPC endpoints continuously and publish the method. Your dedicated node is measured by the same probes, from the same regions, the same way. Every other provider asks you to believe their latency figures; ours are produced by the apparatus we already point at their endpoints.
Requests to your node appear alongside your API-key traffic — volume, errors, p50 and p95, by endpoint. Not a separate dashboard bolted on, and no per-request charge behind it, because the node is yours and there is nothing to meter.
A private link between your machines, so an application never crosses the public internet to reach its own node. Put an indexer or a bot on an application server in the same rack and the hop is a cable.
It is your machine. Full root from the first minute, any operating system, and nothing of ours that has to stay installed. Monitoring is offered rather than imposed.
We place nodes in the cities our probes already run in, so the latency from that region is a figure we have been publishing rather than a number a datacentre sales page gave us. New York, Dallas, Frankfurt, Amsterdam, Singapore.
Every plan's price is published, along with the machine it runs on. The industry norm is “contact sales”, which exists so the number can vary by how much you look like you can pay.
A machine running your own execution and consensus clients, allocated to one customer. No shared rate limit, no credit metering, and you choose which clients run on it.
It depends entirely on the client. Erigon's flat state holds full history in roughly 2–3.5 TB; a Geth archive is roughly 18–20 TB of the same data. We default to Erigon on archive plans, which is why our archive pricing is close to our full-node pricing rather than several times it.
Yes, on archive plans, enabled and unmetered. They are the reason most people need an archive node.
Yes, on the same machine, on every Ethereum plan including archive. A node depending on somebody else's consensus layer is a node with somebody else's uptime.
Yes, and we would rather you did. Client diversity is a property the network needs and it costs you nothing here — say which one at order, or ask us after.
You hold the withdrawal credentials; we never do. Signing keys are loaded for the validator client so it can attest. We cannot exit or drain your validator.
Three reasons that are not marketing. There is no rate limit, because there is nobody to ration against. There is no noisy neighbour, so your p99 is your own workload rather than somebody else's. And you choose the client and the plugins, which on Solana and Ethereum changes what the node can do rather than only how fast it does it.
From what the machine costs us, published alongside what it is. We buy from Latitude, Terraswitch, CherryServers and 23m, and every plan names the provider SKU so you can check the hardware is what we say it is.
Yes — ETH, BNB or SOL, priced in dollars against an on-chain Chainlink feed. The invoice records the feed address and the round id, and the payment dialog publishes both, so the conversion can be checked against the chain rather than taken on trust.
The node keeps running until the end of the period you have already paid for, and the confirmation names the date. Nothing is destroyed early, and an unpaid invoice on a cancelled order is voided rather than left owing.
Not yet, and we are not going to invent one. This is a new product. What we do have is millions of measurements of public endpoints across three chains, taken continuously from four regions against a published method — and the same probes pointed at your node from day one. If that is not enough assurance for your workload, it should not be. Talk to us before you buy rather than after.
Prices are on the page and the specs are real. If your workload is unusual, say so before you buy rather than after — we would rather talk you out of the wrong machine than sell you one.
Dedicated Solana RPC nodes
Dedicated BNB Smart Chain nodes