ThingsBoard Products Pricing

Installation guides are available in the documentation. The Community Edition can be installed in monolith or microservice cluster mode, and supports deployment on Docker, Kubernetes, or directly on Linux/Windows OS.

You can install the Community Edition on your virtual machine, local servers, or any cloud provider infrastructure of your choice.

The Community Edition supports pure SQL or a hybrid SQL + NoSQL (for telemetry storage) . For more details on database options, you can check the database approach reference.

Yes, official Docker images are available on Docker Hub.

Yes, but performance may be limited due to hardware constraints. You can check details in the installation options guide.

Yes, the ThingsBoard Community Edition supports multi-tenancy out of the box.

The Community Edition includes device and asset management, data visualization, rule engine automation, and API integrations. You can find all features and descriptions in the documentation.

The Professional Edition offers advanced features such as white-labeling, RBAC, advanced rule engine capabilities, platform integrations, etc. You can find a more detailed comparison on the ThingsBoard PE page.

No, white-labeling is available only in the Professional Edition.

Yes, the Community Edition supports secure device connectivity options, OAuth configuration, and domain management.

Yes, you can integrate the ThingsBoard Community Edition with third-party systems through REST APIs or Rule Engine. Please note that the Professional Edition of the platform provides more integration option via platform integrations.

Yes, using the rule engine, which allows event-based processing and alerts.

The ThingsBoard team does not provide dedicated support for Community Edition users. However, users can access community-driven resources such as forums, documentation, and GitHub for assistance.

Depending on the type of support you are looking for, the ThingsBoard team may be able to offer certain types of additional support packages. To discuss your unique case and requirements, please contact us.

GitHub (report issues, contribute)

Stack Overflow (for developer-related questions)

Documentation & Tutorials

Yes, you are welcome to submit feature requests on GitHub. After the product team reviews them, they may be added to the backlog.

The ThingsBoard team can propose application configuration services. To discuss your unique case and requirements, please contact us.

Yes, updates for all versions are available.

Yes, you can migrate your data and configuration to an Professional Edition at any time.

• White labeling for branding
• RBAC for application business security strategy
• Advanced integrations capabilities
• Grouping functionality
• Reporting, etc.

ThingsBoard Professional Edition is designed for production and enterprise IoT solutions, offering comprehensive features to meet all your potential needs with the flexibility to deliver tailored solutions without any blockers.

Migration depends on factors such as whether you are migrating to a self-managed system or ThingsBoard Cloud, the version, source code changes, and more. Please contact us for personalized suggestions and a clear strategy on how to perform the migration.

Yes, we offer a one-month trial on ThingsBoard Cloud for users considering an upgrade. If you would like to try the system in self-managed mode, please contact us.

Yes, but security depends on your deployment setup and infrastructure.

Yes, the Community Edition includes transport encryption, as well as SSO (Single Sign-On) and OAuth functionality.

Yes, you have full control over where your data is stored.

Compliance depends on your hosting environment and data security practices.

The Community Edition of ThingsBoard Edge is a free, open-source platform. It offers essential features for managing and analyzing IoT data at the edge.

It is ideal for individuals, startups, educational purposes, and organizations conducting small to medium-sized IoT projects without the need for advanced enterprise features.

Yes, ThingsBoard Edge Community Edition can be used for commercial purposes. You can develop and deploy IoT solutions based on the Community Edition as part of your business operations. It is distributed under the Apache 2.0 license, which allows commercial use without the license or royalty fees.

ThingsBoard Edge Community Edition is able to connect only to ThingsBoard Community Edition server.
ThingsBoard Edge Professional Edition is able to connect only to ThingsBoard Professional Edition server (it can be ThingsBoard Cloud or on-premise instances).
ThingsBoard Edge Community Edition cannot be connected to ThingsBoard Professional Edition and vice versa.

You can install the Community Edition following the installation guides available in the official documentation.

The Community Edition is compatible with various operating systems, including Linux, Windows, and macOS. Specific requirements depend on the deployment method and can be found in the installation guide.

Billing is handled via Stripe and is charged monthly based on your selected plan. You can also pay annually with card or wire transfer. Please contact us to receive a custom invoice.

