LinkPool

RPC endpoints at a fixed monthly cost

Managed RPC endpoints on infrastructure LinkPool owns and operates. One fixed monthly cost for the endpoint you need, with no compute units, no per-request metering and no overage bill.

LinkPool has operated Web3 infrastructure since 2017, against a 99.99% uptime SLA target, on a 1.5 Tbps+ east-west network with 0.2 ms latency between nodes.

Metered billing is the problem, not the price

Usage-based RPC pricing moves the risk onto you. Credits, compute units and request tiers are the same idea in different clothes: the bill is unpredictable, and it grows fastest on your best day.

Metered billing punishes growth

Compute-unit pricing scales with traffic, so a launch or a volatile market arrives as an overage charge. A fixed monthly cost prices the endpoint once and leaves the bill alone.

Rate limits are the hidden cost

Metered plans cap requests per second as well as total volume. Hitting that ceiling means throttled calls or an upgrade in the middle of an incident. Here the capacity is agreed when the endpoint is sized.

Egress is not a line item

A busy public endpoint serves multiple terabytes of JSON-RPC traffic a month. Bandwidth is a flat monthly port on a network LinkPool owns, so egress never arrives as a separate charge.

Chains we support

RPC nodes across 74 mainnets, plus testnets, alongside oracle infrastructure for the Chainlink Network.

Featured: Ethereum, Solana, Polygon, BNB Smart Chain, Bitcoin, Avalanche, Polkadot, Sui, Linea, Starknet, Hedera and the XRP Ledger.

Every network: AB, Abstract, ADI, ApeChain, Aptos, Arbitrum (testnet), Arc (testnet), Avalanche, Base (testnet), Berachain, Bitcoin, Blast (testnet), BNB Smart Chain, BOB, Botanix, Celo, Centrifuge, Codex, Conflux, Core, Cronos, Cronos zkEVM, Dogecoin, Edge, Ethereum, Etherlink, Frax, Gnosis (testnet), HashKey, Hedera, Hemi, Hyperliquid, Ink, Kaia, Katana, Lens, Linea, Lisk, Litecoin, Mantle, MegaETH, Merlin, Metal L2, Metis, Mode, Moonbeam, Moonriver, Morph, Neo X, opBNB, Pharos, Plasma, Plume (testnet), Polkadot, Polygon, Ronin, Rootstock, Scroll, Sei, Shibarium, Solana, Soneium, Sonic, Stable, Starknet, Stellar, Sui, Superseed, TAC, Taiko, Tempo, TRON, Unichain, WEMIX, World Chain, X Layer, XDC, XRP Ledger, ZetaChain, Zircuit (testnet), zkLink.

More chains are available on request. Tell us the chain and the traffic profile and we will confirm what we can run.

Built for endpoints that stay up

Kubernetes on owned hardware

Managed clusters on hardware LinkPool owns. Containers run straight on the machine, so no hypervisor sits between your requests and the CPU.

Guaranteed QoS on Performance

Performance reserves capacity, so requests equal limits: no throttling and no eviction when a neighbour spikes.

Three availability zones

Endpoints fail over across three availability zones in Manchester, the location institutional buyers audit.

Protected and monitored 24/7

DDoS protection in front of every endpoint, continuous health checks behind it, and automatic failover when a node falls out of sync.

What teams ask us

Do you charge per request or per compute unit?

No. There are no compute units, no credit balance and no per-request metering. You pay one fixed monthly cost for the endpoint, and it does not move when your traffic does.

How is the cost worked out?

Every quote is different because every workload is. We size the endpoint against the chains you need, the traffic profile and whether you need archive data, then quote a single fixed monthly figure for the term.

Which chains do you support?

RPC nodes across 74 mainnets, plus testnets, including Ethereum, Solana, Polygon, BNB Smart Chain, Bitcoin, Avalanche, Polkadot, Sui, Linea, Starknet, Hedera and the XRP Ledger. The full list is on this page, and LinkPool runs oracle infrastructure for the Chainlink Network on the same platform. More chains are available on request.

What happens when my traffic spikes?

The bill does not move. Capacity is agreed when the endpoint is sized rather than sold in requests-per-second tiers, so a spike is a conversation about headroom rather than an overage invoice.

Can we have a private endpoint rather than a shared public one?

Yes. A private endpoint serves you alone rather than sharing a public URL with other traffic. Resources on the platform are shared by default and Performance reserves them, so tell us the throughput and isolation you need and we will size it.

How we think about RPC

Get a quote for your RPC workload

Tell us the chains, the traffic profile and the scale. We reply with a fixed monthly number, not a deck.