# Platform (/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.

<Cards>
  <Card title="Quickstart" href="/platform/quickstart" description="Rent a node, allowlist your IP, make your first call. Two minutes." />
</Cards>

## What are you building?

| If you want to                                                  | Use                                          |
| --------------------------------------------------------------- | -------------------------------------------- |
| Read chain state, simulate, or make any standard Solana call    | [Solana RPC](/solana-rpc)                    |
| Subscribe to accounts, transactions, slots or blocks            | [Yellowstone gRPC](/solana-rpc/grpc)         |
| Submit transactions with low latency over HTTP, QUIC or UDP     | [Falcon](/falcon)                            |
| See transactions before they execute, for trading or monitoring | [aRPC](/arpc)                                |
| Process native Solana shreds yourself                           | [Shredstream](/platform/shredstream)         |
| Call BSC or Polygon                                             | [EVM chains](/platform/evm)                  |
| Stake SOL, or hold a liquid staking token                       | [Validator & corvusSOL](/platform/validator) |

Solana RPC runs in five metros; Falcon, aRPC and Shredstream run in all nine. The [availability matrix](/platform/regions#product-availability-by-metro) has the breakdown. Choosing by speed rather than by task? The [latency stack](/platform/latency-stack) orders every stream by how early it sees a transaction.

## What the products share

<Cards>
  <Card title="Plans & pricing" href="/platform/pricing" description="RPS, TPS, and which interfaces each plan unlocks" />

  <Card title="Access & authentication" href="/platform/access" description="IP allowlist, tokenized URLs, x-token, and transport security" />

  <Card title="Regions" href="/platform/regions" description="Nine metros, and which products run in each" />

  <Card title="Custom deployments" href="/platform/dedicated" description="When no preset fits, and what to bring to the conversation" />
</Cards>

Your plan's RPS drives the limits on the Solana interfaces, and each one documents what it enforces: [Solana RPC rate limits](/solana-rpc/limits), [Yellowstone gRPC](/solana-rpc/grpc/limits) and [aRPC](/arpc/limits).

Capacity, endpoints and allowlisted egress IPs all live in the [dashboard](https://dashboard.corvus-labs.io). API keys and tokens come from onboarding, and we're on [Discord](https://discord.gg/corvus-labs) when you need a human.