We accept credit and debit cards through Stripe. You can also pay annually with card or wire transfer. Please contact us to receive a custom invoice.

Sure. In this case, you must reach out to our sales team via contact us. If you have ongoing communication with the account manager or success manager on our end, please refer your request to that person.

We currently offer only a monthly subscription with automatic payments via Stripe. For annual payments, please contact our team to arrange a wire transfer invoice.

We offer Private Cloud plans for large-scale deployments with 10% discounts for annual payments; contact us for details.

You can access invoices and payment history via your ThingsBoard Cloud account dashboard.

Limits vary by plan; details can be found on our plans definition page.

Device usage is determined by the number of device entities created within your account.

Yes, ThingsBoard Cloud charges for all created device entities, whether active or inactive, since telemetry and attribute data for inactive devices are also stored.

If you exceed your limits, you may need to upgrade to a higher plan or purchase additional entity and API call packs.

Yes, you can upgrade your plan at any time to increase your limits, or you can purchase additional entity and API call packs as needed.

Brand the platform as your own. Fully customize it with your own logo, domain, color scheme, and menu items.

We use encryption, access controls, and best security practices to protect your data.

The ThingsBoard Cloud is hosted in an IaaS asset compliant with multiple standards, including SOC II, and ISO 27001.

Your data is stored in either North America or the EU, depending on the cloud region (US or European) you choose. With the Enterprise subscription, you can choose any region or specific country for data storage.

No, security and compliance features are included in all plans.

Yes, ThingsBoard Cloud supports multi-tenancy, with each tenant requiring its own subscription. Within a tenant, a customer hierarchy can be established, allowing tenant administrators to manage multiple customers under a single subscription. This structure provides sufficient flexibility and access control for most use cases, ensuring a well-organized and efficient management model. ThingsBoard Enterprise subscription offers multi-tenancy within a single plan.

Yes, you can export data via APIs or the ThingsBoard dashboard.

Simply sign up on our website—no credit card required (North America or EU).

Once your free trial ends, you will need to add billing details so the system can automatically charge you for the new monthly renewal period after the initial free month expires.

Yes, all your data and configurations remain intact when upgrading.

Kindly refer to the subscription cancellation guide.

Canceling your subscription before the end of the billing cycle will result in the loss of funds allocated for the unused period.

No, refunds are not provided for mid-cycle cancellations.

All paid subscriptions provide access to the ThingsBoard Support Portal, allowing customers to submit support tickets and communicate directly with the support team. Startup and Business plans also include priority support.

Yes, we do provide 24/7 support. If this is what you're looking for, please contact us for a more detailed discussion about your specific needs.

You can use the contact us form and select the "Other" topic. Our account managers will assist you with any billing-related issues.

All of our documentation is available on our website, with no hidden information. Additionally, you can use our Github issues for community support.

Priority support is included with the Startup and Business plans.

Response times vary by plan; Private Cloud customers receive better SLAs.

Trendz is an add-on for advanced IoT Data Analytics. It allows you to analyze, detect anomalies, and predict outcomes — all in one unified analytics workspace that works seamlessly with ThingsBoard. You can check pricing in the Plan calculator.

Trendz pricing depends on your ThingsBoard model. You can check the relevant pricing in the Plan Calculator on this page.

No, all standard features are included in the subscription. However, additional services like professional support may incur extra costs.

No, ThingsBoard and Trendz Analytics must have the same license type to function correctly. Trendz Analytics automatically detects all devices and assets from your ThingsBoard instance, along with their relationships.

It analyzes all entities without the option to select specific ones; all entities will be analyzed and added to the 'business entity' column.

No, you cannot use Trendz without ThingsBoard. Trendz automatically detects and analyzes all entities from your ThingsBoard instance. Without ThingsBoard, Trendz has no data source to work with, making it incompatible for use on its own.

To activate your Trendz license, follow this path:

Billing page → ThingsBoard license details → Manage Add-ons → Enable the checkbox for Trendz → Save the changes.

If you cancel your subscription before the billing period ends, the funds for the remaining period will stay on your balance but will not be refundable.

