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

General

Quota Type Value
Tenant amount Soft 2000

Microservices

Quota Type Value
Microservice name length Hard 23
Microservice image size Hard 500 MB
Threads in a microservice Hard 10240
Retained log size Hard 35 MB

Domain model

Quota Type Value
Document size Hard 16 MB
Document size Soft 1 MB
Array size within document Soft 1000
Children of an inventory object Soft 1000

REST API

Quota Type Value
Maximum API request duration Hard 5 minutes

Realtime APIs

Quota Type Value
MQTT message size Hard 16 KB
Notifications 2.0 message backlog Hard 25 MB
Notifications 2.0 time-to-live Hard 36 hours
Microservice-based data broker message backlog Hard 50 MB
Microservice-based data broker time-to-live Hard 36 hours

Applications and services

Quota Type Value
Devices shown on the Cockpit home page map Hard 100
Data points in a graph Hard 5000

Protocols

Quota Type Value
File size for LWM2M bulk registration Hard 10 MB
Concurrent pending LWM2M operations Hard 10