Quotas and limits in Yandex IoT Core
Written by
Updated at July 14, 2025
Yandex IoT Core has the following limits:
- Quotas are organizational constraints that can be changed by support on request.
- Limits are technical constraints of the Yandex Cloud architecture. You cannot change the limits.
If you need more resources, you can increase your quotas in one of the following ways:
- Make a request to increase your quotas.
- Contact support and specify which quotas you want increased and by how much.
To have your request processed, you must have the quota-manager.requestOperator role or higher, e.g., editor or admin.
You can manage your quotas with Cloud Quota Manager.
Quotas
|
Type of limit |
Value |
|
Number of registries per cloud |
10 |
|
Number of devices per cloud |
1,000 |
|
Number of brokers per cloud |
10 |
|
Frequency of sending messages per broker |
50 per second |
|
Number of clients concurrently connected to the broker |
50 |
Limits
| Type of limit | Value |
|---|---|
| Maximum size per message | 256 KB |
| Frequency of sending messages per device | No more than once per second |
| Maximum subtopic name length | 1,024 characters |
| Maximum number of aliases per device | 5 |
Note
Message delivery is not guaranteed if the limits are exceeded.
Other restrictions
- The
Retainflag is not supported. This flag enables the MQTT broker to save the flagged message and send it when subscribing to the topic next time. - Persistent sessions, when the MQTT broker saves information about a client (device or registry) to reconnect faster, are not supported.
- The
QoS 2: Exactly oncequality of service level for MQTT is not supported. - There is no guarantee that the devices or registries with the same ClientID cannot connect to the MQTT broker at the same time.