On this page
How to read this page. Rows marked used are plans BLIX has run real traffic through. Rows marked tried are sign-ups or endpoints we tested. Rows marked published are the provider's own stated numbers that we have not exercised. Plans change often: check the provider's pricing page before you build on any number here. BLIX is not affiliated with any of these companies and earns nothing from any of them.
The comparison
| Provider | Free allowance | Speed | What we found | Basis |
|---|---|---|---|---|
| Solana public endpoint | No monthly cap | 100 requests per 10 s per IP; 40 for one method | No key needed. Heavy methods answer 429 quickly. Fine for a script, not for an app. | used |
| Helius | 1M credits a month | 10 requests a second; 1 send a second | Everything an ordinary app needs is served, including token-account reads. The allowance is the limit: a busy reader spends it in days. | used |
| Alchemy | 30M compute units a month | Throttled by compute units a second | A typical read cost us about 20 units, so think 1.5M calls. Short bursts were rate-limited well before the monthly cap. | used |
| Chainstack | 3M request units a month | 25 requests a second | Account reads served (getBalance, getAccountInfo, getMultipleAccounts, getTokenSupply). getTokenAccountsByOwner, getProgramAccounts and getTokenLargestAccounts asked for a paid plan; signature history asked for archive access. | used |
| GetBlock | 50K compute units a day | Modest | A daily allowance, not monthly: it resets, but a burst can spend the day in minutes. | used |
| QuickNode | 10M credits a month (published) | 15 requests a second (published) | Served our ordinary account reads without method refusals. | used |
| Tatum | 100K credits a month | 3 requests a second | No batches larger than one request, and no getTokenAccountsByOwner. Fine for a slow single-request job. | tried |
| PublicNode | No key, no stated cap | Per-IP limits | Refused getTokenAccountsByOwner; getTransaction only one per batch. From a server IP that already used it for blocks, we were rate-limited. | tried |
| dRPC | Large free allowance advertised | n/a | When we tried in November 2026, Solana answered "chain is not available on free plan". | tried |
| Ankr | Free plan with sign-in | n/a | The old keyless public Solana endpoint now answers 403 without a key. | tried |
| Shyft | 1M credits a month | 10 requests a second | Not exercised by us. | published |
Checked November 17, 2026. "Credits", "compute units" and "request units" are each provider's own unit and are not comparable with each other.
What the big number hides
- Method blocks matter more than the allowance. The reads that make a wallet or holder view (
getTokenAccountsByOwner,getProgramAccounts,getTokenLargestAccounts) are exactly the ones free plans refuse. A plan with 3M units that blocks them is useless for a portfolio page and perfect for balance checks. - A credit is not a request. One provider charges one credit per call, another charges twenty units for the same call, a third charges more for heavy methods. Convert to "calls of the method I use most" before comparing.
- Bursts are throttled separately. You can be far under the monthly cap and still get 429s, because the per-second limit is what you hit when a page loads forty things at once.
- Daily and monthly caps fail differently. A monthly cap fails once, for weeks. A daily cap fails every afternoon. Budget per day either way, so a bad hour cannot spend the month.
- Batches are counted per item, and some free plans refuse batches entirely.
- Your IP has a reputation. A keyless endpoint that works from a laptop can refuse a cloud server that shares its address range with other heavy users.
Which free plan for which job
| You are building | What you need | A sensible start |
|---|---|---|
| A script or a class project | A few calls, no sign-up | The public endpoint |
| A wallet or portfolio view | Token-account reads that are not blocked | A plan that serves getTokenAccountsByOwner; test that method first |
| A price or pool watcher | Many cheap account reads | getMultipleAccounts on any plan with a high per-second limit |
| A live feed | WebSocket subscriptions that stay up | A provider key; see the WebSocket tutorial |
| Transaction history | Signatures and old transactions | A plan with archive access; many free plans stop at recent history |
| A trading bot that sends | Fast, reliable sends | Usually a paid plan: free plans allow about one send a second and no priority routes |
Making free plans go further
- Test the exact methods you need before writing code. One curl per method tells you more than the pricing page. The requests are on the Solana RPC page.
- Route by method. Send cheap account reads to the plan with the highest per-second limit and heavy reads to the plan that serves them. A request should only go to a provider that serves every method in it.
- Give each provider a daily budget and a per-second cap below what it allows, so a burst never becomes a ban.
- Cache what does not change. Token decimals, metadata and old transactions never change; read them once.
- Batch with
getMultipleAccountsinstead of a hundredgetAccountInfocalls. - Fall back on refusal, not on a timer. When one provider says 429 or "paid plan", try the next one for that request and leave the first alone for a while.
When free stops being enough
Three things push a project to a paid plan, and none of them is the monthly number: sending transactions that must land quickly, streaming every transaction of a busy program without gaps, and reading history older than ordinary nodes keep. If your project needs none of those, free plans carry it a long way.
If what you want is the data, not the node
A lot of people look for a free RPC because they want live Solana token data: new launches, trades, holders, candles, wallet activity. Rebuilding that from raw RPC calls is weeks of work and a lot of requests. A BLIX account includes that data already indexed, over 69 JSON endpoints and one live stream, at no charge. It does not replace an RPC for sending your own transactions or reading arbitrary accounts.
More on Solana and on-chain data
This page is education about how the technology works. It is not financial advice, and nothing here recommends buying or selling anything.
Frequently asked questions
What is the best free Solana RPC?
It depends on the method you call most. For general reads, a plan that serves token-account methods is the most useful; for many cheap account reads, the one with the highest per-second limit. Test your exact methods with curl before choosing.
Is the public Solana RPC free?
Yes, and it needs no key, but it allows about 100 requests per 10 seconds per IP and throttles heavy methods much harder. Solana's own documentation says it is not meant for production apps.
Why do I get 429 errors under my monthly limit?
The per-second limit is separate from the monthly allowance. A burst of requests trips it even when most of the month's allowance is unused. Add a per-second cap in your own code.
Can I use several free RPC providers at once?
Yes, and it is the usual way to stay inside each plan: route each request to a provider that serves that method, with a daily budget per provider and a fallback when one refuses.
Do free plans include WebSockets?
Most include standard WebSocket subscriptions. High-volume streaming products (gRPC streams of every transaction) are paid on every provider we looked at.