The Edge Computing add-on enables local data processing at remote sites through ThingsBoard Edge PE instances. Edge runs independently with offline capability and automatically syncs with your central ThingsBoard PE Server when connectivity returns.

It is available for all ThingsBoard PE deployments: Cloud, Private Cloud, and self-managed.

Edge Computing add-on pricing depends on your ThingsBoard model. Check the relevant pricing in the Plan Calculator.

Edge edition must match your ThingsBoard Server edition:

• Edge PE connects to ThingsBoard PE Server.
• Edge CE connects to ThingsBoard CE Server.

Note: Community Editions are free and open-source.

No, Edge PE requires a ThingsBoard PE Server (Cloud, Private Cloud, or self-managed) to provision devices, sync configurations, and exchange data. However, it processes data locally and can operate offline when the connection drops.

You can start with the Free plan (limited to 5 devices) with the Edge Computing add-on permanently enabled. This lets you explore Edge PE features at no cost.

For larger deployments, you can upgrade to paid plans with higher device limits and additional features.

We recommend up to 1,000 devices per Edge instance based on typical edge hardware and connectivity constraints. You can exceed this number depending on your hardware capabilities. For more capacity, deploy multiple Edge instances or, starting with version 4.0, cluster Edge nodes for high availability.

The pricing for Private Cloud is based on the selected service tier. Each plan includes a specific device and data point rate limit to ensure proper resource allocation and SLA compliance. The available plans are:

• Launch: $1,499/month — includes up to 5,000 devices and up to 50,000 data points per minute; additional devices are billed at $0.1/device/month.
• Growth: $2,199/month — includes up to 25,000 devices and up to 100,000 data points per minute; additional devices are billed at $0.09/device/month.
• Scale: $3,999/month — includes up to 50,000 devices and up to 500,000 data points per minute; additional devices are billed at $0.08/device/month.
• Enterprise: Custom pricing — includes 100,000 devices by default and no data point rate limits. Extendable as needed based on specific deployment requirements.
• Short-term bursts up to 20% over the dp/minute ceiling for ≤ 15 min are tolerated. Sustained overages require a plan upgrade.

Yes, we offer a 10% discount on all Private Cloud plans—including Launch, Growth, Scale, and Enterprise—if you choose to pay annually upfront. The annual subscription provides cost savings and simplifies billing by consolidating charges into a single yearly invoice.

We accept bank wire/ACH and credit- or debit-card payments. Card payments are processed securely via Stripe. All billing and invoicing is handled directly by the ThingsBoard Team.

The monthly subscription fee for Private Cloud covers the full provisioning and maintenance of your dedicated environment. This includes platform licensing, infrastructure and system monitoring, software updates, security patching, 24/7 availability monitoring, and SLA-backed support. Each plan tier comes with a predefined allocation of devices, storage, and data point rate capacity. Any usage beyond those included limits (e.g., additional devices, storage, or add-ons) is calculated on top of your regular subscription fee according to your selected plan.

No. Start or stop whenever you like. We do ask for 30 days’ notice before cancellation so we can export your data and decommission the cluster cleanly.

In addition to the base monthly fee for each plan, you may incur additional monthly charges for the following:

• devices beyond the included limit for your selected plan (see pricing table)
• Additional storage usage beyond the included capacity - $0.50 per GB
• Optional add-ons:
  • Dev/Test environment - $299/month
  • White-labeled Mobile App - $99/month + one-time $1 000 build fee

There are no data point rate overage fees—sustained traffic above plan limits requires an upgrade. Short-term bursts up to 20 % over the dp/minute ceiling for ≤ 15 min are tolerated. Sustained overages require a plan upgrade.

A device is any distinct IoT endpoint that the platform tracks as its own entity—i.e. a row in the Device table. A record can be created in three ways:

• Direct connection – the physical unit authenticates itself (token, X-509, access key). One unit → one record.
• Gateway proxy – a gateway authenticates once, then forwards data for subordinate nodes. The gateway is one device, and each proxied node is an additional device (e.g., 1 gateway + 10 meters = 11 devices).
• Server-side integration – data arrives through an integration connector (REST, Kafka, Pub/Sub, OPC-UA, etc.). If the payload identifies a new deviceName/deviceType, ThingsBoard auto-creates the record. Every such auto-created entry counts as a separate device.
• Deleting or disabling a Device entry immediately frees that slot for a replacement, so you only pay for the active records shown in your Device list.

