Platform
One account across every Corvus product, and the plans, access, regions and limits they all share.
Every Corvus product runs off one account and one dashboard. Rent capacity and a region there, then call the endpoint it hands back. This section covers what the products share; each product keeps its own reference.
What are you building?
| If you want to | Use |
|---|---|
| Read chain state, simulate, or make any standard Solana call | Solana RPC |
| Subscribe to accounts, transactions, slots or blocks | Yellowstone gRPC |
| Submit transactions with low latency over HTTP, QUIC or UDP | Falcon |
| See transactions before they execute, for trading or monitoring | aRPC |
| Process native Solana shreds yourself | Shredstream |
| Call BSC or Polygon | EVM chains |
| Stake SOL, or hold a liquid staking token | Validator & corvusSOL |
Solana RPC runs in five metros; Falcon, aRPC and Shredstream run in all nine. The availability matrix has the breakdown. Choosing by speed rather than by task? The latency stack orders every stream by how early it sees a transaction.
What the products share
Plans & pricing
RPS, TPS, and which interfaces each plan unlocks
Access & authentication
IP allowlist, tokenized URLs, x-token, and transport security
Regions
Nine metros, and which products run in each
Custom deployments
When no preset fits, and what to bring to the conversation
Your plan's RPS drives the limits on the Solana interfaces, and each one documents what it enforces: Solana RPC rate limits, Yellowstone gRPC and aRPC.
Capacity, endpoints and allowlisted egress IPs all live in the dashboard. API keys and tokens come from onboarding, and we're on Discord when you need a human.