# Pricing (/platform/pricing)

> Corvus plans compared by request capacity (RPS), transaction capacity (TPS) and which interfaces each one unlocks.



A plan is capacity: a request allowance (RPS), a transaction submission allowance (TPS), and a set of interfaces. You rent in the [Corvus dashboard](https://dashboard.corvus-labs.io), from the presets below or by setting your own RPS and TPS on the Custom plan.

| Plan | Price | Effective hourly | RPC RPS | Submit TPS | Interfaces | For |
| --- | --- | --- | --- | --- | --- | --- |
| Starter | $160/month | $0.22 | 200 | 50 | RPC, gRPC | For smaller production workloads |
| Standard | $325/month | $0.45 | 500 | 125 | RPC, gRPC, aRPC | Balanced throughput and cost |
| Professional (popular) | $400/month | $0.56 | 1,000 | 250 | RPC, gRPC, aRPC | For high-throughput applications |
| Custom | Quoted | Priced on the capacity you choose | Your choice | Your choice | RPC, gRPC, aRPC | Dial in any capacity |

Monthly billing controls. Effective hourly rates use a 720-hour month and are rounded to two decimals. Custom capacity is configured and priced in the [dashboard](https://dashboard.corvus-labs.io); you can choose any RPS and TPS, including capacity above the presets.

RPS and TPS are separate allowances that don't convert into each other. `sendTransaction` costs 0 RPS units and draws on TPS instead.

## What a plan includes

| Plan         |         RPS |         TPS | JSON-RPC & WebSocket | Yellowstone gRPC |         aRPC         |
| ------------ | ----------: | ----------: | :------------------: | :--------------: | :------------------: |
| Starter      |         200 |          50 |           ✓          |         ✓        |           —          |
| Standard     |         500 |         125 |           ✓          |         ✓        |           ✓          |
| Professional |       1,000 |         250 |           ✓          |         ✓        |           ✓          |
| Custom       | Your choice | Your choice |           ✓          |         ✓        | When RPS + TPS ≥ 500 |

**aRPC unlocks when RPS and TPS together reach 500.** The same total applies on a Custom plan, so size with that in mind if you want streams.

Falcon sits outside this table: its TPS allowance attaches to your API key rather than to a plan, and every transaction pays a [tip](/falcon/tips). See [Falcon](/falcon).

An [NFT pass](/platform/nft-pass) is the other way in. Instead of renting one region, a pass carries a fixed high allowance across every region for a monthly renewal. You never need one to rent.

Whichever you pick, you also get:

* **One region**, chosen when you rent, from the five Solana RPC metros: Frankfurt, Amsterdam, London, New York and Tokyo. See [Regions](/platform/regions).
* **IP allowlist access** on the standard regional endpoints; register a public egress IP in the [dashboard](https://dashboard.corvus-labs.io). See [Access & authentication](/platform/access).
* **Support on [Discord](https://discord.gg/corvus-labs)** for API keys, tokens and anything the dashboard doesn't cover.

Call an interface your plan doesn't include and you get HTTP `403`, code `-32003`, prefix `You have no access to this service`.

## What RPS buys

RPS is metered by weighted method cost rather than request count, and every item in a JSON-RPC batch is counted on its own. On a 500 RPS plan:

| Workload                                    | Cost per call | Calls per second at 500 RPS |
| ------------------------------------------- | ------------: | --------------------------: |
| Ordinary reads (`getSlot`, `getBalance`, …) |             1 |                         500 |
| `getAccountInfo`                            |             2 |                         250 |
| `getMultipleAccounts`, 100 accounts         |           200 |                         2.5 |
| `getTransaction`                            |            10 |                          50 |
| `getProgramAccounts`                        |            30 |                        \~16 |

`getMultipleAccounts` is the row that moves: below 800 plan RPS it costs 2 units per account, and from 800 RPS it drops to `ceil(accounts / 20)`, so the same 100-account call on Professional costs 5 units. NFT pass holders get that cheaper rate on any plan. [The formula](/solana-rpc/limits#getmultipleaccounts) has all three cases.

Six scan-style methods also carry a concurrency limit, independent of RPS, so a `getProgramAccounts`-heavy workload can hit `Scan request timed out waiting for concurrency slot` with RPS headroom to spare. The full rules are in [Solana RPC rate limits](/solana-rpc/limits). These weights apply to the shared regional JSON-RPC endpoints.

If your mix doesn't fit any of the presets, see [Custom deployments](/platform/dedicated).

## How billing works

Plans bill monthly in USD. The hourly figure on each card is for comparison, not a separate metered price:

```text
effective hourly rate = monthly price / 720 hours
```

It's rounded to two decimals.

**Custom** isn't a quote request. You set the RPS and TPS you want, including capacity above the Professional preset, and the [dashboard](https://dashboard.corvus-labs.io) prices that configuration before you commit.

## Compare providers

Corvus sells capacity, Helius combines plans with credits, and Triton publishes usage-based pricing. The [normalized RPC cost comparison](/platform/pricing-comparison) puts all three on one axis, with the assumptions, exact values and source links.

Pricing verified **July 25, 2026**.