Skip to content
Measured continuouslySolana rankings

Dedicated Solana RPC nodes that you can check

A Solana node that is yours alone — no shared rate limit, because there is nobody to share it with. Yellowstone gRPC configured before handover, your choice of Agave, Jito-Solana or Frankendancer, and the option to sit on DoubleZero rather than the public internet.

In the last 24 hours we took 580,831 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 evidence

What Solana's public endpoints actually do

Not a claim about our own hardware — we have not sold one yet, so we have no such figure and will not invent it. This is what our probes measured on the public Solana endpoints in the last day.

Fastest measured

53 ms

publicnode

Slowest measured

354 ms

solana-foundation

Spread

6.6×

between the two

  1. publicnode53 ms99.6%
  2. tatum89 ms99.6%
  3. solana-foundation354 ms99.8%

Median response and availability over 24h, across the public Solana endpoints we measure, from 3 providers. Taken by our own probes against a published method — the same figures behind the Solana rankings, not a number written for this page.

The problem

What makes Solana hard to run

The reasons a shared endpoint disappoints on this chain specifically, in the order they bite.

The accounts database is the bottleneck, not the CPU

Solana's accounts database is read on every transaction and it does not fit in a cache you can hand-wave. A node that keeps it in RAM answers getProgramAccounts in milliseconds; one that reads it from disk answers in seconds, and the difference is memory rather than clock speed. Every plan here is sized for the accounts database to stay resident.

Accounts and ledger on one drive is how nodes fall behind

The ledger is written continuously while the accounts database is read continuously. Put them on the same NVMe and they compete for IOPS, the node drifts a few slots behind, and then a few hundred. Two drives is not a luxury on Solana; it is the difference between a node that keeps up and one that does not.

A shared endpoint's rate limit is somebody else's traffic

On a shared plan the 429 you get at 11am is not about your usage — it is about the aggregate, and you have no visibility into it and no lever on it. A dedicated node has no rate limit because there is nobody to ration against.

The advantage

An application on a shared endpoint crosses a balancer, the public internet and a queue it shares with strangers before its request reaches a node. Put it on a machine beside its own node and the path is a cable inside the rack — and that traffic is not charged.

A shared endpoint versus a private link to your own nodeAbove: an application reaches a provider's load balancer over the public internet, waits behind other tenants' requests in a shared queue, and is served by a node it does not control. Below: the same application runs on a machine in the same rack as its own node and reaches it over a private link, with no balancer, no shared queue and no public internet in the path.Shared endpointYour appinternetBalancerShared queueother tenantsNodethree hops you do not control, and a queue you shareYour node, private linkYour appprivate linkYour nodenobody else queuedone hop, inside the rack, with the whole machine to yourself
Three hops you do not control, against one you do.
Shared tenancy against a dedicated machineOn a shared endpoint, several unrelated customers send requests to one node, so the rate limit and the latency tail belong to the aggregate rather than to any one customer. On a dedicated machine one customer reaches one node, so both belong to that customer's own workload.SharedSomeoneSomeoneYouSomeoneOne nodeone rate limitDedicatedYouYour nodeno limitthe tail is your ownworkload, not a stranger’s
The other tenants are invisible from outside a shared endpoint, which is exactly why their traffic is surprising when it arrives.

What you get

Built for Solana, not adapted to it

Configured before handover unless it says otherwise. Where something is optional, the page says optional.

Yellowstone gRPC, configured before handover

The Geyser plugin is compiled in and running when you receive the machine, with account, slot, transaction and block subscriptions on your private link and a token we issue you. Not a thing to ask for later and wait a week for — the difference between “available on request” and “configured” is a product difference, and we state which one you are getting.

DoubleZero, where the region supports it

We can attach the node to the DoubleZero fabric instead of routing over the public internet. Vote and block propagation are network problems before they are CPU problems, so this is where the milliseconds actually are. We will tell you honestly whether it helps your workload rather than selling it as a default.

Bring your own Geyser plugin

Have an indexer that needs its own plugin? We will build it and run it — or tell you why it will not keep up at your subscription volume, which is more useful than discovering it in production.

Snapshot restores, not a ledger replay

A rebuild restores from a recent snapshot rather than replaying the ledger, so recovery is hours instead of days. This matters more on Solana than anywhere else.

How it is built

How a Solana node is built here

Why a Solana RPC node needs two devicesAccounts and ledger are written continuously and independently. Anza's requirements put them on separate NVMe devices; a single device that satisfies the combined capacity still fails on input and output operations per second, and the node falls behind the cluster.one machineValidator process--no-votingaccountsledgerNVMe — accounts1 TB+, high TBWNVMe — ledger1 TB+, high TBWseparate devicesthe constraint isIOPS, not capacityRPC adds account indexes on top of both —and roughly doubles the memory a validator needs.
Two NVMe drives, not one. The accounts database is read on every transaction while the ledger is written continuously; on a single drive they compete for IOPS and the node drifts behind. This is the most common reason a Solana node that looks correctly specified still falls over.

Your choice

Run the client you want

