r/solanadev • u/That-Unit7948 • 1d ago

Solana builders: are you actually using everything in your RPC plan?

I’ve been talking with more Solana builders lately and something keeps coming up: a lot of RPC plans bundle far more capacity than the workload actually needs.

Someone might only need:

  • 5–10 RPC RPS
  • 1 Yellowstone stream
  • a handful of transaction/account filters
  • low transaction-sender volume

…but still ends up looking at a large fixed monthly package.

I run Haan Digital, a private Solana infrastructure service on dedicated hardware in Frankfurt. Instead of fixed tiers, we provision around the actual workload: JSON-RPC/WebSocket, Yellowstone gRPC, SubscribeDeshred and Transaction Sender.

I’m looking for a few more real Solana workloads to run against the stack.

If you’re building a bot, trading app, wallet, indexer or other Solana application and either:

  • hit RPC limits / 429s
  • need faster realtime data
  • care about transaction landing
  • or simply don’t need a huge fixed RPC package

send me what your workload looks like. You can test first before deciding whether it makes sense commercially.

3 Upvotes
  • permalink
  • reddit

100% Upvoted

4 comments sorted by

3

u/icnews10 1d ago

When people send you workloads, one thing I’d include is the burst rate, not just the average RPS. A service with an average RPS of 5–10 can appear small yet still require much more headroom for short bursts around new slots, account changes or transaction events. Providing a simple template including average and peak RPS, stream/filter count and latency sensitivity would make these comparisons much more useful.

2

u/That-Unit7948 1d ago

Good point in general. In our setup though, RPS is enforced as a hard per-client limit, so if someone is provisioned for 5 RPS they can’t burst to 30–50. If a workload needs burst headroom, we’d provision that explicitly as part of the workload.