Dedicated nodes
A machine that is yours alone, running the client you choose, in a city we already measure from. Real specs, prices on the page, and no rate limit — because there is nobody to share it with.
Every provider’s dedicated-node page publishes latency figures nobody outside the company can check, and replaces the price with “contact sales”. We are the site that measures the whole market, so we are the one provider that cannot get away with that.
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.
In the last 24 hours this site took 612,568 measurements of public RPC endpoints across 3 chains, from 4 regions, covering 12 providers and 28 methods. The method is published in full, the rankings are open to anyone, and they include providers who would rather they did not.
Your dedicated node is measured by the same probes, from the same cities, the same way. That is not a feature we added to a hosting product — it is the thing this company already does, pointed at your machine.
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.
