# Resource-based limits

The limits on this page apply to accounts on [resource-based pricing](https://ably.com/docs/platform/pricing/resource-based.md). Accounts on [MAU pricing](https://ably.com/docs/platform/pricing.md) have different [limits](https://ably.com/docs/platform/pricing/limits.md).

The [types of limit](https://ably.com/docs/platform/pricing/limits.md#types), [how to view them](https://ably.com/docs/platform/pricing/limits.md#view) and [what happens when you exceed one](https://ably.com/docs/platform/pricing/limits.md#hitting) are the same under both pricing models. Under resource-based pricing, Ably will also contact you if your usage consistently exceeds the limits of your package, to let you know that you need to upgrade.

## Application limits 

Application limits relate to the quantity of resources that can be created per account.

| Application limit | Free | Standard | Pro | Enterprise |
| ----------------- | ---- | -------- | --- | ---------- |
| **Number of apps (per account)**<p>*the maximum number of applications that can be created per account*</p> | 100 | 100 | 100 | 100 |
| **Number of API keys (per account)**<p>*the maximum number of API keys that can be created per account*</p> | 100 | 100 | 100 | 100 |
| **Number of rules (per account)**<p>*the maximum number of rules that can be created per account*</p> | 100 | 100 | 100 | 100 |
| **Number of namespaces (per account)**<p>*the maximum number of namespaces that can be created per account*</p> | 100 | 100 | 100 | 100 |

## Message limits 

Message limits relate to the number, rate and bandwidth of messages consumed across your account. See [how messages are counted](https://ably.com/docs/platform/pricing/message-counting.md) for which operations count as a message. Message count limits and data transfer (bandwidth) limits are enforced separately - exceeding one does not affect the other.

| Message limit | Free | Standard | Pro | Enterprise |
| ------------- | ---- | -------- | --- | ---------- |
| **Message rate (per second)**<p>*the maximum rate at which messages can be published and received across your account each second*</p> | 500 | 2,500 | 10,000 | Unlimited |
| **Messages (per month)**<p>*the maximum number of messages that can be sent and received across your account each month*</p> | 6,000,000 | Unlimited | Unlimited | Unlimited |
| **Message count (per hour)**<p>*the total number of messages that can be sent across an account per hour*</p> | 250,000 | 5,208,000 | 20,833,000 | Unlimited |
| **Message bandwidth rate (per second, KiB)**<p>*the maximum rate at which data can be transferred through messages each second, in KiB*</p> | 2,384 | 11,921 | 47,684 | Unlimited |
| **Message bandwidth (hourly, GiB)**<p>*the maximum amount of data that can be transferred through messages each hour, in GiB*</p> | 1.2 | 24.8 | 99.3 | Unlimited |
| **Message bandwidth (monthly, GiB)**<p>*the maximum amount of data that can be transferred through messages each month, in GiB*</p> | 28.6 | 1,192 | 4,768  | Unlimited |
| **Max message size (KiB)**<p>*the maximum size of a single published message*</p> | 64 | 64 | 256 | 256 |
| **Default history TTL (hours)**<p>*the default time that a message or presence message can be retrieved from history*</p> | 24 | 72 | 72 | 72 |
| **Max history / storage TTL (days)**<p>*the maximum time that a message or presence message can be retrieved from history*</p> | 1 | 30 | 365 | 365 |

## Channel limits 

Channel limits relate to the number, rate and membership of [channels](https://ably.com/docs/channels.md) on your account. See [why concurrent channel limits exist](https://ably.com/docs/platform/pricing/limits.md#concurrent-limits) for the reasoning behind them.

| Channel limit | Free | Standard | Pro | Enterprise |
| ------------- | ---- | -------- | --- | ---------- |
| **Concurrent channels**<p>*the maximum number of channels that are active simultaneously at any point*</p> | 200 | 10,000 | 50,000 | Unlimited |
| **Default last message on channel TTL (days)**<p>*the default period that the last message on a channel is stored for, when enabled*</p> | 1 | 30 | 365 | 365 |
| **Channel creation rate (per second)**<p>*the maximum rate at which channels can be created across an account*</p> | 42 | 250 | 500 | Custom |
| **Message publish rate per channel (per second)**<p>*the maximum rate at which messages can be published for each channel*</p> | 50 | 50 | 50 | 50 |
| **Message bandwidth per channel (per second)**<p>*the maximum total size of all messages published to a channel per second*</p> | 1024 KiB | 1024 KiB | 1024 KiB | 1024 KiB |
| **Presence members per channel**<p>*the maximum number of clients that can be simultaneously present on a channel*</p> | 200 | 200 | 200 | 200 |
| **Presence members per channel with [server-side batching](https://ably.com/docs/messages/batch.md#server-side) enabled**<p>*the maximum number of clients that can be simultaneously present on a channel when server-side batching is enabled*</p> | 200 | 5,000 | 10,000 | 20,000 |
| **Total object size per channel(MB)**<p>*the maximum aggregate size of all objects on a channel*</p> | 6.5 | 6.5 | 6.5 | 6.5 |

## Connection limits 

Connection limits relate to the realtime [connections](https://ably.com/docs/connect.md) made to Ably from your account.

| Connection limit | Free | Standard | Pro | Enterprise |
| ---------------- | ---- | -------- | --- | ---------- |
| **Concurrent connections**<p>*the maximum number of realtime clients connected to Ably simultaneously at any point*</p> | 200 | 10,000 | 50,000 | Unlimited |
| **New connection rate (per second)**<p>*the maximum rate at which new realtime connections can be made to Ably across an account*</p> | 42 | 250 | 500 | Custom |
| **Inbound message rate (per second)**<p>*the maximum rate at which messages can be published by a realtime connection*</p> | 50 | 50 | 50 | 50 |
| **Outbound message rate (per second)**<p>*the maximum rate at which messages can be received by a realtime connection*</p> | 50 | 50 | 50 | 50 |
| **Number of channels per connection**<p>*the maximum number of channels that each connection can be attached to*</p> | 200 | 200 | 200 | 200 |
| **Connection state TTL**<p>*the maximum duration that Ably will preserve the state of a dropped connection for*</p> | 2 mins | 2 mins | 2 mins | 2 mins |

## Integration limits 

Integration limits relate to the rate and concurrency of [webhooks](https://ably.com/docs/platform/integrations/webhooks.md), [queues](https://ably.com/docs/platform/integrations/queues.md) and [Firehose](https://ably.com/docs/platform/integrations/streaming.md).

| Integration limit | Free | Standard | Pro | Enterprise |
| ----------------- | ---- | -------- | --- | ---------- |
| **Integration rate (per second)**<p>*the maximum rate at which integrations can be executed, or streamed*</p> | 250 | 250 | 1,000 | Custom |
| **Webhook concurrency**<p>*the maximum number of unbatched webhook requests that can be in-flight at any one time from a given source*</p> | 25 | 25 | 100 | Custom |
| **Webhook batch size**<p>*the maximum number of webhook events that can be sent per batch*</p> | 50 | 100 | 100 | 100 |
| **Webhook batch concurrency**<p>*the maximum number of webhook batches that can be processed at the same time*</p> | 1 | 1 | 1 | 1 |
| **Max number of queues (per account)**<p>*the maximum number of queues that can be created per account*</p> | 5 | 10 | 50 | 100+ |
| **Max queue length**<p>*the maximum number of messages that can be stored in queues whilst waiting to be consumed. This value is shared between all queues in an account*</p> | 50,000 | 50,000 | 50,000 | 50,000 |
| **Queue publish rate (per second)**<p>*the maximum rate at which messages can be published to all queues across your account*</p> | 250 | 250 | 1,000 | Custom |
| **Queue TTL (hours)**<p>*the maximum time that a message is stored in a queue for, before being transferred to the dead letter queue*</p> | 24 | 24 | 24 | 24 |

## API limits 

API request limits are the maximum number of [REST API](https://ably.com/docs/api/rest-api.md) requests, [Control API](https://ably.com/docs/platform/account/control-api.md) requests and [token requests](https://ably.com/docs/auth/token.md) that can be made to Ably.

| API request limit | Free | Standard | Pro | Enterprise |
| ----------------- | ---- | -------- | --- | ---------- |
| **HTTP API requests (per hour)**<p>*the maximum number of HTTP API requests that can be made to Ably per hour, excluding token requests*</p> | 25,000 | 521,000 | 2,083,300 | Custom |
| **HTTP API request rate (per second)**<p>*the maximum rate at which HTTP API requests can be made to Ably*</p> | 50 | 362 | 1,447 | Custom |
| **Token requests (per hour)**<p>*the maximum number of token requests that can be made to Ably per hour*</p> | 60,000 | 360,000 | 720,000 | Custom |
| **Token request rate (per second)**<p>*the maximum rate at which token requests can be made*</p> | 50 | 250 | 500 | Custom |
| **Control API: authenticated account requests (per hour)**<p>*the maximum number of requests that can be made to the Control API, per hour, from authenticated users*</p> | 4000 | 4000 | 4000 | 4000 |
| **Control API: authenticated access token requests (per hour)**<p>*the maximum number of requests that can be made to the Control API, per hour, for each access token*</p> | 2000 | 2000 | 2000 | 2000 |
| **Control API: unauthenticated requests (per hour)**<p>*the maximum number of requests that can be made to the Control API, per hour, from unauthenticated users*</p> | 60 | 60 | 60 | 60 |

## Related Topics

- [Overview](https://ably.com/docs/platform/pricing/resource-based.md): Understand Ably's resource-based pricing model: the packages, how messages, channel minutes and connection minutes are charged, and how you are billed.
- [Migrate to MAU pricing](https://ably.com/docs/platform/pricing/resource-based/migrate.md): How to move an account from resource-based pricing to MAU pricing: upgrade your SDKs, identify your users with a clientId, estimate your MAUs and switch packages.

## Documentation Index

To discover additional Ably documentation:

1. Fetch [llms.txt](https://ably.com/llms.txt) for the canonical list of available pages.
2. Identify relevant URLs from that index.
3. Fetch target pages as needed.

Avoid using assumed or outdated documentation paths.