> ## Documentation Index
> Fetch the complete documentation index at: https://docs.thornode.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Plans and limits

> Read the throughput, concurrency, and streaming limits for a ThorNode access.

Use this page to size a workload against the limits shown for the pass or rental your application uses. The standard tiers are **Flash**, **Classic**, **Elite**, and **Prime**; limits can also be customized for a specific access.

<Note>
  Prices, locations, and limits can change. Read them from the dashboard for the
  access you will use; do not copy values from a screenshot or another access.
</Note>

## Check capacity for a workload

<Steps>
  <Step title="Select the pass or rental">
    Choose the exact active access your application will use. Do not assume two
    accesses with the same tier label have identical current configuration.
  </Step>

  <Step title="Choose a product and location">
    Open **Endpoints** for the selected access and choose from the products and
    locations shown there.
  </Step>

  <Step title="Read activity and published capacity">
    Open **Usage** for current activity and **Limits** for the values shown for
    the selected access.
  </Step>

  <Step title="Test the intended configuration">
    Obtain the target and credential after selecting the access, network, and
    location, then run one low-impact operation.
  </Step>
</Steps>

Run a low-impact test, then keep the workload within the limits shown in the dashboard.

## Understand the monthly and live limits

ThorEdge RPC has no monthly request cap. Throughput and concurrency limits still apply.

Live constraints still apply:

| Limit                     | What it governs                                                            | When it is reached                                                                                              |
| ------------------------- | -------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------- |
| RPC RPS                   | JSON-RPC request throughput                                                | Requests can be throttled; inspect `429` responses and retry volume.                                            |
| Transaction TPS           | Transaction-submission throughput                                          | Submissions can be throttled; bound application concurrency and retries.                                        |
| WebSocket capacity        | Connections, subscriptions, or related concurrent use                      | New work can be rejected; reuse connections and close idle subscriptions.                                       |
| Yellowstone capacity      | Concurrent streams; account and owner keys across live streams for a token | Subscriptions can be rejected; narrow filters and close unused streams.                                         |
| Pulse capacity            | Concurrent streams and total accounts across filters                       | New streams can be rejected; an unfiltered request can be unavailable when the access requires account filters. |
| Raw Shred Stream capacity | Active UDP receiver registrations                                          | A new registration can be rejected; remove registrations no longer in use.                                      |
| Location access           | Locations enabled for a product and access                                 | A location does not appear as an available choice.                                                              |

The dashboard can show additional product-specific constraints. [Read **Usage** and **Limits**](/dashboard/usage-and-limits) for the selected access instead of encoding a tier table into application logic. RPC rate and subscription caps apply per active location token where the published table says so.

Creating extra clients, credentials, reconnect loops, or location targets does not increase the entitlement attached to an access.

## Check the selected access

Products, locations, and capacity vary by pass or rental. Use the options and limits shown for the selected access; RPC access does not automatically include every streaming or transaction-routing product.

## Operate below the live limits

* Leave headroom for bursts and retries instead of targeting the displayed ceiling.
* Bound concurrency and use exponential backoff with jitter for retryable throttling.
* Reuse WebSocket and streaming connections where the protocol permits.
* Keep Yellowstone filters narrow and close streams that are no longer needed.
* Review **Usage** and **Limits** after releases or material traffic changes.
* Contact [ThorNode support](mailto:support@thornode.io) before a traffic increase needs more capacity.

For a `429`, rejected subscription, or other capacity symptom, use the [limit troubleshooting table](/reference/troubleshooting#requests-or-subscriptions-are-rate-limited).

## Next steps

* [Choose and test a location](/reference/locations)
* [Read live usage and capacity in the dashboard](/dashboard/usage-and-limits)
* [Diagnose throttling and availability failures](/reference/troubleshooting)