// Geyser gRPC + Fastlane
Stream Solana transactions, accounts, slots, and blocks over a Yellowstone-compatible Geyser gRPC interface. Both modes are built for speed: Regular Geyser for reliable production streaming, and Fastlane—Shreder’s custom implementation with the same client code and up to 2x lower latency.
Already using Yellowstone gRPC? Point your client at a Shreder endpoint and keep your existing subscription logic. For shred-level transaction streams, see Binary or Decoded Shreds.
Measured in head-to-head Geyser-class benchmarks. View benchmarks and methodology →
// Choose your speed path
Both modes are fast, structured, and compatible with Yellowstone tooling. Choose Regular Geyser for reliable standard delivery. Choose Fastlane when speed is the deciding factor and you want Shreder’s fastest gRPC path without changing your client.
Shreder’s accelerated Yellowstone-compatible implementation. Same interface and data semantics as Regular Geyser, with 2x faster delivery through a custom low-latency path.
Standard Yellowstone Geyser gRPC for production teams that need reliable structured Solana data, familiar subscription filters, and cost-efficient delivery.
// Structured Solana streaming
Geyser is Solana’s validator-side streaming interface for pushing blockchain updates to external systems. Yellowstone gRPC is the widely used protocol built around that interface. Instead of polling RPC or relying on coarse WebSocket subscriptions, Geyser gRPC lets your backend subscribe to structured updates as they happen.
With Shreder Geyser gRPC, you stream transactions, account updates, slots, blocks, block metadata, and entries through a persistent gRPC connection. Filters run at the stream level so your application receives targeted updates instead of repeatedly querying RPC.
Fastlane is not a separate data format—it is Shreder’s accelerated implementation of the same Yellowstone-compatible Geyser gRPC interface.
// Fastlane
Regular Geyser is already a fast structured stream. Fastlane reduces time-to-data while preserving the same Yellowstone-compatible API—your subscription logic stays intact.
Use the same Yellowstone-compatible client, protos, filters, and stream types.
Fastlane uses Shreder’s custom implementation to deliver Geyser data 2x faster.
Engineered and validated for data consistency and accuracy while optimizing delivery speed.
Change endpoint and token—keep your existing Yellowstone subscription filters.
// Stream types
Keep subscriptions narrow for lower bandwidth and faster processing, or stream broader data when your indexing workload requires it.
Track by included, excluded, or required accounts, signature, vote status, and failed status.
Subscribe by exact account, owner, memcmp filters, data-size filters, and optional data slices.
Follow slot updates and commitment transitions for sync and latency measurement.
Receive block-level data for indexing and analytics pipelines.
Monitor execution status and lifecycle details for post-execution context.
Track block metadata or entry updates where your endpoint and plan support them.
Available stream types, filter limits, and replay behavior may vary by plan. Contact Shreder if you need broad filters, full-block payloads, or dedicated infrastructure.
// Use cases
Receive transaction and account updates earlier with a standard Geyser-compatible stack. Use Fastlane when milliseconds matter.
Monitor transactions, slots, and account changes with lower time-to-data on Fastlane.
Stream transactions, accounts, and blocks into databases and queues without polling RPC.
Deliver faster balance, confirmation, and program-activity updates to users and dashboards.
// Benchmarks
Representative Geyser-class runs in Frankfurt. Comparing first-detection share and latency percentiles under the same filters and commitment level.
Run 002
Measured in Frankfurt, Teraswitch FRA2.
| Provider | p50 | p95 | p99 |
|---|---|---|---|
| Shreder Fastlane Frankfurt | 0.00 ms | 0.00 ms | 0.00 ms |
| Helius LaserStream Frankfurt | 2.92 ms | 26.58 ms | 45.08 ms |
Run 003
Measured in Frankfurt, Teraswitch FRA2.
| Provider | p50 | p95 | p99 |
|---|---|---|---|
| Shreder Fastlane Frankfurt | 0.00 ms | 0.00 ms | 0.00 ms |
| Shyft Frankfurt | 14.03 ms | 59.51 ms | 79.89 ms |
// Compare
Use Geyser/Fastlane when you need structured Yellowstone-compatible updates across transactions, accounts, slots, and blocks.
| Product | Format | Best for | Customer-side work | Latency profile |
|---|---|---|---|---|
| Raw Shreds | Raw UDP shred packets | Teams with custom deshredding and strict latency budgets | Highest: receive, dedupe, reconstruct, decode, filter | Earliest feed; end-to-end speed depends on your decoder |
| Decoded Shreds | Structured transaction stream with filters | Production teams that want shred-level delivery without running a decoder | Low: subscribe and process transaction updates | Low latency with less operational overhead |
| Binary | Transaction data from shreds | Trading systems that want efficient transaction-level delivery | Low: no local decoding required | Lowest-latency transaction-level path for most workloads |
| Geyser gRPC / Fastlane | Yellowstone-compatible gRPC | Existing Geyser users, indexers, wallets, DeFi apps | Low: use existing gRPC tooling | Same interface; Fastlane is optimized for speed |
Choose Fastlane for Geyser semantics and the fastest Shreder gRPC delivery. Choose Binary or Decoded Shreds for shred-level transaction data only.
Not sure which stream to use? Talk to us →
// Production notes
processed for lowest latency; confirmed or finalized for stronger finality.account_required where possible.Shreder Geyser gRPC is a Yellowstone-compatible Solana data stream. Backend systems subscribe to structured updates such as transactions, account changes, slots, blocks, and block metadata over a persistent gRPC connection.
Fastlane is Shreder’s accelerated Geyser gRPC mode. It keeps the same Yellowstone-compatible interface as Regular Geyser but uses Shreder’s custom low-latency implementation to deliver data 2x faster.
No. They are two delivery modes for the same Yellowstone-compatible Geyser gRPC interface. Your client code, protos, filters, and stream handling should remain the same.
Yes. Fastlane is designed as a drop-in Yellowstone-compatible endpoint. Teams using standard Yellowstone clients can migrate by changing the endpoint and token, then validating the same subscription filters.
Choose Regular Geyser for standard delivery with cost-efficient setup. Choose Fastlane when your workload is latency-sensitive and you want Shreder’s fastest gRPC path.
Use Fastlane when you need Yellowstone-compatible Geyser data: account updates, slots, blocks, and transaction statuses. Use Binary for compact serialized transaction bytes from shreds.
Use Raw Shreds for packet-level control and your own decoder. Use Geyser/Fastlane for structured Yellowstone-compatible updates without that infrastructure.
Yes. If your integration uses Yellowstone-compatible Geyser gRPC, migration will take just a few minutes.
Run endpoints from the same machine with the same filters, commitment, and region. Track first-detection share, p50/p95/p99 deltas, and consistency. Use GeyserBench or see the Benchmarks page.
Frankfurt, Amsterdam, New York, London, and Tokyo.
Start from the Shreder console or contact the team.
Use Regular Geyser for reliable Yellowstone-compatible streaming, or Fastlane when you need Shreder’s fastest gRPC delivery. Bring your existing client, choose your region, and benchmark against your current provider.