Blog · Guides · 6 min read

Solana indexer vs RPC: what to use, and when to add an indexer

By Kuba Malarczyk, Founder ·

Use an RPC node to read current state and send transactions. Add an indexer when your app needs history, filters, totals or fast lists, because RPC answers one question at a time and is not a database. Most production Solana apps use both: RPC for the live path, an indexer for everything users browse.

RPC node vs indexer
RPC nodeIndexer
AnswersCurrent state, one request at a timeHistory, filters and totals from a database
Sends transactionsYesNo
Typical useBalances, simulate, send, confirmActivity feeds, leaderboards, analytics
Who runs itA provider, or youYou, or a provider that decodes for you

Providers package these differently: ask what is included in writing.

Key takeaways
  • An RPC node reads state and sends transactions. It is not built to filter, sort or aggregate history.
  • An indexer reads chain data, decodes it with your program IDL and stores it in a database you can query.
  • Add an indexer when you show histories, lists, totals or search, or when getProgramAccounts gets slow or costly.
  • Index at confirmed or finalized commitment, or handle rollbacks if you read processed data.
  • Decide who owns the data pipeline before launch: it is part of the product, not an afterthought.

A first Solana app usually works with a single RPC endpoint. Then someone asks for a transaction history, a leaderboard or a search box, and the endpoint that felt fast starts to feel slow and expensive. The cause is usually not the provider. It is asking an RPC node to do the job of a database.

What an RPC node is good at

RPC methods return the current state of the chain: an account, a balance, a transaction by signature, the result of a simulation. The same endpoint is how your app sends transactions and learns whether they landed. That is the live path, and it should stay on RPC.

Where it struggles is breadth. Scanning every account of a program with getProgramAccounts is heavy, providers often limit or price it up, and standard nodes do not keep unlimited history. Our guide on choosing an RPC provider covers rate limits and transaction landing.

What an indexer adds

An indexer reads blocks, transactions and account updates, decodes them and stores the result in a database. Your app then queries that database with ordinary filters, sorting and aggregation, so a history page is one fast query instead of thousands of RPC calls.

When you need one

If you only read balances and send transactions, an RPC provider is enough. Do not build a pipeline you do not need.

Build it or buy it

Questions to ask a provider or developer: which commitment level do you index at and how do you handle a rolled-back slot? How do you backfill history? What happens when a program upgrade changes an account layout? How do you detect that the indexer fell behind? Who owns the database and can we export it?

Mistakes to avoid

Indexing is also a cost line in a build. See how much it costs to build a Solana dApp, and compare verified providers on the Solana infrastructure providers page. The related term in the glossary is RPC.

Also useful: how to monitor a Solana program in production.

Frequently asked questions

Do I need an indexer for my Solana app?

Only if you show history, lists, totals or search, or if account scans such as getProgramAccounts become slow or costly. If you read balances and send transactions, an RPC provider is enough.

What is the difference between an RPC node and an indexer on Solana?

An RPC node returns current chain state and sends transactions, one request at a time. An indexer reads and decodes chain data into a database you can filter, sort and aggregate.

What is a Geyser plugin?

A validator plugin interface that streams account, slot and transaction updates to an external system. Providers commonly expose it as a gRPC stream that indexers consume to stay current.

Should I build my own Solana indexer or use a hosted one?

A hosted indexer is the fastest start but ties you to its schema and uptime. Your own gives full control at scale but means running a stream consumer, a database, monitoring and backfills. Many teams mix both.

Find a Solana infrastructure provider

Describe your workload and stage. Smart Match suggests verified infrastructure and development providers with a reason for each match. Free for teams.

Get matched →

Looking for help with this? Browse Solana infrastructure and RPC providers, or describe your project and get matched for free.

Related reading

← All posts