Yellowstone gRPC providers for Solana compared (2026): streams per plan, metering and replay

Last updated: October 25, 2026

Disclosure: We sell one of these (Triport); its row is marked (ours). This comparison is ordered for reading, with no scores or speed ranking.

Compare plans · Pick by stream count · Estimate metered traffic

Solana gRPC providers: streams, prices, metering and replay

Monthly list prices and connection allowances below come from dated vendor records. Add-ons require their base plan; a prepaid deposit is not a monthly fee. “Not recorded” means the catalog cannot establish the detail, not that a feature or location is unavailable. Each row is a Yellowstone-compatible gRPC endpoint over the validator's Geyser interface; read how the Geyser plugin interface works before comparing them.

Vendor contradictions matter at checkout: Chainstack's title and pricing cards disagree on stream count; Helius pages give different replay windows; QuickNode's separate Streams product has its own active-stream table. The dated caveats above keep those distinctions visible. Do not substitute the older QuickNode announcement's traffic rate for its October documentation.

Pick by stream count

These are capacity shortlists, not a cheapest-to-most-expensive ranking. Count all replicas and temporary deployment overlap. A plan covering only part of a band is an option only up to its published allowance.

For eight sessions, Shyft Build's full $199 monthly plan covers the workload; its 10 included connections cost $19.9 each, versus $31.125 per included stream on Triport Pro. This divides the full plan price by included capacity; it is not a separately purchasable per-stream tariff. Shyft is cheaper per included stream. Triport's case is the product bundle and absence of traffic metering.

The 21–50 row includes offers with different capacities; check the individual connection count. Above the largest listed allowance, request Enterprise terms rather than assuming another connection is included. On Triport Business the Shred stream filter is optional; Firehose has no per-key connection limit and its connections do not count against the gRPC allowance. Shred stream has no data-volume quota and no per-GB charge. Connection, filter and API RPS limits still apply. Plan matrix and Shred stream reference, checked 2026-10-25.

Metered vs included: what your filter will cost

Measure billable bytes for your exact filters from the region where your consumer runs. Use the same commitment and message types you will deploy. Application payload size, network traffic and the provider's billable-byte counter can differ; confirm which counter drives the invoice.

Monthly traffic charge ≈ GB/day × 30 × price per GB
Total ≈ base plan + required add-ons + chargeable traffic + other metered usage

The first formula assumes a constant daily billable volume over a 30-day month. For credits, subtract the remaining applicable monthly credit allowance before charging overage; RPC calls may consume the same allowance. For data bundles, subtract included data under that provider's terms. The marginal rates below do not include subscription fees and are not a forecast of your total bill.

Conversions use decimal units: 1 GB = 1,000 MB and 1 TB = 1,000 GB, not GiB or TiB. Helius counts uncompressed bytes; QuickNode on port 443 counts compressed data when compression is negotiated. Equal decoded payloads therefore need not produce equal billable GB. QuickNode's rate is effective from 2026-10-01; both dated inputs appear beside each conversion.

• Triton One: Streaming traffic is $0.08/GB; compression billing basis is not stated in the captured pricing page. Equivalent decimal rate: $0.08/GB. Compression billing basis is not recorded in the catalog. Source, read on 2026-10-24.
• Alchemy: gRPC costs $75/TB prorated by bytes; spend caps and alerts do not apply to gRPC bandwidth. Equivalent decimal rate: $0.075/GB. Compression billing basis is not recorded in the catalog. Source, read on 2026-10-24.
• Ankr: $0.5/GB for request and response binary data, plus $0.000001 per method call. Equivalent decimal rate: $0.5/GB. Compression billing basis is not recorded in the catalog. Source, read on 2026-10-25.

No filter-volume measurements are available for this comparison. We will publish measured volumes when a dated dataset and method are available; until then, substitute your own observed GB/day in the formula. Do not estimate an all-network feed from the number of open connections alone. For the broader billing model, see how credit metering differs from flat plans.

What vendors claim about delivery and replay

The source catalog records delivery and recovery claims, but no comparable latency measurements or reproducible latency methods. The statements below concern recovery, not arrival speed. No measured timing result or provider speed ranking is published here.

At Triport, each subscription is served by a race between several independent sources; the client receives the first arriving message. This describes delivery behavior, not a measured speed advantage. Test equivalent filters and commitment levels on the same host, match updates by signature, and timestamp receipt with one local monotonic clock. Record the region, client versions, sample window, missed matches and reconnect gaps so first-arrival results have a clear denominator.

When Triport is the wrong choice

• You require server-side replay after a disconnect. Triport live gRPC has no replay buffer; backfilling through HTTPS consumes the plan's read RPS budget and does not recreate every account update.
• You require a standard plan region beyond EU and US. Confirm the precise location and capacity with any shortlisted vendor.
• You require more than 20 concurrent gRPC sessions without a contract. Enterprise capacity is negotiated, not a published fixed stream count.
• You require raw UDP shreds or pre-execution data over gRPC. Triport supplies neither through Yellowstone. gRPC access also does not come with Basic or the trial.

For endpoint, auth and recovery details, see Triport Yellowstone gRPC plans and the gRPC troubleshooting reference. Native clients connect to grpc.triport.io with x-token metadata.

Shreds instead?

Pre-execution intent and raw UDP packets are different products from execution-aware gRPC updates. If your bot needs transactions before execution or your node needs packets, start with shred stream providers compared.

Methodology and dates

Competitor facts and all derived rates use the existing provider catalog; every cited row retains its source URL and verification date. Streaming records were checked on 2026-10-24–2026-10-25; the older credit-overage dates remain visible because the conversion uses both inputs. Prices use monthly billing, not annual discounts. Regions and latency evidence absent from the catalog stay unverified. Triport plan data comes from the shared matrix-derived facts and API reference, checked 2026-10-25. Refresh this comparison monthly and confirm checkout terms, compression, replay and regional availability before purchase.