What is a “message”?

A message is any application-layer packet that enters or leaves the platform—whether it’s uplink telemetry, an RPC call, an attribute update, or a downlink—regardless of transport protocol (MQTT, HTTP, CoAP, LwM2M) or integration. We measure sustained messages per minute, aggregated across all protocols.

What is a “data point”?

A data point is a single key/value pair (e.g., "temperature": 23.5) within a message payload. Because some messages bundle multiple measurements, the total number of data points often exceeds the raw message count.

How we count the msg/minute limit?

Telemetry messages carry one or more data points (sensor readings, attribute updates, etc.). Each data point in a telemetry message counts as 1 toward your per-minute limit.

Non-telemetry messages (RPC calls or downlinks with no measurements) carry zero data points—but we still count each such message as 1 toward your per-minute limit.

Total data points per minute = telemetry data points + count of messages with zero data points.

Examples:

Telemetry Payload { "temperature": 23.5, "humidity": 62 } counts as 2 data points

Telemetry Payload { "latitude": 42.222222, "longitude": 73.333333, "speed": 55.5, "fuel": 92, "batteryLevel": 81 } counts as 5 data points.

RPC call payload { "method": "setGPIO", "params": {"pin": 4, "value": 1} } counts as 1 message/data point.

By treating messages without payload as one data point and counting every actual measurement as one data point, we ensure your plan’s per-minute limit reflects your true platform usage.

The cluster tolerates brief spikes (see next answer). If sustained traffic stays above your tier’s ceiling, our monitoring flags it and we’ll ask you to upgrade. Plan upgrades are provisioned within three business days; remaining over-quota traffic may be throttled to protect platform stability.

Yes. Short-term bursts up to 20% above the stated dp-per-minute ceiling for 15 minutes or less are absorbed automatically and carry no penalty.

The Home dashboard contains information about number of devices and The API Usage dashboard contains information about hourly data point rates. The storage usage information is calculated from multiple data sources and available upon request. We are working on a way to embed it into the platform dashboards.

Each plan bundles a block-storage pool (Launch 500 GB, Growth 1 TB, Scale 2 TB; Enterprise custom). Telemetry, attributes, events, and file assets all consume this pool. When usage approaches the quota you can: (a) request to prune old data, (b) expand storage at $0.50 / GB / month, or (c) upgrade the plan.

Replication overhead

The figures above represent raw logical data. For durability the underlying databases keep multiple physical copies:

• PostgreSQL (metadata, latest-timeseries) is synchronously replicated 2×.
• Cassandra (long-term telemetry) keeps 3× replicas by default.

Therefore, 100 GB of logical telemetry stored in Cassandra will be accounted as 300 GB of physical disk space inside your pool, and 100 GB of metadata in PostgreSQL will consume roughly 200 GB.

Note for Cassandra-backed deployments:

Telemetry rows receive a TTL (time-to-live) at the moment they are written. If the TTL is missing or longer than intended, those rows cannot be purged retrospectively; they will live until the TTL expires or the table is truncated. Be sure to set an appropriate TTL in your Rule Engine or integration pipeline when inserting data to keep storage growth predictable.

The Enterprise plan is tailored for customers with complex operational and business needs. While it builds on the same platform features, it introduces a separate, flexible billing model and the option for advanced engineering support at the application level. This combination enables organizations to manage Private Cloud at scale with greater control, specialized assistance, and the ability to align infrastructure with their unique workflows and compliance requirements.

The Enterprise plan includes a default SLA with a guaranteed uptime of 99.95%, which already meets the needs of most mission-critical applications. While fully custom SLAs are typically not required, we are open to discussing specific availability or support requirements on a case-by-case basis to ensure alignment with your business expectations.

Enterprise pricing is calculated based on multiple components to reflect the scale, flexibility, and support level required. The total cost typically consists of:

