# CU and rate limits

This guide explains how limits work across all available plans, helping you understand what’s included and how to choose the option that best fits your current workload and future growth.

{% hint style="success" %}

* **Shared Nodes** operate on a system of limits defined by Compute Units (**CUs**) and Requests Per Second (**RPS**). Each plan also determines how many access tokens you can generate.
* With **Dedicated Nodes**, you’re not limited by CUs or RPS.
  {% endhint %}

***

### Shared node limits

GetBlock’s shared node service is subject to several usage limits. These are the key limits that directly affect costs and performance:

* [**CU (Compute Units)**](https://docs.getblock.io/getting-started/plans-and-limits/what-counts-as-a-cu): Measures the computational effort required to process requests. Different shared node plans include a varying number of CUs that you can use in a month.
* **RPS (Requests Per Second)**: Each plan enforces a maximum number of requests you can send every second. While you’re not billed per request, staying within this limit is critical to maintaining optimal service quality.
* [**Access Tokens**](https://docs.getblock.io/getting-started/authentication-with-access-tokens)**:** Access tokens are unique identifiers used to authenticate your connection to GetBlock’s node infrastructure, generated when you create an endpoint. The limitation on your plan determines how many of these access tokens (and therefore endpoints) you can create.

<table><thead><tr><th width="120.7734375">Plan</th><th width="90.09765625">Free</th><th width="116.25">Starter</th><th width="124.421875">Advanced</th><th width="125.66015625">Pro</th><th>Enterprise</th></tr></thead><tbody><tr><td><a data-footnote-ref href="#user-content-fn-1">Price/month</a></td><td>$0</td><td>$49</td><td>$199</td><td>$499</td><td>from $999</td></tr><tr><td>CU Allocation</td><td>50k/day</td><td>50M/month</td><td>220M/month</td><td>600M/month</td><td>Custom</td></tr><tr><td>RPS Limit</td><td>20 RPS</td><td>100 RPS</td><td>300 RPS</td><td>500 RPS</td><td>Custom</td></tr><tr><td>Access Tokens</td><td>2</td><td>10</td><td>25</td><td>50</td><td>Custom</td></tr><tr><td>Extra CU Purchase</td><td>❌</td><td>✅</td><td>✅</td><td>✅</td><td>✅</td></tr></tbody></table>

To see the full comparison table, navigate to <https://getblock.io/pricing/>.

{% hint style="info" %}
Your **balance of CUs for Shared Nodes** is distributed on **all endpoints** added under the ‘Shared nodes’ tab.
{% endhint %}

{% tabs %}
{% tab title="1) Free plan" %}
The plan is ideal if you’re **just starting out** and do not have complex calls or large request volumes.

<figure><img src="https://3589185681-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFOeg95CadVyFvyLi70Bh%2Fuploads%2Fgit-blob-38b94a66a77f4b108ad9c6087ae7b21587c9dd2e%2FFree_widget_upd.svg?alt=media" alt="GetBlock&#x27;s free RPC node plan limits"><figcaption></figcaption></figure>

* **CU**: 50,000/day
* **Throughput**: 20 requests per second (RPS)
* **Access Tokens**: 2

{% hint style="warning" %}
**Compute Units** are **renewed daily**, but unused CUs cannot be transferred to the next day.
{% endhint %}

Clients who want to increase their usage limits can choose between the higher-tier options.
{% endtab %}

{% tab title="2) Starter plan" %}
This is a monthly subscription designed for use cases that are growing beyond the free tier. It offers a **significant increase in CU** compared to the Free plan.

<figure><img src="https://3589185681-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFOeg95CadVyFvyLi70Bh%2Fuploads%2Fgit-blob-14ac39b19b2bddcc2bb90531bdb4a530e2030c71%2FStarter_widget_upd.svg?alt=media" alt="Starter plan limits for Shared RPC nodes by GetBlock"><figcaption></figcaption></figure>

* **CU**: 50M per month (\~1.6M/day)
* **Throughput**: 100 requests per second (RPS)
* **Access Tokens**: 10
* Additional CU packages can be purchased as needed.
  {% endtab %}

{% tab title="3) Advanced plan" %}
The Advanced Plan is a **mid-to-upper tier, production-ready** plan, suitable for moderate-to-high traffic applications.

<figure><img src="https://3589185681-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFOeg95CadVyFvyLi70Bh%2Fuploads%2Fgit-blob-345e33687d96765cc250193eecf777efcfc7ff76%2FAdvanced_widget_upd.svg?alt=media" alt=""><figcaption></figcaption></figure>

* **CU**: 220M per month (\~7.2M/day)
* **Throughput**: 300 requests per second (RPS)
* **Access Tokens**: 25
* Add extra compute units (CU) to your account balance when needed without switching plans
  {% endtab %}

{% tab title="4) Pro plan" %}
The Pro Plan is built for applications that need significantly **higher throughput** and **increased resource availability** compared to lower tier plans.

<figure><img src="https://3589185681-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFOeg95CadVyFvyLi70Bh%2Fuploads%2Fgit-blob-b6acbce1cdf9ad2543123ededc4f2c026bb9a38a%2FPro_widget_upd.svg?alt=media" alt="RPC node with higher-limit access"><figcaption></figcaption></figure>

* **CU**: 600M per month (\~20M/day)
* **Throughput**: 500 requests per second (RPS)
* **Access Tokens**: 50
* Purchase additional CU packages when required
  {% endtab %}

{% tab title="5) Enterprise plan" %}
The Enterprise plan is **fully customizable** with tailored CU allocations, rate limits, and access tokens to meet exceptionally high call volumes and performance requirements.

<figure><img src="https://3589185681-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFOeg95CadVyFvyLi70Bh%2Fuploads%2Fgit-blob-190a8ae8b91018794d78011a51db7032ebf5066f%2FEnterprise_widget.svg?alt=media" alt="GetBlock&#x27;s Enterprise plan with custom usage limit settings"><figcaption></figcaption></figure>

* **CU**: Custom monthly allocation based on your demands
* **Throughput**: Custom
* **Access Tokens**: Custom
* Additional CU packages can be purchased on demand
  {% endtab %}
  {% endtabs %}

***

#### Managing unused & extra CUs

If you don’t use all your allocated CUs within a month, the unused amount **will carry over to the next month** as long as **your subscription is** **active and renewed**. If your subscription expires or is not renewed on time, the remaining CUs will be lost.

{% hint style="success" %}
If your demand exceeds the included limits, you can **purchase extra CU packages**. This means that even within a given plan, there’s room for scaling without an immediate need to move to a higher tier.

* [Top up CUs and boost limits](https://docs.getblock.io/getting-started/plans-and-limits/top-up-cus-and-boost-limits)
  {% endhint %}

***

### Dedicated node limits

Our Dedicated Node service is perfect for teams and projects that demand absolute freedom from rate limits and CU monitoring.

<figure><img src="https://3589185681-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFOeg95CadVyFvyLi70Bh%2Fuploads%2Fgit-blob-f7d424fbfdc0117a75e460c33da080880ca6f911%2FDedic_widget.svg?alt=media" alt="Dedicated node for scalable and unlimited RPC node access"><figcaption></figcaption></figure>

* **CU**: Unlimited
* **Rate**: Unlimited

***

If you’re unsure which plan best fits your needs, our team is ready to help! [Contact our support team](https://getblock.io/contact/) or visit our [Choosing your plan](https://docs.getblock.io/getting-started/plans-and-limits/choosing-your-plan) page for more information.\\

[^1]: Prices are based on monthly billing. Opt for **annual subscriptions** to save up to **$200 per month**


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.getblock.io/getting-started/plans-and-limits/cu-and-rate-limits.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
