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 | Indexer | |
|---|---|---|
| Answers | Current state, one request at a time | History, filters and totals from a database |
| Sends transactions | Yes | No |
| Typical use | Balances, simulate, send, confirm | Activity feeds, leaderboards, analytics |
| Who runs it | A provider, or you | You, or a provider that decodes for you |
Providers package these differently: ask what is included in writing.
- 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.
- Decoding: Anchor programs publish an IDL, and accounts and instructions start with an 8-byte discriminator, so decoding is mostly mechanical. Native programs need a hand-written decoder.
- Streaming: validators can stream account, slot and transaction updates through Geyser plugins, and providers expose this as a gRPC feed. It is the usual way to keep an indexer current.
- Backfill: when you start, you also need old data. Ask where history comes from and how long a backfill takes.
- Compressed NFTs: their data is not stored in ordinary accounts, so reading them needs an indexer that supports the Digital Asset Standard (DAS) API.
When you need one
- You show history: activity feeds, transaction lists, portfolio charts.
- You rank or total: leaderboards, volume, TVL, rewards, anything summed across accounts.
- You search or filter: by owner, status, date range or tag across many accounts.
- Your account scans are slow: getProgramAccounts timeouts or a growing bill are the usual sign.
- You need reports: finance, tax or compliance exports are database work, not RPC work.
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
- Hosted indexer or data API: fastest to start, you pay per use and depend on their schema and uptime. Good for early stage.
- Your own indexer: full control of schema, history and cost at scale, but you run a stream consumer, a database, monitoring and backfills. Budget engineering time for it.
- Mixed: a hosted feed for the stream, your own database for the data that is core to the product.
Mistakes to avoid
- Reading processed data as final: processed slots can be dropped. Index at confirmed or finalized, or write rollback handling.
- No lag alert: an indexer that quietly stops shows stale numbers to users. Monitor the gap to the chain head.
- Ignoring program upgrades: a new account layout breaks old decoders. Version your decoders.
- Using RPC as a database: it works in a demo and fails on launch day.
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
- Solana program monitoring: what to watch and alert onWhat to monitor on a live Solana program: failed transactions, upgrade and authority changes, keeper balances, oracle freshness and RPC lag, plus how to get the data and who should own each alert.
- How to choose a Solana RPC provider: 10 questions to askHow to pick a Solana RPC provider: shared vs dedicated nodes, rate limits, streaming, transaction landing, failover and security, with questions to ask and a way to test.
- What makes a Solana development company trustworthy? 8 signals you can checkHow to tell if a Solana development company is trustworthy: on-chain programs, public commits, named engineers, client references, code ownership and milestone payments.