• Base fee – foundational cost for core platform access and services
• Infrastructure processing costs – reflects actual compute and networking usage
• Management fee – covers monitoring, updates, and support
• Storage costs – based on allocated capacity and retention policy
• Per-device fee – applies after the included 100,000 device threshold is exceeded

Trial access is available on ThingsBoard Cloud, which allows you to explore the core features and capabilities of ThingsBoard without setup overhead.

For ThingsBoard Private Cloud, trials are not applicable due to the use of dedicated infrastructure and custom deployment.

Yes, you can downgrade your Private Cloud plan if your data point rate and resource usage fall within the thresholds of a lower-tier Private Cloud plan. Downgrades are coordinated with the ThingsBoard team to ensure service continuity and SLA compliance. If a downgrade results in a remaining balance, the unused portion of your subscription can either be refunded or applied as store credits for future use. However, it is not possible to downgrade from Private Cloud to ThingsBoard Cloud, as the architectures, infrastructure models, and operational processes differ entirely.

There are no cancellation fee for Private Cloud. However, since your Private Cloud instance runs on dedicated infrastructure, we kindly ask for at least 30 days' advance notice prior to cancellation to ensure smooth resource decommissioning and service wrap-up.

Yes. Once we receive your cancellation notice, we prepare a full encrypted PostgreSQL/Cassandra dump of all your tenant data—including entities, telemetry, files, and audit logs—and deliver it to you over a secure channel (SFTP link or your own cloud bucket). You have up to 60 days after the cancellation date to download and verify the dump. After that 60-day grace period, all remaining backups and cluster data are permanently and securely deleted from our systems.

Yes, additional storage is available and automatically calculated based on your actual usage and retention policy. There's no need to make a separate manual request. At the end of each month, we assess your storage consumption, and any overage beyond your plan’s default quota is billed at $0.50 per GB. This ensures accurate, usage-based billing without administrative overhead on your side.

The Dev/Test Environment is a standalone deployment. It is designed to help you safely test configurations, validate integrations, and simulate real workflows before applying them in production—ensuring accuracy, minimizing risks, and supporting continuous development processes.

High-availability (HA) services are built into the structure of Private Cloud starting Scale plan and are not offered separately as an add-on.

If your usage or operational requirements indicate the need for HA, the ThingsBoard team will proactively recommend an upgrade to the appropriate tier.

This approach ensures consistent architecture, SLA alignment, and reliability without complicating plan configurations.

The Edge Computing add-on enables local data processing at remote sites through ThingsBoard Edge PE instances. Edge runs independently with offline capability and automatically syncs with your central ThingsBoard PE Server when connectivity returns.

It is available for all ThingsBoard PE deployments: Cloud, Private Cloud, and self-managed.

Edge Computing add-on pricing depends on your ThingsBoard model. Check the relevant pricing in the Plan Calculator.

Trendz is an add-on for advanced IoT Data Analytics. It allows you to analyze, detect anomalies, and predict outcomes — all in one unified analytics workspace that works seamlessly with ThingsBoard. You can check pricing in the Plan calculator.

Billing is handled via Stripe and is charged monthly based on your selected plan. You can also pay annually with card or wire transfer. Please contact us to receive a custom invoice.

We accept credit and debit cards through Stripe. You can also pay annually with card or wire transfer. Please contact us to receive a custom invoice.

Sure. In this case, you must reach out to our sales team via contact us. If you have ongoing communication with the account manager or success manager on our end, please refer your request to that person.

We currently offer only a monthly subscription with automatic payments via Stripe. For annual payments, please contact our team to arrange a wire transfer invoice.

If a payment fails, Stripe will retry the charge several times. If unsuccessful, your license will be suspended.

Yes, you can cancel your subscription anytime.

Maker: 10 devices
Prototype: 50 devices
Pilot: 100 devices
Startup: 500 devices
Business: 1000 devices, with the option to purchase additional devices at $0.10 per device per month

A Production Instance refers to a single node of the ThingsBoard platform within your deployment. While one instance is enough to run your solution, multiple instances allow you to operate in Cluster Mode.

By running multiple instances, you achieve:

• High Availability (HA): Your system remains operational even if a node goes down.
• Horizontal Scalability: Distribute the processing load across multiple servers to handle more devices and data.
• Reliability: Built-in redundancy for mission-critical IoT applications.

