Opens in a new tab

Kaldera gRPC

Solana Yellowstone gRPC Streaming

Kaldera is constant-k's enhanced Yellowstone gRPC service for Solana: account, transaction, slot, block and entry streams delivered over gRPC from dedicated bare-metal RPC nodes in New York, Frankfurt and Amsterdam. It speaks the standard Yellowstone (Geyser) protocol your tooling already understands — then adds leader shred injection, a per-subscriber fanout layer and an optional pre-execution fast path on top.
Kaldera is included on the Blade Runner and Nexus plans. Compare plans on the pricing page, check per-method caps on plan limits, and watch the live p50 latency of the exact nodes serving you on our Solana RPC benchmarks.

What Kaldera Adds to Yellowstone gRPC

Shred-Accelerated Updates

Standard Yellowstone gRPC emits updates after the validator executes a block. Kaldera additionally ingests leader shreds as they arrive, so hot data reaches your stream ahead of the normal Turbine propagation path. When you are racing for a landing slot or watching a pool for the first state change, those milliseconds are the edge.

Standard Filters, Generous Caps

Filter your stream by account owners, addresses, transaction inclusion, commitment level and data slices using stock SubscribeRequest filters, no proprietary query language. Reconnections are painless too. Each region keeps up to 24 hours of slot replay, so a dropped connection does not mean a gap in your data. zstd compression is available on every stream.

A Dedicated Lane for Every Subscriber

constant-k's custom gRPC fanout gives each subscription its own isolated stream from Yellowstone. A slow consumer elsewhere can never stall your feed, and your bandwidth allocation is yours alone: 37.5 MB/s on Blade Runner, 150 MB/s on Nexus.

Run by Operators, Not Resellers

Kaldera runs on bare-metal servers we build, own and tune ourselves in New York, Frankfurt and Amsterdam — the same nodes whose latency we publish live on our benchmarks page. No white-labelled capacity, no shared firehose, no mystery middle-boxes between you and the chain.

Coming From Another Provider?

Kaldera is hosted Yellowstone gRPC: filtered, post-execution streams of accounts, transactions, slots, blocks and entries over the standard Subscribe API. Helius calls the equivalent LaserStream gRPC, Triton One calls it Dragon's Mouth, and QuickNode calls it Solana gRPC. Any Yellowstone client connects unchanged: set the endpoint and send your API key as x-token.

Need it faster? Try Turbo-Kaldera - Pre-Execution with SubscribeDeshred

For workloads where seeing the pipeline early beats seeing it enriched, Kaldera can serve your regular Subscribe request from a shred-reassembly path that surfaces transactions before execution — two stages earlier in the transaction lifecycle. It is raw and unconfirmed by design, and it is there when you want it.
Turbo Kaldera (aRPC)

Connect in Minutes

Kaldera speaks the stock Yellowstone protocol, so any Yellowstone client works unchanged. A minimal TypeScript example with @triton-one/yellowstone-grpc:
import Client, { CommitmentLevel } from "@triton-one/yellowstone-grpc";

const client = new Client(
  "https://kaldera-newyork.constant-k.com", // or kaldera-frankfurt / kaldera-amsterdam
  process.env.CK_API_KEY,                   // sent as the x-token header
  undefined,
);
await client.connect();                     // required before subscribing

const stream = await client.subscribe({
  commitment: CommitmentLevel.PROCESSED,
  accounts: {
    pools: {
      account: [],
      owner: ["675kPX9MHTjS2zt1qfr1NYHuzeLXfQM9H24wFSUt1Mp8"], // Raydium AMM v4
      filters: [],
    },
  },
  // every map must be present, even when empty
  transactions: {}, transactionsStatus: {}, slots: {},
  blocks: {}, blocksMeta: {}, entry: {}, accountsDataSlice: [],
});

stream.on("data", (update) => {
  console.log(update.filters, update.account?.account?.pubkey);
});