Quotas and Limits
The EMQX Platform sets default quotas (or limits) for each deployment and the default value of some of the quotas can be adjusted. The following tables show the default value of the quotas in different deployments and whether they can be adjusted. If you need to adjust the quotas, please contact us.
Serverless
| Quotas | Default Value | Adjustable |
|---|---|---|
| Maximum internal authentication entries | 2000 | NO |
| Maximum internal authorization entries | 2000 | NO |
| Anonymous access | No anonymous access | NO |
| Maximum message queue length | 1000 | NO |
| Maximum message size | 1 MB | NO |
| Session expiry time（MQTT 3.x） | 2 hours | NO |
| Maximum retained messages | 2000 | NO |
| Maximum size of a retained message | 1 MB | NO |
| Retained message expiry interval | Never | NO |
| Client ID maximum length | 1024 | NO |
| Maximum subscriptions for a single client | 10 | NO |
| Maximum deployment TPS | 1000/s | NO |
| Maximum Topic Levels | 10 | NO |
| Maximum single-client subscription TPS | 1000/s | NO |
| Maximum single-client publishing TPS | 10/s | NO |
| TCP connect timeout | 10s | NO |
| Customized TLS/SSL configuration | Not support | NO |
| TLS version | 1.2 and 1.3 | NO |
| TLS encryption algorithm | - | NO |
| Maximum API QPS | 100/s | NO |
| Number of deployments | Up to 2 [*1] | YES |
| Number of subaccounts | 20 | NO |
| Maximum number of connectors created in data integration | 2 | NO |
| Maximum number of rules created in data integration | 4 | NO |
| Maximum number of actions created in data integration | 4 | NO |
[1] Create an extra Serverless deployment by adding a payment method.
Dedicated, Premium and BYOC
| Quotas | Default Value | Adjustable | Requires Deployment Restart |
|---|---|---|---|
| Maximum internal authentication entries | Session tier * 2 [*1] | - | - |
| Maximum internal authorization entries | Session tier * 2 [*2] | - | - |
| External authentication supported at the same time | 2 | NO | - |
| Anonymous access | No anonymous access | YES | NO |
| Maximum message queue length | 1000 | YES[*3] | NO |
| Maximum message size | 1 MB | YES[*4] | NO |
| Maximum message size (Premium Plan) | 100 KB | NO | - |
| Session expiry time（MQTT 3.x） | 2 hours | YES | NO |
| Maximum retained messages | Session tier * 10 | NO | - |
| Maximum size of a retained message | 1 MB | YES | NO |
| Maximum size of a retained message (Premium Plan) | 100 KB | NO | - |
| Retained message expiry interval | Never | YES | NO |
| Client ID maximum length | 1024 | YES | YES |
| Maximum Topic Levels | 16 | YES | NO |
| Maximum API QPS | 100/s | NO | - |
| TCP connect timeout | 10s | YES | YES |
| TLS version | 1.2 and 1.3 | NO | YES |
| TLS encryption algorithm | - | YES | YES |
| Maximum resources that can be created in Data Integration | 10 | YES | NO |
| Maximum rules that can be created in Data Integration | 50 | YES | NO |
| Maximum actions that can be created in Data Integration | 50 | YES | NO |
| Number of deployments | 3 | YES | NO |
| Number of subaccounts | 20 | NO | - |
[1] It is recommended to use external authentication if the credentials are more than 100,000.
[2] It is recommended to use external authentication if the credentials are more than 100,000.
[3] The number can be adjusted to the same as the session tier.
[4] The maximum size can be adjusted to 10 MB. Due to deployment bandwidth limitations, the maximum TPS will be affected. In the case of transmitting 10 MB-sized MQTT messages, the TPS of the deployed will shrink to 100/s.