Blog · Guides · 7 min read

How to choose a Solana RPC provider: 10 questions to ask

By Kuba Malarczyk, Founder ·

To choose a Solana RPC provider, start from your workload: reads, heavy account queries, streaming or sending transactions. Check documented rate limits, how transactions land, regions, support and uptime history, then benchmark two providers with your own traffic for a week. Use a second provider as a fallback, and never expose an unrestricted key in the frontend.

Shared vs dedicated Solana RPC
Shared planDedicated node
CostLower, scales with requestsMuch higher, fixed
PerformanceVaries with other customersSteady, reserved for you
Heavy queriesOften limited or priced upUsually fewer limits
Good forEarly stage and most appsTrading, indexers, high load

Plans and prices differ by provider: ask for current limits in writing.

Key takeaways
  • The public Solana endpoints are rate limited and are not for production.
  • Match the provider to your workload: plain reads, heavy account queries, streaming or transaction sending behave very differently.
  • Ask how transactions land and what happens at the rate limit, not just for a requests-per-second number.
  • Benchmark with your own traffic and compare latency, errors and slot lag.
  • Use two providers, keep API keys out of the frontend, and test the failover.

An RPC provider sits between your app and the chain. When it is slow or drops requests, users blame your product, not the node. Choosing one is mostly a question of what you ask it to do, and a few checks before you sign save a painful migration later.

Start with your workload

Ten questions to ask

Test before you commit

A benchmark of simple calls tells you little. Run your own traffic against two providers for a week, including your heaviest calls and some peak hours. Record median and slow latency, error rates, rate-limit responses and how far each reports its slot behind a second source. Ask for a trial or a short plan to do it.

Use two providers. A single endpoint is an availability risk for your frontend and your keepers. Configure a fallback, set client-side timeouts and test the switch before launch, as in the pre-launch security checklist.

Security and red flags

For terms and fees around priority transactions see the glossary entries for RPC and priority fee. To compare providers that Orivions has verified, see Solana infrastructure providers.

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

Frequently asked questions

Can I use the public Solana RPC endpoint in production?

No. The public endpoints are rate limited and are meant for development and light use. A production app needs a provider with documented limits, support and an agreement on uptime.

What is the difference between shared and dedicated Solana RPC nodes?

Shared plans split capacity between customers and are cheaper, but a busy neighbour or a traffic spike can slow you down. A dedicated node is reserved for you, costs much more, and gives steady performance and fewer limits on heavy calls.

Do I need more than one RPC provider?

For anything that holds user funds or runs keepers, yes. One provider is a single point of failure. Configure a second one as a fallback and test the switch.

How do I test a Solana RPC provider before committing?

Run your own real workload against it for a week and record median and slow latency, error rate, rate-limit responses and how far its reported slot lags behind a second source. A benchmark of simple calls tells you little about your use case.

Find a verified Solana infrastructure provider

Describe your project and load. Smart Match suggests verified infrastructure 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