Solana Yellowstone gRPC endpoint: 8 streams on Pro, 20 on Business

Last updated: October 25, 2026

Yellowstone gRPC plans

Solana gRPC (Yellowstone) is a native HTTP/2 and protobuf endpoint for backend ingestion. Yellowstone exposes updates from Solana's Geyser interface (read how the Geyser plugin interface works); your client sends a subscription and receives the matching account, transaction or slot updates. Pick a plan by concurrent sessions and the HTTPS read capacity you need alongside them.

Plan prices and limits come from the enforced plan matrix. Read RPS is the Solana HTTPS read budget, separate from the gRPC concurrent-stream count. Firehose connections have no per-key connection limit and do not count against the gRPC allowance. Create a Pro API key to connect.

What counts as a stream?

One open geyser.Geyser/Subscribe session counts as one stream per API key. Several named filters in that session share its allowance; watching several addresses does not by itself open several streams. Opening a session beyond your cap returns RESOURCE_EXHAUSTED. Leave room for a replacement session during deployments, or close an old session before opening another.

A new SubscribeRequest within the same session replaces the entire active filter set; it does not open a second stream. Keep the complete intended set in your application and resend it when changing filters. Omitting an old filter removes it. See how SubscribeRequest filters combine and replace for routing several consumers through one session.

What 8 streams cost elsewhere

These published options can cover eight concurrent gRPC sessions. Prices are monthly list prices; connection allowances, base-plan requirements and traffic billing differ. This is a focused purchase check for a Triport plan, based on the dated vendor pages below.

Shyft's published entry option costs less than Triport Pro for this connection count. Triport Pro bundles 8 gRPC streams, 2 Shred stream connections, Firehose and 200 Solana read RPS for $249/mo, with no per-GB charge. Compare the complete workload, including replay needs and traffic billing, before choosing.

Stream counts, traffic metering and replay windows for the Yellowstone providers we track, with dated sources: see how other providers price Yellowstone streams.

Subscribe and filter

Use standard Yellowstone requests for accounts, transactions, slots, blocks, block metadata and entries. Select processed, confirmed or finalized commitment according to the certainty your consumer needs. Start with this minimal slot request to check delivery before adding narrower account or transaction filters:

{ "slots": { "my-slots": {} } }

Test connectivity and authentication with GetVersion. Supply your local Yellowstone proto descriptors: the public reflection service does not expose the full Geyser contract. The import path below assumes the proto files are in ./proto.

grpcurl -import-path ./proto -proto geyser.proto \
  -H "x-token: $TRIPORT_API_KEY" \
  grpc.triport.io:443 geyser.Geyser/GetVersion

Keep the key in backend call metadata. The key needs stream.grpc.solana scope; wildcard keys also work. The Yellowstone gRPC reference has client examples and the complete connection contract.

How the subscription is served

Each subscription is served by a race between several independent sources; the client receives the first arriving message. Your application uses one endpoint and the standard Yellowstone request and update shapes. This does not add a replay buffer or change the commitment you request. Measure arrival and processing from your own region with your actual filters before sizing ingestion.

When the stream drops

There is no replay buffer on Triport's live gRPC streams. Reconnecting restores live delivery; it does not resend the updates produced while you were disconnected. A client library's reconnect option cannot supply history the endpoint does not retain.

1. Persist the last fully processed slot with your application checkpoint, after its work is committed.
2. Reconnect with exponential backoff starting around one second, adding jitter, and resend the complete SubscribeRequest.
3. Read continuously on the new stream while filling the missed slot range through HTTPS with getBlock, or find relevant address history with getSignaturesForAddress.
4. Deduplicate the overlap between backfill and the live stream. Use commitment appropriate to your application before treating an outcome as final.

Keep database writes, enrichment and other heavy work off the stream-reading loop. Narrow filters when your consumer falls behind, and monitor the distance from its checkpoint to the live slot. The stream may be closed under sustained backpressure; reconnect as above. HTTPS backfill uses your plan's per-method RPS limits and cannot recreate every intermediate account update. Consult gRPC status codes and fixes before retrying authentication or entitlement errors.

Migrating from another Yellowstone provider

Change the target to https://grpc.triport.io and set your Triport key as x-token. Clients that accept a dial target use grpc.triport.io:443 with TLS. Keep your standard subscription shapes, then test each filter and commitment level. Triport answers GetVersion with a neutral payload and removes vendor identifiers from source error messages and metadata. Check your library's replay settings explicitly: moving the host does not preserve another provider's replay window.

When Triport is the wrong choice

• You need server-side replay. Helius advertises up to 48 hours; its docs disagree on the window, so confirm it. (Helius replay, read 2026-10-24) (Replay caveat, read 2026-10-24) QuickNode publishes 3,000 slots. (QuickNode replay, read 2026-10-24)
• You need Asia regions. Triport Pro and Business list eu and us in the plan matrix. Select a provider with the location your ingestion needs.
• You need more than 20 concurrent gRPC sessions without Enterprise. Arrange contract capacity or compare another provider's published allowance.
• You need pre-execution transactions over gRPC or raw UDP shreds. Neither is available here. For deshredded transactions before execution, use the Shred stream over WebSocket; raw-shred ingestion requires a different product. The difference between execution updates and deshredded data: Solana shreds and Turbine explained.