ThingsBoars Cloud provides subscription plans based on the pay-as-you-go model. Main characteristics of the subscription plan are: entity limits, api limits, white-labeling and the level of support you get.
Entity Limits
Please see table below to compare the entity limits of the subscription plans.
| Parameter name | Maker | Prototype | Startup | Business | Description |
| Devices | 30 | 100 | 500 | 1000 | Maximum number of devices |
| Assets | 30 | 100 | 500 | 1000 | Maximum number of assets |
| Customers | 2 | 50 | 100 | 500 | Maximum number of customers |
| Users | 5 | 50 | 100 | 500 | Maximum number of users |
| Dashboards | 25 | 100 | 200 | 500 | Maximum number of dashboards |
| Rule chains | 5 | 20 | 50 | 100 | Maximum number of rule chains |
| Integrations | 1 | 5 | 10 | 20 | Maximum number of integrations |
| Converters | 5 | 25 | 50 | 100 | Maximum number of converters |
| Scheduler events | 5 | 20 | 50 | 100 | Maximum number of scheduler events |
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 | Maker | Prototype | Startup | Business | Description |
| Transport messages | 5M | 50M | 250M | 500M | Total number of messages received by any of the Transports (MQTT, HTTP, CoAP, etc) or Integrations |
| Transport data points | 10M | 100M | 500M | 1B | Total number of key-value pairs that your telemetry or attribute transport messages contain |
| Rule Engine executions | 25M | 250M | 1B | 2B | 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. |
| JavaScript executions | 1M | 10M | 50M | 100M | Total number of any execution of user defined functions. For example, processing of the “Script” filter or transformation node, invocation of the data converter, etc. |
| Default storage TTL | 60 days | 180 days | 365 days | 365 days | Default value of the "time to live" parameter that is used to store time-series data. You may overwrite the default value in the "Save Timeseries" rule node or using "TTL" metadata field of your message. This allows you to optimize storage consumption. The maximum allowed value of TTL is 5 years. For example, you may store "raw" data for 3 month and aggregated data for 3 years |
| Data point storage days | 300M | 10B | 100B | 200B | Data points storage days are calculated for all time-series data points that are stored to the database. Platform multiplies number of data points by the number of days those data points will be stored. The TTL parameter is used to extract amount of days to store the data. For example, if you store 1M data points for 30 days, this is 30M storage data point days |
| Alarms TTL | 60 days | 180 days | 365 days | 365 days | How many days to store alarms in the database |
| RPC TTL | 60 days | 180 days | 365 days | 365 days | How many days to store persistent RPC in the database |
| Alarms | 200 | 4K | 20K | 40K | Total number of alarms created per month |
| Emails | 100 | 2K | 10K | 40K | Total number of emails sent |
| SMS | 0 | 100 | 500 | 1000 | Total number of SMS sent |
where “K” means 1 thousand, “M” means 1 million, “B” means 1 billion.
Rate Limits
| Parameter name | Maker | Prototype | Startup | Business | Description |
| All Transport messages (Tenant) | Up to 200 per second, not exceeding 6,000 per minute, and capped at 140,000 per hour |
Up to 2,000 per second, not exceeding 60,000 per minute, and capped at 1,400,000 per hour |
Up to 10,000 per second, not exceeding 300,000 per minute, and capped at 6,000,000 per hour |
Up to 20,000 per second, not exceeding 600,000 per minute, and capped at 12,000,000 per hour |
Total number of messages received by any of the transport microservices for all devices that belong to the tenant |
| Telemetry Transport messages (Tenant) | Up to 100 per second, not exceeding 3,000 per minute, and capped at 70,000 per hour |
Up to 1,000 per second, not exceeding 30,000 per minute, and capped at 700,000 per hour |
Up to 5,000 per second, not exceeding 150,000 per minute, and capped at 3,500,000 per hour |
Up to 10,000 per second, not exceeding 300,000 per minute, and capped at 7,000,000 per hour |
Total number of telemetry messages received by any of the transport microservices for all devices that belong to the tenant |
| Telemetry Transport data points (Tenant) | Up to 200 per second, not exceeding 6,000 per minute, and capped at 140,000 per hour |
Up to 2,000 per second, not exceeding 60,000 per minute, and capped at 1,400,000 per hour |
Up to 10,000 per second, not exceeding 300,000 per minute, and capped at 7,000,000 per hour |
Up to 20,000 per second, not exceeding 600,000 per minute, and capped at 14,000,000 per hour |
Total number of telemetry data points received by any of the transport microservices for all devices that belong to the tenant |
| All Transport messages (Device) | Up to 200 per second, not exceeding 6,000 per minute, and capped at 14,000 per hour |
Up to 200 per second, not exceeding 6,000 per minute, and capped at 14,000 per hour |
Up to 200 per second, not exceeding 6,000 per minute, and capped at 14,000 per hour |
Up to 200 per second, not exceeding 6,000 per minute, and capped at 14,000 per hour |
Total number of messages received by any of the transport microservices for each device separately |
| Telemetry Transport messages (Device) | Up to 100 per second, not exceeding 3,000 per minute, and capped at 7,000 per hour |
Up to 100 per second, not exceeding 3,000 per minute, and capped at 7,000 per hour |
Up to 100 per second, not exceeding 3,000 per minute, and capped at 7,000 per hour |
Up to 100 per second, not exceeding 3,000 per minute, and capped at 7,000 per hour |
Total number of telemetry messages received by any of the transport microservices for each device separately |
| Telemetry Transport data points (Device) | Up to 200 per second, not exceeding 6,000 per minute, and capped at 14,000 per hour |
Up to 200 per second, not exceeding 6,000 per minute, and capped at 14,000 per hour |
Up to 200 per second, not exceeding 6,000 per minute, and capped at 14,000 per hour |
Up to 200 per second, not exceeding 6,000 per minute, and capped at 14,000 per hour |
Total number of telemetry data points received by any of the transport microservices for each device separately |
| Integration messages (Tenant) | Up to 100 per second, not exceeding 3,000 per minute, and capped at 70,000 per hour |
Up to 1,000 per second, not exceeding 30,000 per minute, and capped at 700,000 per hour |
Up to 5,000 per second, not exceeding 150,000 per minute, and capped at 3,500,000 per hour |
Up to 10,000 per second, not exceeding 300,000 per minute, and capped at 7,000,000 per hour |
Total number of messages received by any of the transport microservices for all devices that belong to the tenant |
| Integration messages (Device) | Up to 100 per second, not exceeding 3,000 per minute, and capped at 7,000 per hour |
Up to 100 per second, not exceeding 3,000 per minute, and capped at 7,000 per hour |
Up to 100 per second, not exceeding 3,000 per minute, and capped at 7,000 per hour |
Up to 100 per second, not exceeding 3,000 per minute, and capped at 7,000 per hour |
Total number of telemetry messages received by any of the transport microservices for all devices |
| REST requests (Tenant) | Up to 100 per second, not exceeding 2,000 per minute |
Up to 100 per second, not exceeding 2,000 per minute |
Up to 100 per second, not exceeding 2,000 per minute |
Up to 100 per second, not exceeding 2,000 per minute |
Total number of telemetry data points received by any of the transport microservices for all devices that belong to the tenant |
| REST requests (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 |
Up to 50 per second, not exceeding 1,000 per minute |
Total number of messages received by any of the transport microservices for each device separately |
| WS updates per session | Up to 1,000 per second, not exceeding 10,000 per minute |
Up to 1,000 per second, not exceeding 10,000 per minute |
Up to 1,000 per second, not exceeding 10,000 per minute |
Up to 1,000 per second, not exceeding 10,000 per minute |
Total number of telemetry messages received by any of the transport microservices for each device separately |
| WS Sessions (Tenant) | 1K | 1K | 1K | 1K | Maximum number of Web socket sessions for the tenant |
| WS Subscriptions (Tenant) | 20K | 20K | 20K | 20K | Maximum number of Web socket subscription for the tenant |
| WS Sessions (Customer) | 500 | 500 | 500 | 500 | Maximum number of Web socket sessions for the сustomer |
| WS Subscriptions (Customer) | 10K | 10K | 10K | 10K | Maximum number of Web socket subscription for the сustomer |
| WS Sessions (Public user) | 250 | 250 | 250 | 250 | Maximum number of Sessions per public user |
| WS Subscriptions (Public user) | 5K | 5K | 5K | 5K | Maximum number of subscriptions per public user |
| WS Sessions (Regular user) | 100 | 100 | 100 | 100 | Maximum number of Sessions per regular user |
| WS Subscriptions (Regular user) | 2K | 2K | 2K | 2K | Maximum number of subscriptions per regular user |
| WS queue message (Session) | 500 | 500 | 500 | 500 | Maximum size of queue message per session |
where “K” means 1 thousand, “M” means 1 million, “B” means 1 billion.
White-labeling
ThingsBoard web interface allows you to configure your company or product logo and color scheme in 2 minutes with zero coding efforts and no service restart required. See feature documentation for more details. ThingsBoard Cloud extends white-labeling feature with ability to configure own domain name easily. See managing domain for more details.
The white-labeling feature is available for Prototype and Startup subscription plans.