- Entity limits
- API limits
- Calculated fields limits
- Rate limits
- Top-ups
- Add-ons
- How to cancel my subscription?
ThingsBoars US Cloud provides subscription plans based on the flexible pay-as-you-go model. Designed for scalability, these plans allow you to top-up entity and API limits on demand and enable ThingsBoard Edge and Trendz Analytics as add-ons—empowering you to manage your entire IoT infrastructure in one place.
Main characteristics of the subscription plan are: entity limits, api limits, calculated fields limits, white labeling and the level of support you get.
Looking for older plan details? This page covers subscription tiers introduced on Jan 20, 2026. For accounts created prior to this date, please review the legacy subscriptions page.
Entity limits
Please see table below to compare the entity limits of the subscription plans.
| Parameter name | Free | Prototype | Pilot | Startup | Business | Description |
| Devices | 5 | 50 | 100 | 500 | 1000 | Maximum number of devices |
| Assets | 5 | 50 | 100 | 500 | 1000 | Maximum number of assets |
| Customers | 2 | 5 | 50 | 100 | 200 | Maximum number of customers |
| Users | 5 | 10 | 50 | 100 | 200 | Maximum number of users |
| Dashboards | 5 | 50 | 100 | 200 | 500 | Maximum number of dashboards |
| Rule chains | 3 | 5 | 20 | 50 | 100 | Maximum number of rule chains |
| Integrations | 1 | 3 | 5 | 10 | 20 | Maximum number of integrations |
| Converters | 3 | 10 | 15 | 25 | 50 | Maximum number of converters |
| Scheduler events | 5 | 10 | 100 | 250 | 500 | 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 | Free | Prototype | Pilot | Startup | Business | Description |
| Transport messages | 0.5M | 5M | 50M | 250M | 500M | Total number of messages received by any of the Transports (MQTT, HTTP, CoAP, etc) or Integrations |
| Transport data points | 1M | 10M | 100M | 500M | 1B | Total number of key-value pairs that your telemetry or attribute transport messages contain |
| Rule Engine executions | 3M | 30M | 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 | 100K | 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 | 30 days | 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 10 years. For example, you may store "raw" data for 3 month and aggregated data for 3 years |
| Data point storage days | 30M | 1B | 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 data point storage days |
| Alarms TTL | 30 days | 60 days | 180 days | 365 days | 365 days | How many days to store alarms in the database |
| RPC TTL | 30 days | 60 days | 180 days | 365 days | 365 days | How many days to store persistent RPC in the database |
| Alarms | 200 | 1K | 4K | 20K | 40K | Total number of alarms created per month |
| Emails | 100 | 1K | 2K | 10K | 40K | Total number of emails sent |
| SMS | 0 | 10 | 100 | 500 | 1000 | Total number of SMS sent |
where “K” means 1 thousand, “M” means 1 million, “B” means 1 billion.
Calculated fields limits
Please see the table below to compare the calculated fields limits across subscription plans.
| Parameter name | Free | Prototype | Pilot | Startup | Business | Description |
| Calculated fields per entity maximum number | 10 | 10 | 10 | 10 | 10 | The maximum number of calculated fields allowed on an entity. |
| Max data points number in rolling arguments | 1000 | 1000 | 1000 | 1000 | 1000 | The maximum number of data points supported in rolling arguments. |
| Arguments per calculated field max number | 10 | 10 | 10 | 10 | 10 | The maximum number of input arguments a single calculated field can use. |
| State maximum size in KB | 32 | 32 | 32 | 32 | 32 | The maximum allowed size of stored state data, measured in kilobytes. |
| Single value argument maximum size in KB | 16 | 16 | 16 | 16 | 16 | The maximum size of a single argument value, in kilobytes. |
Rate limits
The platform’s rate-limiting policy preserves predictable service quality and reinforces operational resilience under peak load. Controls are enforced at both the tenant level (aggregate activity across all devices and users) and the individual device level, using consolidated time windows—per second, per minute, and per hour—to balance burst tolerance with sustained throughput ceilings. Thresholds are plan-dependent (Maker, Prototype, Startup, Business, Business+) and scale in line with expected traffic profiles to ensure fair multitenant consumption and SLA adherence.
If the workload exceeds the allocated limits, the corresponding requests will be rejected by the platform for the time being until the rate limits return to within the policy. Additionally, the platform also notifies tenant administrators when a limit breach occurs.
| Parameter name | Free | Prototype | Pilot | Startup | Business | Description |
| All Transport messages (Tenant) | Up to 100 per second, not exceeding 2,000 per minute, and capped at 75,000 per hour |
Up to 1,000 per second, not exceeding 30,000 per minute, and capped at 750,000 per hour |
Up to 2,000 per second, not exceeding 60,000 per minute, and capped at 1,500,000 per hour |
Up to 10,000 per second, not exceeding 300,000 per minute, and capped at 7,500,000 per hour |
Up to 20,000 per second, not exceeding 600,000 per minute, and capped at 15,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 50 per second, not exceeding 1,000 per minute, and capped at 35,000 per hour |
Up to 500 per second, not exceeding 15,000 per minute, and capped at 350,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 100 per second, not exceeding 2,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 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 50 per second, not exceeding 1,000 per minute, and capped at 15,000 per hour |
Up to 100 per second, not exceeding 1,000 per minute, and capped at 15,000 per hour |
Up to 100 per second, not exceeding 1,000 per minute, and capped at 15,000 per hour |
Up to 100 per second, not exceeding 1,000 per minute, and capped at 15,000 per hour |
Up to 100 per second, not exceeding 1,000 per minute, and capped at 15,000 per hour |
Total number of messages received by any of the transport microservices for each device separately |
| Telemetry Transport messages (Device) | Up to 50 per second, not exceeding 600 per minute, and capped at 7,000 per hour |
Up to 100 per second, not exceeding 600 per minute, and capped at 7,000 per hour |
Up to 100 per second, not exceeding 600 per minute, and capped at 7,000 per hour |
Up to 100 per second, not exceeding 600 per minute, and capped at 7,000 per hour |
Up to 100 per second, not exceeding 600 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 100 per second, not exceeding 2,000 per minute, and capped at 15,000 per hour |
Up to 200 per second, not exceeding 2,000 per minute, and capped at 15,000 per hour |
Up to 200 per second, not exceeding 2,000 per minute, and capped at 15,000 per hour |
Up to 200 per second, not exceeding 2,000 per minute, and capped at 15,000 per hour |
Up to 200 per second, not exceeding 2,000 per minute, and capped at 15,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 50 per second, not exceeding 1,000 per minute, and capped at 30,000 per hour |
Up to 500 per second, not exceeding 15,000 per minute, and capped at 350,000 per hour |
Up to 1,000 per second, not exceeding 30,000 per minute, and capped at 750,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,500,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 50 per second, not exceeding 1,000 per minute, and capped at 15,000 per hour |
Up to 100 per second, not exceeding 1,000 per minute, and capped at 15,000 per hour |
Up to 100 per second, not exceeding 1,000 per minute, and capped at 15,000 per hour |
Up to 100 per second, not exceeding 1,000 per minute, and capped at 15,000 per hour |
Up to 100 per second, not exceeding 1,000 per minute, and capped at 15,000 per hour |
Total number of telemetry messages received by any of the transport microservices for all devices |
| Gateway Transport messages (All connected devices) | Up to 100 per second, not exceeding 2,000 per minute, and capped at 60,000 per hour |
Up to 1,000 per second, not exceeding 30,000 per minute, and capped at 360,000 per hour |
Up to 1,000 per second, not exceeding 30,000 per minute, and capped at 360,000 per hour |
Up to 1,000 per second, not exceeding 30,000 per minute, and capped at 360,000 per hour |
Up to 1,000 per second, not exceeding 30,000 per minute, and capped at 360,000 per hour |
Total number of messages received by the transport microservice for all devices connected via particular gateway |
| Gateway Telemetry Transport messages (All connected devices) | Up to 50 per second, not exceeding 1,000 per minute, and capped at 30,000 per hour |
Up to 500 per second, not exceeding 15,000 per minute, and capped at 180,000 per hour |
Up to 500 per second, not exceeding 15,000 per minute, and capped at 180,000 per hour |
Up to 500 per second, not exceeding 15,000 per minute, and capped at 180,000 per hour |
Up to 500 per second, not exceeding 15,000 per minute, and capped at 180,000 per hour |
Total number of telemetry messages received by the transport microservice for all devices connected via particular gateway |
| Gateway Telemetry Transport data points (All connected devices) | Up to 100 per second, not exceeding 2,000 per minute, and capped at 60,000 per hour |
Up to 1,000 per second, not exceeding 30,000 per minute, and capped at 360,000 per hour |
Up to 1,000 per second, not exceeding 30,000 per minute, and capped at 360,000 per hour |
Up to 1,000 per second, not exceeding 30,000 per minute, and capped at 360,000 per hour |
Up to 1,000 per second, not exceeding 30,000 per minute, and capped at 360,000 per hour |
Total number of telemetry data points received by the transport microservice for all devices connected via particular gateway |
| Gateway Transport messages (Gateway system messages) | Up to 50 per second, not exceeding 1,000 per minute, and capped at 15,000 per hour |
Up to 100 per second, not exceeding 1,000 per minute, and capped at 15,000 per hour |
Up to 100 per second, not exceeding 1,000 per minute, and capped at 15,000 per hour |
Up to 100 per second, not exceeding 1,000 per minute, and capped at 15,000 per hour |
Up to 100 per second, not exceeding 1,000 per minute, and capped at 15,000 per hour |
Total number of messages received by the transport microservice for a particular gateway excluding related devices: statistics, debug logs, configuration updates |
| Gateway Telemetry Transport messages (Gateway system messages) | Up to 50 per second, not exceeding 600 per minute, and capped at 7,000 per hour |
Up to 100 per second, not exceeding 600 per minute, and capped at 7,000 per hour |
Up to 100 per second, not exceeding 600 per minute, and capped at 7,000 per hour |
Up to 100 per second, not exceeding 600 per minute, and capped at 7,000 per hour |
Up to 100 per second, not exceeding 600 per minute, and capped at 7,000 per hour |
Total number of telemetry messages received by the transport microservice for a particular gateway: statistics, debug logs, other telemetry |
| Gateway Telemetry Transport data points (Gateway system messages) | Up to 100 per second, not exceeding 2,000 per minute, and capped at 15,000 per hour |
Up to 200 per second, not exceeding 2,000 per minute, and capped at 15,000 per hour |
Up to 200 per second, not exceeding 2,000 per minute, and capped at 15,000 per hour |
Up to 200 per second, not exceeding 2,000 per minute, and capped at 15,000 per hour |
Up to 200 per second, not exceeding 2,000 per minute, and capped at 15,000 per hour |
Total number of telemetry data points received by the transport microservice for a particular gateway: statistics, debug logs, other telemetry |
| REST requests (Tenant) | Up to 100 per second, not exceeding 1,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 |
Up to 100 per second, not exceeding 2,000 per minute |
Total number of REST API calls received by any of the users belong to the tenant |
| REST requests (Customer) | Up to 50 per second, not exceeding 500 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 |
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 |
| WS updates per session | Up to 1,000 per second, not exceeding 5,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 |
Up to 1,000 per second, not exceeding 10,000 per minute |
Total number of messages received by particular WebSocket session |
| WS Sessions (Tenant) | 50 | 100 | 1K | 2K | 4K | Maximum number of Web socket sessions for the tenant |
| WS Subscriptions (Tenant) | 1K | 2K | 4K | 20K | 40K | Maximum number of Web socket subscriptions for the tenant |
| WS Sessions (Customer) | 25 | 50 | 500 | 1K | 2K | Maximum number of Web socket sessions for the сustomer |
| WS Subscriptions (Customer) | 500 | 1K | 2K | 10K | 20K | Maximum number of Web socket subscription for the сustomer |
| WS Sessions (Public user) | 20 | 100 | 250 | 250 | 250 | Maximum number of Sessions per public user |
| WS Subscriptions (Public user) | 500 | 1K | 5K | 5K | 5K | Maximum number of subscriptions per public user |
| WS Sessions (Regular user) | 10 | 50 | 100 | 100 | 100 | Maximum number of Sessions per regular user |
| WS Subscriptions (Regular user) | 200 | 1K | 2K | 2K | 2K | Maximum number of subscriptions per regular user |
| WS queue message (Session) | 100 | 250 | 500 | 500 | 500 | Maximum size of queue message per session |
where “K” means 1 thousand, “M” means 1 million, “B” means 1 billion.
Top-ups
If you reach a specific limit within your subscription plan, you rarely need to upgrade to a higher tier. Instead, you can purchase specific Top-up packs to increase individual limits instantly.
Note: Top-ups are recurring monthly additions to your base plan.
Entity top-ups
These packs allow you to scale the number of managed entities and integrations within your environment.
| Top-up name | Added capacity | Cost |
| Extra Device Pack | +50 Devices, +50 Assets | $15 |
| Extra Customer Pack | +10 Customers, +10 Users | $10 |
| Extra Integration Pack | +1 Integration, +1 Converter | $10 |
| Extra Calculated Field | +1 to max number of Calculated Fields per entity | $5 |
Availability: Extra Device pack is available starting from the Business plan. Other entity top-ups are available starting from the Pilot plan.
API limits top-ups
These packs allow you to extend the operational capacity of your solution, ensuring smooth data processing and communication.
| Top-up name | Added capacity | Cost |
| Traffic Pack | +2.5M Transport Messages, +5M Transport Data Points | $5 |
| Compute Pack | +5M Rule Engine Executions, +1M JavaScript Executions | $25 |
| Storage Pack | +1B Data Points Storage Days | $10 |
| Alarm Pack | +1K alarms created per month | $1 |
| Email Pack | +1K emails sent per month | $1 |
| SMS Pack | +100 SMS sent per month | $15 |
Availability: All Usage & API top-ups are available starting from the Pilot plan.
Add-ons
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 add-on is automatically enabled starting from the Pilot plan.
Edge Computing
The Edge Computing add-on brings intelligence and data processing capabilities directly to the field. It allows you to run a local instance of the platform on-premises, ensuring that your critical operations continue even during a total loss of internet connectivity to the cloud. See product homepage for more details.
Trendz Analytics
The Trendz Analytics add-on is a powerful business intelligence tool designed to convert your raw IoT data into actionable insights. It goes beyond basic visualization, allowing you to perform complex calculations, identify patterns, and predict future trends using advanced statistical models. See product homepage for more details.
How to cancel my subscription?
To terminate your ThingsBoard Cloud subscription, follow these steps:
- Log in to ThingsBoard Cloud as Tenant Administrator;
- Navigate to the “Plan and billing” page in the main navigation menu;
- Locate the Management section, which contains your subscription details and options to control it;
- Click the “Cancel subscription” button and follow the instructions to cancel your subscription;
- Confirm the action by clicking the “Cancel subscription” button in the confirmation window.
Note:
This action cannot be undone. This will permanently delete your tenant account, all devices, assets, dashboards, rule-chains, users and other entities, all telemetry data and alarms.