Service quotas
Your Cumulocity service includes so-called quotas. These quotas ensure that the service operates within the guarantees of the Cumulocity service-level agreements.
The following types of quotas are used:
- Hard: Services enforce this quota so that it cannot be exceeded.
- Soft: Services are guaranteed to operate within the specified service-level agreements as long as the quotas are not exceeded; however, exceeding the quotas may result in a degraded user experience and no assurance of meeting the service-level agreements.
The quotas listed here reflect the maximum values for the cloud subscriptions unless indicated otherwise. If you’re unsure whether a specific cloud service quota is sufficient for your use case, we recommend reaching out to your sales contact to discuss your needs and explore potential options. Some quotas may be adjustable through professional services, depending on the system dimensioning and your specific requirements. For Edge deployments, consult the Cumulocity Edge documentation.
Platform
The quotas below are listed separately for the Standard Dedicated Environment (SDE) and the Advanced Dedicated Environment (ADE).
General
| Quota | Type | SDE value | ADE value |
|---|---|---|---|
| Number of tenants | Soft | 500 | 2000 |
Microservices
| Quota | Type | SDE value | ADE value |
|---|---|---|---|
| Microservice name length | Hard | 23 | 23 |
| Microservice image size | Hard | 500 MB | 500 MB |
| Threads in a microservice | Hard | 10240 | 10240 |
| Retained log size | Hard | 35 MB | 35 MB |
Domain model
| Quota | Type | SDE value | ADE value |
|---|---|---|---|
| Document size | Hard | 16 MB | 16 MB |
| Document size | Soft | 1 MB | 1 MB |
| Array size within document | Soft | 1000 | 1000 |
| Children of an inventory object | Soft | 1000 | 1000 |
| Property size | Soft | 32 KB | 32 KB |
REST API
| Quota | Type | SDE value | ADE value |
|---|---|---|---|
| API request duration | Hard | 5 minutes | 5 minutes |
| Database query execution | Hard | 2 minutes | 2 minutes |
The database query execution timeout applies to every individual database query triggered by an API request. This limit is independent of the API request duration timeout.
Realtime APIs
| Quota | Type | SDE value | ADE value |
|---|---|---|---|
| MQTT message size (Core MQTT) | Hard | 16 KB | 16 KB |
| Notifications 2.0 message backlog | Hard | 25 MiB | 25 MiB |
| Notifications 2.0 time-to-live | Hard | 36 hours | 36 hours |
| Microservice-based data broker message backlog | Hard | 50 MiB | 50 MiB |
| Microservice-based data broker time-to-live | Hard | 36 hours | 36 hours |
| Streaming Analytics and Streaming Lake offloading message backlog | Hard | 1 GiB | 1 GiB |
MQTT Service
| Quota | Type | SDE value | ADE value |
|---|---|---|---|
| Client identifier length | Hard | 128 bytes | 128 bytes |
| Topic name length | Hard | 256 bytes | 256 bytes |
| Topics | Unlimited | Unlimited | |
| Concurrent client connections (per tenant)1 | Hard | 500 connections | 1000 connections |
| Client connection rate (per tenant)2 | Hard | 100 per second | 100 per second |
| Inbound message publishing rate (per tenant)2 | Hard | 100 per second | 1000 per second |
| Inbound message publishing rate (per client) | Soft | 50 per second | 100 per second |
| Outbound message publishing rate (per tenant)2 | Hard | 50 per second | 100 per second |
| Maximum message size (per tenant) | Hard | 128 KiB | 128 KiB |
| Maximum aggregate throughput (per tenant, connected clients x message size x publishing rate) | Soft | 512 KiB per second | 1 MiB per second |
| Message backlog (per tenant, total for all MQTT topics) | Hard | 1 GiB | 1 GiB |
| Message time-to-live (per tenant) | Hard | 36 hours | 36 hours |
Applications and services
| Quota | Type | SDE value | ADE value |
|---|---|---|---|
| Map tiles | Soft | Policy | Policy |
| Data points in a graph | Hard | 5000 | 5000 |
Protocols
| Quota | Type | SDE value | ADE value |
|---|---|---|---|
| File size for LWM2M bulk registration | Hard | - | 10 MB |
| Concurrent pending LWM2M operations per device | Hard | - | 10 |
| Maximum number of Loriot devices that can be registered per deployment | Soft | - | 40000 |
| Maximum number of Loriot devices that can be registered per tenant | Soft | - | 20000 |
Cloud Remote Access
| Quota | Type | Value |
|---|---|---|
| Concurrent remote access sessions per tenant | Soft | 50 |
| Concurrent remote access sessions per device | Soft | 3 |
| New remote access connection attempts per tenant | Soft | 30/minute |
| Remote access session lifetime | Soft | 4 hours |
See also the Cloud Remote Access service-level agreement.
DataHub 1.0
| Quota | Type | SDE value | ADE value |
|---|---|---|---|
| Number of tenants | Soft | - | 250 |
| Number of Dremio users per tenant | Soft | - | 40 |
| Number of active offloaders per tenant | Soft | - | 100 |
| Number of offloadings per tenant per hour | Soft | - | 20 |
| Offloading frequency | Hard | - | hourly |
| Offloaded leaf properties3 | Soft | - | 6400 |
| Query time out | Soft | - | 4 minutes |
| Query job retention | Hard | - | 1 day |
| Rows in a query job | Hard | - | 1000000 |
| Rows in a high performance query | Soft | - | 1000000 |
| Parallel high performance queries per tenant | Hard | - | 18 |
Additional quotas from the Dremio engine may apply for DataHub customers.
-
These default quotas are set to support reliable operation on Cumulocity’s shared cloud environments. Significantly higher quotas can be configured for dedicated environments. ↩︎
-
MQTT Service hard quotas documented as per tenant can be increased if necessary to support your use case, with any additional usage charged for. ↩︎ ↩︎ ↩︎
-
Leaf properties are properties with elementary types (text, number, boolean). The total count of leaf properties offloaded into the same table should not exceed the limit. ↩︎