Cloud
ThingsBoard Documentation
Cloud Professional Edition Community Edition IoT Gateway License Server Trendz Analytics
Try it now Pricing
Documentation > Subscriptions
Getting Started
Guides API FAQ

ThingsBoard Cloud Subscription plans definition

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 nameMakerPrototypeStartupDescription
Devices 10 100 500 Maximum number of devices
Assets 10 100 500 Maximum number of assets
Customers 2 20 100 Maximum number of customers
Users 5 50 100 Maximum number of users
Dashboards 5 50 100 Maximum number of dashboards
Rule chains 5 20 50 Maximum number of rule chains
Integrations 1 5 10 Maximum number of integrations
Converters 5 25 50 Maximum number of converters
Scheduler events 5 20 50 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 nameMakerPrototypeStartupDescription
Transport messages 5M 50M 250M Total number of messages received by any of the Transports (MQTT, HTTP, CoAP, etc) or Integrations.
Transport data points 10M 100M 500M Total number of key-value pairs that your telemetry or attribute transport messages contain.
Rule Engine executions 25M 250M 1000M 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 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 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 50B 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.
Emails 100 2000 10000 Total number of emails sent
SMS 1 20 100 Total number of SMS sent

where “K” means 1 thousand, “M” means 1 million, “B” means 1 billion.

Rate Limits

Parameter nameMakerPrototypeStartupDescription
All Transport messages (Tenant) 200/sec
but no more then 6K/min
but no more then 140K/hour
2K/sec
but no more then 60K/min
but no more then 1.4M/hour
10K/sec
but no more then 300K/min
but no more then 6M/hour
Total number of messages received by any of the transport microservices for all devices that belong to the tenant
Telemetry Transport messages (Tenant) 100/sec
but no more then 3K/min
but no more then 70K/hour
1K/sec
but no more then 30K/min
but no more then 700K/hour
5K/sec
but no more then 150K/min
but no more then 3.5M/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) 200/sec
but no more then 6K/min
but no more then 140K/hour
2K/sec
but no more then 60K/min
but no more then 1.4M/hour
10K/sec
but no more then 300K/min
but no more then 7M/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) 20/sec
but no more then 600/min
but no more then 14K/hour
20/sec
but no more then 600/min
but no more then 14K/hour
20/sec
but no more then 600/min
but no more then 14K/hour
Total number of messages received by any of the transport microservices for each device separately
Telemetry Transport messages (Device) 10/sec
but no more then 300/min
but no more then 7K/hour
10/sec
but no more then 300/min
but no more then 7K/hour
10/sec
but no more then 300/min
but no more then 7K/hour
Total number of telemetry messages received by any of the transport microservices for each device separately
Telemetry Transport data points (Device) 20/sec
but no more then 600/min
but no more then 14K/hour
20/sec
but no more then 600/min
but no more then 14K/hour
20/sec
but no more then 600/min
but no more then 14K/hour
Total number of telemetry data points received by any of the transport microservices for each device separately
Rule Engine executions per message 20 30 40 Maximum number of rule node executions to process particular message

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.