TriportRPC

Yellowstone gRPC endpoint on a flat monthly plan

Last updated:

What you can subscribe to

Yellowstone gRPC (also known as Dragon's Mouth) is the de-facto standard for low-latency Solana data. A single bidirectional stream carries your subscribe request and delivers typed updates: account writes filtered by owner or address, transactions filtered by involved accounts, full blocks, block metadata and slot progression at processed, confirmed or finalized commitment. Existing Yellowstone clients work unchanged — point the channel at the Triport endpoint and pass your API key.

Connect

# endpoint
triport.io:443            # TLS gRPC
# auth: x-token metadata or Authorization: Bearer <api-key>

Why flat pricing matters for gRPC

Streaming is the workload where usage-billed providers get expensive fastest: a busy account stream can move gigabytes per day, and per-GB or per-credit metering turns that into an unpredictable bill. Triport meters plans by RPS and stream count only — a stream that runs 24/7 costs the same flat monthly price. See the provider comparisons for how credit-based billing models price the same workload.

Plan availability

  • Pro ($249/mo) — 8 concurrent gRPC streams, full DAS, ZK Compression.
  • Business ($499/mo) — higher stream limits plus first-shred and unfiltered pre-execution streams.
  • Enterprise — custom stream counts and dedicated capacity.

FAQ

How many concurrent Yellowstone gRPC streams do I get?
The Pro plan ($249/mo) includes 8 concurrent gRPC streams; higher limits are available on Business and Enterprise. Platform-wide capacity is 100+ concurrent streams.
Is Yellowstone gRPC traffic metered or billed per GB?
No. Triport plans are flat monthly subscriptions — streaming traffic is not billed per gigabyte and does not consume credits, unlike usage-billed providers that meter gRPC by traffic volume.
Which subscriptions does the stream support?
Standard Yellowstone (Dragon's Mouth) subscribe requests: accounts (with owner/account filters), transactions (by account include/exclude), blocks, block metadata, slots and entries, each with configurable commitment levels.