Dedicated nodes
A BSC node sized for a chain whose state has grown faster than the guidance for it. Snapshot restores rather than a sync measured in weeks, hard-fork tracking before the fork block, and an Erigon archive at roughly 6 TB rather than fifty.
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.
BSC produces blocks faster than most chains, so state writes are continuous. Hardware sized against a nominal minimum works until it does not, and the failure looks like random lag rather than a disk running out of headroom.
The published minimum has trailed reality for a while. Our plans are sized well above it, because a node that fills its disk in month seven is a migration you did not plan and did not price.
Which is why every plan here restores from a recent snapshot instead. A three-week sync is not a recovery plan.
Configured before handover unless it says otherwise. Where something is optional, the page says optional.
Restored from a recent snapshot rather than a sync measured in weeks — which is what a BSC full node from genesis actually costs in time.
We follow BNB Chain's release schedule and upgrade before the fork block, rather than after your node has stopped following the chain. This is the failure mode that actually bites BSC operators.
Full BSC history on Erigon is around 6 TB, against roughly 50 TB for a Geth archive. The tracing namespaces are enabled and unmetered.
Run it pruned to stay small or keep more history. It is your machine and your disk, and we do not impose a retention policy on it.
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 BNB Smart Chain full node, sized for a chain whose state grew by half in eighteen months.
$1,190.00
per month · $11,900.00 a year
New York · Frankfurt · Singapore
Order this node →Full BSC history on Erigon — around 6 TB, against roughly 50 TB for a Geth archive.
$3,690.00
per month · $36,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 a BNB Smart Chain client allocated to one customer, with no shared rate limit and no credit metering. You choose the client and the pruning policy.
Around 6 TB on Erigon. The same history on a Geth archive is roughly 50 TB, which is the difference between a plan and a rack.
We track BNB Chain's release schedule and upgrade before the fork block. Missing one means the node quietly stops following the canonical chain, which is the failure that catches most BSC operators out.
Hardware within hours of payment settling, then a snapshot restore rather than a sync from genesis — hours rather than the weeks a full sync would take.
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 Ethereum nodes