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	Notes
Maximum number of concurrent connections	1000	NO
Maximum default authentication entries	2000	NO
Maximum default authorization entries	2000	NO
Maximum authorization entries for a single username or client ID	100	NO	As the number of entries increases, performance may degrade.
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
Maximum retained message publish rate per client	1000/s	NO
Maximum retained message publish rate per cluster	1000/s	NO
Client ID maximum length	1024	NO
Maximum subscriptions per client	10	NO
Maximum topic levels per subscription	10	NO
Maximum deployment TPS	1000/s	NO
Maximum subscription TPS per client	1000/s	NO
Maximum publish TPS per client	10/s	NO
Maximum combined publish and subscribe TPS	1000	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	10/s	NO
Number of deployments	Up to 2	YES	Create an extra Serverless deployment by adding a payment method.
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

Dedicated and BYOC

Quotas	Default Value	Adjustable	Requires Deployment Restart	Notes
Maximum default authentication entries	Session tier * 2	-	-	It is recommended to use external authentication if the credential entries exceed 100,000.
Maximum default authorization entries	Session tier * 2	-	-	It is recommended to use external authorization if the credential entries exceed 100,000.
Maximum authorization entries for a single username or client ID	100	NO	NO	As the number of credential entries increases, performance may degrade.
External authentication supported at the same time	2	NO	-
Anonymous access	No anonymous access	YES	NO
Maximum message queue length	1000	YES	NO	The number can be adjusted to the same as the session tier.
Maximum message size	1 MB	YES	NO	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.
Session expiry time（MQTT 3.x）	2 hours	YES	NO
Maximum retained messages	Session tier * 10	NO	-	For Dedicated deployments, the retained message quota is fixed at 10 times the number of connections and cannot be modified. However, the total number of retained messages is capped at 500,000. Even if the number of connections exceeds 50,000, the maximum limit for retained messages remains 500,000.
Maximum size of a retained message	1 MB	YES	NO
Maximum retained message publish rate per cluster	1000/s	YES	NO
Maximum retained message deliver rate per cluster	1000/s	YES	NO
Maximum message publish rate per client	1500/s	YES	YES
Retained message expiry interval	Never	YES	NO
Disk storage (Dedicated Plan)	10 GB	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/connectors can be created in Data Integration	10	NO	-
Maximum rules can be created in Data Integration	50	NO	-
Maximum actions (Sink) can be created in Data Integration	50	NO	-
Maximum actions (Source) can be created in Data Integration	50	NO	-
Maximum schemas can be created in Schema Registry (Dedicated Plan)	50	NO	NO
Number of deployments	3	YES	NO
Number of subaccounts	20	NO	-