# What Solana RPC actually costs once the prototype works

> The free RPC endpoint got you through the demo. Production means rate limits, archival history, websockets that stay up — and a provider bill that scales with calls your code did not need to make.

The public Solana RPC is a shared hose: fine for devnet hacking, throttled to uselessness at real traffic. Paid providers sell requests per month plus compute units — Helius, QuickNode, Alchemy and friends — and the pricing model means the bill is driven by call count × method cost, not by how much your app does. A wallet tracker that polls every account every block is a very different customer than one using websockets.

The two real cost drivers are architecture decisions made early. Polling versus subscribing: `getAccountInfo` in a loop costs calls forever; a websocket subscription or Yellowstone gRPC stream pushes changes once. And history: `getTransaction` on data older than a couple of days needs archival endpoints, which cost meaningfully more — the decision of whether you actually need deep history (and for what) is worth more than negotiating rates.

## Measure calls before scaling them

Log what the app actually requests for a week before buying a plan: which methods, how often, from where. The usual finding is a retry loop or a N+1 pattern inflating calls tenfold — fixing the pattern is free and beats any negotiation. Provider dashboards show the same data but only after you are already paying.

## Push beats pull on anything live

Websockets (or gRPC streams on the heavier providers) deliver account and log changes as they happen — one connection instead of a poll per entity per interval. For NFT trackers, wallet dashboards and anything watching many accounts this is the difference between a starter plan and an enterprise invoice.

## Archive only what needs archiving

Full archival history is the expensive tier for a reason: most apps need recent state plus the occasional deep lookup. Keep hot data in your own database (written once, read free), hit archival endpoints only for what you did not store, and decide upfront whether 'look up any transaction ever' is a feature or a liability.

## What to take away

- Paid RPC bills calls × method cost — a chatty client is the bill.
- Websockets/gRPC streams replace most polling; measure calls before buying.
- Archival history is the expensive tier — store hot data yourself, archive on demand.
- Fix retry loops and N+1 patterns first; it is free and beats any plan upgrade.

## Tags

Solana, RPC, Infrastructure, Costs

## We build this for clients

https://dfieldsolutions.com/en/services/blockchain

## More from the lab

- https://dfieldsolutions.com/en/lab/solana-anchor-footguns.md — Solana foot-guns Anchor does not remove
- https://dfieldsolutions.com/en/lab/custom-software-cost.md — What custom software actually costs
- https://dfieldsolutions.com/en/lab/custom-vs-off-the-shelf.md — Custom software or off the shelf — the honest test
- https://dfieldsolutions.com/en/lab/n8n-self-hosted-vs-zapier.md — Self-hosted n8n or Zapier — where the bill actually differs

---

Source: https://dfieldsolutions.com/en/lab/solana-rpc-costs
DField Solutions — Dunakeszi, Hungary — dezso@dfieldsolutions.com
Booking: see https://dfieldsolutions.com/en/contact