You will need to upgrade to a higher-tier plan. With the Business plan, you also have the option to purchase additional devices at $0.10 per device per month.

A platform instance can be installed on a single server, which may be a virtual machine, a running Docker container, or a single OS process. If you need to run the platform across multiple locations or as part of a clustered deployment, you can purchase additional instances for any plan as required.

By default, each license includes a predefined number of platform instances. The Maker, Prototype, and Pilot plans include one instance, the Startup plan includes two instances, and the Business plan includes three instances.

No, but you may be charged by your cloud provider for resource usage.

Yes, an internet connection is required for periodic license verification. The system checks the license once per hour, and if the connection is not restored within 24 hours, the platform may shut down. This process ensures proper license management while allowing temporary connectivity issues. For more details, please refer to the license check description. Offline mode is also possible as an add-on to the Perpetual license. Contact our sales team to know more.

Security depends on your infrastructure setup, but ThingsBoard provides built-in authentication, role-based access control, and encryption.

Your data is stored on your own infrastructure, whether on-premise or in the cloud.

Yes, you have full control over data storage location.

Yes, you can export your data using the ThingsBoard dashboard, APIs, or by creating a full database backup.

No, we do not do it for many reasons. Firstly, as a platform vendor, we cannot disclose detected vulnerabilities of certain versions of the platform as the disclosure affects the safety of our existing customers who use that particular version. Secondly, the self-declared pentest is less trustworthy as it is in the vendor's interest to come up with clean results and you never know whether to believe them or not. Lastly, the penetration test makes more sense to be conducted over a ready-to-use end client software/application to define weak spots (if any). It is the Licensee's responsibility to order independent testing. Having said that, the ThingsBoard platform gives one a tool to develop solutions. You may consider the platform a building that a banker rents to establish an office, vault, etc. Now you can see that testing a building itself does not make much sense. But things change when it hosts a bank (or whatever tenant).

Please stay tuned with our Release notes. Critical vulnerabilities or security issues are mentioned in separate line items. Less threatful vulnerabilities appear as a single record ("Vulnerability fixes") stating that, at the release date, the version is free of known HIGH and some MEDIUM CVEs.

Yes, the Maker plan ($10/month) is a low-cost way to explore the platform. It also includes trial license for Edge and Trendz products, so you can fully test the ThingsBoard ecosystem.

Your license will become inactive, and your ThingsBoard instance will be stopped.

Customer may cancel the subscription and purchase a perpetual license. The remain costs from terminated subscription plan (if remain) will be deducted from Total cost for the perpetual license. The perpetual license is non-refundable. Once purchased, it cannot be canceled.

No, all sales are final.

• Maker and Prototype: Community support.
• Startup: Support with 36-hour response time during regular working shifts via Support Portal. Please note: Support for the Startup plan becomes available from the second month of usage.
• Business: Support with 12-hour response time during regular working shifts via Support Portal.

Yes, we can provide 24/7 support as part of our managed services with an additional signed SLA. Please contact us for more details.

If your subscription plan includes response time support and you have access to the Support Portal, the ThingsBoard support team can assist with system deployment as part of the subscription. However, this applies only if you follow recommended installation methods and architecture. Custom installation scripts or non-recommended deployment scenarios are not covered under included support. If your subscription plan does not include support, then we recommend using our documentation, tutorials, and optional professional services. To discuss options, please contact us.

Users of Startup and higher subscriptions, as well as perpetual license holders, are automatically added to the ThingsBoard Support Portal after purchasing a license.

Access to the ThingsBoard Support Portal is available for users with Startup and higher subscriptions, as well as perpetual license holders. Without the need for a separate support agreement, all support inquiries are seamlessly managed through a unified queue, ensuring efficient handling of your requests. Our support team is dedicated to providing an initial response within 24 hours to address your needs promptly.

The support service includes assistance with installation and migration for default deployments, as well as resolving any questions related to the platform's out-of-the-box functionalities, as detailed in our documentation. For specialized services such as consulting, code reviews, health assessments, or development projects, we offer tailored solutions to meet your specific requirements. Should your request involve additional expertise, our support engineers will guide you to the best resources to ensure your success.

