ThingsBoard Private Cloud provides subscription plans based on the pay-as-you-go model. Main characteristics of the subscription plan are the number of connected devices and amount of messages they produce. However, to keep the environment safe, we introduce certain Entity, API and Rate limits.
Entity Limits
Please see table below to compare the entity limits of the subscription plans.
| Parameter name | Launch | Growth | Scale | Description |
| Devices | 5,000 | 25,000 | 50,000 | Maximum number of devices |
| Assets | 5,000 | 25,000 | 50,000 | Maximum number of assets |
| Customers | 5,000 | 25,000 | 50,000 | Maximum number of customers |
| Users | 5,000 | 25,000 | 50,000 | Maximum number of users |
| Dashboards | 1,000 | 5,000 | 10,000 | Maximum number of scheduler events |
| Scheduler Events | 1,000 | 5,000 | 10,000 | Maximum number of scheduler events |
| Integrations | 30 | 50 | 100 | Maximum number of integrations |
| Converters | 100 | 200 | 400 | Maximum number of integrations |
| Rule Chains | 50 | 100 | 150 | Maximum number of rule chains |
API Limits
Please see table below to compare the API limits of the subscription plans. The values are monthly API limits, unless stated otherwise.
| Parameter name | Launch | Growth | Scale | Description |
| Transport messages | 1B | 5B | 25B | Total number of messages received by any of the Transports (MQTT, HTTP, CoAP, etc) or Integrations |
| Transport data points | 1B | 5B | 25B | Total number of key-value pairs that your telemetry or attribute transport messages contain |
| Rule Engine executions | 5B | 25B | 125B | Total number of any execution of the rule node. Processing of a single telemetry message may cause multiple Rule Engine executions. The platform will also count periodic messages produced by Generator nodes, etc. |
| TBEL executions | 10B | 50B | 250B | Total number of any execution of user defined functions written using TBEL. For example, processing of the “Script” filter or transformation node, invocation of the data converter, etc. |
| JavaScript executions | 200M | 1B | 5B | Total number of any execution of user defined functions written using JS. For example, processing of the “Script” filter or transformation node, invocation of the data converter, etc. |
| Default storage TTL | 365 days | 365 days | 365 days | How many days to store telemetry in the database by default. Configurable upon request. |
| Default alarms TTL | 365 days | 365 days | 365 days | How many days to store alarms in the database by default. Configurable upon request. |
| Default RPC TTL | 1 week | 1 week | 1 week | How many days to store persistent RPC in the database by default. Configurable upon request. |
| Default notifications TTL | 1 week | 1 week | 1 week | How many days to store notifications in the database by default. Configurable upon request. |
| Default debug event TTL | 1 week | 1 week | 1 week | How many days to store debug events in the database by default. Configurable upon request. |
| New Alarms per month | 50K | 75K | 100K | Total number of alarms created per month. |
| Rule Engine executions per message | 20 | 20 | 20 | Maximum number of rule node executions to process single message. |
| Calculated fields per entity | 5 | 5 | 5 | Number of calculated fields per entity. |
| Arguments per calculated field | 10 | 10 | 10 | Maximum number of arguments that may be used in the calculated field. |
| Data points in rolling argument | 1000 | 1000 | 1000 | Maximum number of data points to be stored as part of the calculated field's rolling argument. |
where “K” means 1 thousand, “M” means 1 million, “B” means 1 billion.
Rate Limits
| Parameter name | Launch | Growth | Scale | Description |
| All messages | Up to 2K per second, not exceeding 25K per minute and capped at 1.2M per hour | Up to 10K per second, not exceeding 125K per minute and capped at 6M per hour | Up to 20K per second, not exceeding 600K per minute and capped at 30M per hour | Total number of messages received by any of the transports or integrations for all devices |
| All data points | Up to 2K per second, not exceeding 25K per minute and capped at 1.2M per hour | Up to 10K per second, not exceeding 125K per minute and capped at 6M per hour | Up to 20K per second, not exceeding 600K per minute and capped at 30M per hour | Total number of data points received by any of the transports or integrations for all devices |
| Messages per device | Up to 200 per second, not exceeding 6K per minute and capped at 20K per hour | Up to 200 per second, not exceeding 6K per minute and capped at 20K per hour | Up to 200 per second, not exceeding 6K per minute and capped at 20K per hour | Total number of messages received by any of the transports or integrations for each device separately |
| Data points per device | Up to 200 per second, not exceeding 6K per minute and capped at 20K per hour | Up to 200 per second, not exceeding 6K per minute and capped at 20K per hour | Up to 200 per second, not exceeding 6K per minute and capped at 20K per hour | Total number of data points received by any of the transports or integrations for each device separately |
| All REST requests | Up to 100 per second, not exceeding 2,000 per minute | Up to 100 per second, not exceeding 3,000 per minute | Up to 100 per second, not exceeding 4,000 per minute | Total number of REST API calls received by any of the users |
| REST requests for customer | Up to 50 per second, not exceeding 1,000 per minute | Up to 50 per second, not exceeding 1,000 per minute | Up to 50 per second, not exceeding 1,000 per minute | Total number of REST API calls received by any of the users belong to the particular customer |
| WebSocket updates per session | Up to 1K per second, not exceeding 10K per minute |
Up to 1K per second, not exceeding 10K per minute |
Up to 1K per second, not exceeding 10K per minute |
Total number of messages received by particular WebSocket session |
| WebSocket sessions | 1K | 5K | 10K | Maximum number of concurrent WebSocket sessions |
| WebSocket subscriptions | 10K | 50K | 100K | Maximum number of active subscriptions for all WebSocket sessions |
| WebSocket sessions per customer | 500 | 500 | 500 | Maximum number of active WebSocket sessions per сustomer |
| WebSocket subscriptions per customer | 5K | 5K | 5K | Maximum number of WebSocket subscriptions per сustomer |
| WebSocket Sessions per user | 100 | 100 | 100 | Maximum number of WebSocket sessions per user |
| WebSocket subscriptions per user | 1K | 1K | 1K | Maximum number of WebSocket subscriptions per user |
| WebSocket queue size per session | 500 | 500 | 500 | Maximum size of in-transit messages queue per session |
| Telemetry queries | Up to 20K per 10 seconds, not exceeding 60K per minute | Up to 20K per 10 seconds, not exceeding 60K per minute | Up to 20K per 10 seconds, not exceeding 60K per minute | Total number of telemetry queries received by any of the users WebSocket sessions or REST API calls |