A dedicated node is chosen on what software runs on it. This is the part a shared endpoint cannot offer at all.

Agave

The reference validator client, maintained by Anza. What we install unless you ask for something else, and the right answer for most RPC workloads.

Jito-Solana

Agave with the Jito block engine. For MEV-aware workloads and validators that want tips — which go to an account you nominate, with no cut taken by us.

Frankendancer

Firedancer's networking layer on the Agave runtime, for lower jitter. Available on request; we will talk through whether it suits what you are running first.

Pricing

Solana plans

Per month, exclusive of tax. The machine each one runs on is named, so the hardware can be checked against the price.

Solana RPC · Standard

A dedicated Solana RPC node, yours alone, with the accounts database and the ledger on separate NVMe drives.

$1,290.00

per month · $12,900.00 a year, 16% less

CPU
24 cores @ 2.85 GHz (AMD EPYC 7443P)
Memory
512 GB ECC
Storage
2 × 3.8 TB NVMe, accounts and ledger separated
Network
10 Gbps, 20 TB egress included
New YorkDallasFrankfurtSingapore
Recommended

Solana RPC · Performance

For indexers and traders: twice the memory, more cores, and headroom for getProgramAccounts without starving the ledger.

$1,890.00

per month · $18,900.00 a year, 16% less

CPU
32 cores @ 2.8 GHz (AMD EPYC 7543P)
Memory
1 TB ECC
Storage
2 × 3.8 TB NVMe, accounts and ledger separated
Network
10 Gbps, 20 TB egress included
New YorkDallasFrankfurt

Solana Validator

A dedicated Solana validator, operated for you. Vote account and stake remain entirely yours.

$3,490.00

per month · $34,900.00 a year, 16% less

CPU
24 cores @ 4.1 GHz (AMD EPYC 9275F)
Memory
768 GB ECC
Storage
2 × 3.8 TB NVMe, accounts and ledger separated
Network
100 Gbps, 20 TB egress included
New YorkFrankfurt

Honestly

How we compare

Every row is something you can check without asking us — including the one we lose.

What you can checkRPCNode.IOThe rest of the market
Price published on the pageNot “contact sales”, and not behind a login.YesSome publish, some quote on request
The exact machine namedProvider and SKU, so the hardware can be checked against the price.YesUsually a tier name only
Independent measurement of rivalsWe rank every public endpoint on three chains, including our own.YesNone publish measurements of competitors
Latency claims you can checkEvery figure links to the method and the data behind it.YesNumbers stated without a method
Yellowstone gRPC configured on handoverRunning when you receive the machine, not a later request.Solana plansOften an add-on or on request
Choose your clientAgave, Jito, Erigon, Nethermind, Reth and the rest.YesVaries; often fixed
Pay in crypto against an on-chain oracleFeed address and round id printed on the invoice.YesCard, or crypto at an unpublished rate
Track record on dedicated nodesWe are new at this. They are not.Not yetYears of production customers

Included

True of every node here

Whichever chain you came for.

Measured by the fleet that measures everyone else

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.

Your traffic in your own usage figures

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.

Private networking at no extra charge

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.

Root access, no agent required

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.

Regions chosen because we measure them

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.

Prices on the page

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.

Questions

Dedicated Solana RPC nodes: questions

What is a dedicated Solana RPC node?

A physical machine running a Solana validator client in RPC mode, allocated to one customer. Nobody else sends requests to it, so there is no shared rate limit, no noisy-neighbour latency and no credit metering. You choose the client, the region and the plugins.

Is Yellowstone gRPC included or extra?

Included and configured before handover on every Solana RPC plan. Account, slot, transaction and block subscriptions are exposed on your private link with a token we issue. There is no separate charge and no waiting list for it.

Can the node run on DoubleZero?

Yes, where the region supports it. DoubleZero is a dedicated fibre network for Solana traffic; attaching a node to it takes propagation off the public internet, which is where the latency actually is for vote and block delivery. Ask and we will set it up.

Can I run Jito, or Firedancer?

Jito-Solana is a standard option — pick it at order and tips route to an account you nominate. Frankendancer, which is Firedancer's networking layer on the Agave runtime, is available on request.

How long until the node is usable?

Hardware is allocated within hours of payment settling. The node then syncs, which is days on Solana — we restore from a recent snapshot rather than replaying the ledger to keep that short. Your node page shows the sync progress rather than telling you it is live before it is.

Do you hold my keys?

No. For a validator, the vote account and the stake are yours and we never hold the withdrawer key. For any machine, your own SSH public key is installed at provisioning and there is no private key of yours anywhere in our system.

How do I know the node is performing?

The same probe fleet that measures every public Solana endpoint on this site measures yours, from the same regions, with the same published method. You are not taking our word for it — you are reading the same measurements anyone can read about anyone else.

Why is a dedicated node better than a shared endpoint?

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.

How do you price these?

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.

Can I pay in crypto?

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.

What happens if I cancel?

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.

Do you have an uptime record for dedicated nodes?

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.

Order a Solana node

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.

Other chains