Overview
Private Solana mainnet RPC, Yellowstone gRPC and shred streams from bare-metal nodes in dedicated regions.
constant-k runs private Solana mainnet nodes on bare-metal servers in dedicated regions. This section covers endpoints, API keys, plan limits and the first request.
Product by task
| Task | Product | Protocol |
|---|---|---|
| Read accounts, balances, blocks or transaction history | Solana RPC | HTTPS |
Read blocks older than the region's ledger with getBlock | Cube Runner | HTTPS |
| Send transactions | Sending Transactions | HTTPS |
| Get pushed updates for a few accounts or signatures | WebSockets | WSS |
| Stream filtered accounts and transactions with low latency | Kaldera gRPC | gRPC |
| See transactions before they execute, without execution results | Turbo Kaldera (aRPC) | gRPC |
| Receive serialized entries, unfiltered | ShredPrism | gRPC |
aRPC, anticipatory RPC, is constant-k's name for pre-execution transaction streaming. Plan availability per product is in the endpoint table.
Pipeline stages
Each product hands data over at a different stage between the leader and the reader, and an earlier stage arrives sooner and says less about the outcome. Data Stages sets out all six stages and the stage each product delivers at.
Turbo Kaldera and Kaldera can run side by side: Turbo Kaldera for the early notification, Kaldera for the executed result.
Key pages
Quickstart
An account, an API key and a first RPC call.
Endpoints
Hostnames and ports for every product and region.
Authentication
Where the API key goes on HTTP, WebSocket and gRPC.
Plans & Limits
Rate, stream and bandwidth limits for each plan.
Data Stages
The stages from shreds to parsed fields, and which product delivers at each one.
Live measurements
constant-k publishes latency and node health for the same nodes that serve customer traffic. See Benchmarks and RPC Status.