Yes, we offer custom IoT development services designed to match your exact requirements. Whether you need a full-featured IoT platform, scalable architecture, or specific integrations, our IoT development team can help you accelerate time-to-market and reduce internal workload while ensuring long-term maintainability.

The Edge Computing add-on enables local data processing at remote sites through ThingsBoard Edge PE instances. Edge runs independently with offline capability and automatically syncs with your central ThingsBoard PE Server when connectivity returns.

It is available for all ThingsBoard PE deployments: Cloud, Private Cloud, and self-managed.

Edge Computing add-on pricing depends on your ThingsBoard model. Check the relevant pricing in the Plan Calculator.

Edge edition must match your ThingsBoard Server edition:

• Edge PE connects to ThingsBoard PE Server.
• Edge CE connects to ThingsBoard CE Server.

Note: Community Editions are free and open-source.

No, Edge PE requires a ThingsBoard PE Server (Cloud, Private Cloud, or self-managed) to provision devices, sync configurations, and exchange data. However, it processes data locally and can operate offline when the connection drops.

You can start with the Free plan (limited to 10 devices) with the Edge Computing add-on permanently enabled. This lets you explore Edge PE features at no cost.

For larger deployments, you can upgrade to paid plans with higher device limits and additional features.

We recommend up to 1,000 devices per Edge instance based on typical edge hardware and connectivity constraints. You can exceed this number depending on your hardware capabilities. For more capacity, deploy multiple Edge instances or, starting with version 4.0, cluster Edge nodes for high availability.

Trendz is an add-on for advanced IoT Data Analytics. It allows you to analyze, detect anomalies, and predict outcomes — all in one unified analytics workspace that works seamlessly with ThingsBoard. You can check pricing in the Plan Calculator.

Trendz pricing depends on your ThingsBoard model. You can check the relevant pricing in the Plan Calculator on this page.

To activate your Trendz license, log in to the License Portal and follow this path:

ThingsBoard license details → Manage Add-ons → Enable the checkbox for Trendz → Save the changes.

If you cancel your license before the billing period ends, the funds for the remaining period will stay on your balance but will not be refundable.

No, we do not charge extra unless you want an additional service that we offer, such as:

• Professional support
• Custom development and consulting
• Training
• Managed services

No, Trendz can be integrated with ThingsBoard Professional Edition (PE), but it is not available in ThingsBoard Community Edition (CE).

No, ThingsBoard and Trendz Analytics must have the same license type to function correctly. Trendz Analytics automatically detects all devices and assets from your ThingsBoard instance, along with their relationships.

It analyzes all entities without the option to select specific ones. You can't select specific devices or assets; all entities will be analyzed and added to the 'business entity' column.

Installation guides are available in the documentation. The Community Edition can be installed in monolith or cluster mode, and supports deployment on Docker and Kubernetes.

You can install the Community Edition on your virtual machine, local servers, or any cloud provider infrastructure of your choice.

The Community Edition supports Kafka, Redis/Valkey, and PostgreSQL. For more details on database options, you can check the TBMQ architecture page.

Yes, official Docker images are available on Docker Hub.

No, the TBMQ Community Edition does not support multi-tenancy.

You can scale the Community Edition vertically by adding more resources for the server, and horizontally by using a cluster deployment.

The Community Edition includes all essential MQTT broker features with full support for MQTT 3.x and MQTT 5.0. You can find all features and descriptions in the TBMQ documentation.

The Professional Edition offers advanced features such as White Labeling, RBAC, Single sign-on, etc. You can find a more detailed comparison on the TBMQ product page.

No, white-labeling is available only in the Professional Edition.

Yes, the Community Edition supports secure MQTT connectivity, authentication, and authorization for MQTT clients.

Yes, you can integrate the TBMQ Community Edition with third-party systems through platform integrations.

The TBMQ team does not provide dedicated support for Community Edition users. However, users can access community-driven resources such as forums, documentation, and GitHub for assistance.

Depending on the type of support you are looking for, the TBMQ team may be able to offer certain types of additional support packages. To discuss your unique case and requirements, please contact us.

GitHub (report issues, contribute)
Stack Overflow (for developer-related questions)
Documentation & Tutorials

Yes, you are welcome to submit feature requests on GitHub. After the product team reviews them, they may be added to the backlog.

The TBMQ team can propose application configuration services. To discuss your unique case and requirements, please contact us.

Yes, updates for all versions are available.

Yes, you can migrate your data and configuration to an Professional Edition at any time.

* White labeling
* RBAC
* SSO
* Audit logs, etc.
TBMQ Professional Edition is designed for production and enterprise IoT solutions, offering comprehensive features to meet all your potential needs.

Migration depends on factors such as the version, source code changes, and more. Please contact us for personalized suggestions and a clear strategy on how to perform the migration.

Yes, we offer a one-month trial for default subscription plan in self-managed mode.

Yes, but security depends on your deployment setup and infrastructure.

Yes, the Community Edition includes transport encryption, as well as authentication and authorization.

Yes, you have full control over where your data is stored.

Compliance depends on your hosting environment and data security practices.

Billing is handled via Stripe and is charged monthly based on your configured subscription.

We accept credit and debit cards through Stripe.

Sure. In this case, you must reach out to our sales team via contact us. If you have ongoing communication with the account manager or success manager on our end, please refer your request to that person.

We currently offer only a monthly subscription with automatic payments via Stripe. For annual payments, please contact our team to arrange a wire transfer invoice.

If a payment fails, Stripe will retry the charge several times. If unsuccessful, your license will be suspended.

Yes, you can cancel your subscription anytime.

A session is any active connection between an MQTT client and the TBMQ broker. Each session represents a single client, uniquely identified by its client ID, and counts toward your session quota.

If a client connects and maintains an active session, it occupies one slot in the session quota. When session persistence is enabled, a disconnected client still occupies a session slot, since its session data (subscriptions, messages, etc.) is retained by the broker.

A session slot is released only when the session has either expired or been explicitly removed. This means your session quota includes both currently connected clients and any disconnected clients with persisted sessions. Only clients with fully expired or deleted sessions free up capacity for new connections.

Throughput (total messages per second) refers to the combined number of MQTT PUBLISH packets processed by the TBMQ each second. This includes both incoming messages from publishers and outgoing messages delivered to subscribers.

For example, if 100 devices each publish 10 messages per second, that results in 1,000 incoming messages per second. If each message is delivered to 2 subscribers, the outgoing volume is 2,000 messages per second. In this case, the total messages per second would be 3,000.

Only MQTT PUBLISH packets are counted—control packets like CONNECT, SUBSCRIBE, PINGREQ, etc., are excluded. This metric reflects the actual messaging throughput of your deployment and is used to ensure performance and SLA compliance.

A Production Instance is the core unit of deployment for TBMQ Professional Edition, representing a single, dedicated TBMQ broker node. This node is licensed exclusively for processing live client traffic, including all licensed Sessions and Throughput. In a self-managed environment, an instance is typically deployed as a Docker container or a Kubernetes pod. While one instance is usually included in the base license, customers often purchase additional instances to create a fault-tolerant cluster for high availability (HA) and increased reliability.

A Development Instance is a dedicated TBMQ broker node—typically deployed as a Docker container or Kubernetes pod—that is licensed exclusively for non-production activities. This includes staging, testing, QA, and CI/CD workflows. The primary purpose of using a dedicated Development Instance is to ensure isolated environments for testing and integration without risking the integrity or performance of your live Production deployment or contaminating production data.

Yes, the self-managed subscription allows you to enhance your license with two specialized add-ons. The White Labeling add-on enables full customization of the broker interface to seamlessly match your corporate branding. The Priority Help Desk add-on moves your support requests into a high-priority queue managed by the expert TBMQ team, ensuring they are triaged and addressed ahead of standard tickets for faster processing of critical operations.

The White Labeling add-on is an optional feature that allows you to fully customize the TBMQ broker interface and deployment components to match your corporate branding. This removes all TBMQ branding from the control panel and deployment environment, enabling you to deliver a unified and seamless experience to your end-users or internal teams. This is primarily used by organizations integrating TBMQ as a core part of their own product or corporate infrastructure.