TBMQ Pricing

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 GitHub Issues, 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 the 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.

Security depends on your infrastructure setup, but TBMQ 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.

No, we do not do it for many reasons. Firstly, as a broker 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.

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, TBMQ offers a 30-day free trial for the self-managed Professional Edition license, which is available exclusively for the minimum capacity configuration: 100 Sessions, 100 messages per second (msg/sec), and 1 Production Instance. This trial allows you to fully test the broker's performance and core features within your own infrastructure without any financial commitment. At the end of the 30 days, you can choose to transition to a paid subscription, either maintaining that minimum configuration or scaling up your capacity as required.

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

No, all sales are final.

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

The included Support tier for the TBMQ Self-managed Subscription is tied to the total monthly cost of the license. The foundational Community support tier (which provides access to our public knowledge base and forums) is included when the total subscription cost is less than $300. Once the total subscription cost reaches or exceeds $300, the Direct Help Desk tier is automatically unlocked, providing ticketed access to our expert team. Alternatively, the Direct Help Desk tier can be accessed immediately by purchasing the Priority Help Desk add-on, regardless of the subscription's total monthly cost.

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 includes response time support and you have access to the Support Portal, the TBMQ 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.

The method for contacting support depends on your current license tier. If you are using the Community support tier, support is provided via self-service resources, including our comprehensive public documentation, knowledge base, and peer-to-peer forums. If you have the Direct Help Desk or Priority Help Desk tier (which is included when your subscription cost is over $300 or purchased as an add-on), you will access support through our dedicated ticketed system via the Support portal, where requests are managed directly by our TBMQ expert team.

Access to our dedicated Support Portal is included with the Direct Help Desk and Priority Help Desk support tiers, as well as for Perpetual license holders. The support service includes expert assistance with platform installation and migration for default deployments, along with resolving any questions related to the platform's out-of-the-box functionalities, as detailed in our documentation. All support inquiries are managed through a single queue, and our commitment is to provide an initial response within 24 hours to address your needs promptly. For specialized services such as custom consulting, code reviews, health assessments, or bespoke development projects, tailored solutions are available; our support engineers will efficiently guide you to the best resources if a request falls outside the standard platform scope.

The Perpetual License for TBMQ is offered as a one-time payment that grants lifetime access to the software. It includes a predefined capacity for sessions, message throughput, and production instances, along with one year of software updates and support. You can expand your deployment at any time by purchasing additional capacity. After the first year, updates and support can be renewed annually, while your license remains permanently active even without renewal.

The so-called license ‘renewal’ does not refer to the license itself but rather corresponds to Support service and access to the Latest releases. Perpetual license unlocks support service and access to newer versions for 1 year. After the initial year, one can prolong this option.

The annual renewal fee for the Perpetual License depends on the total value of your license. Contact us for more details.

Your current license will remain active, allowing you to continue using the platform seamlessly. By renewing your license, you'll gain access to the latest version releases and ongoing support to enhance your experience.

Here’s how the renewal logic works: If you purchased your license on January 1, 2024, your support period and access to new version releases will expire on January 1, 2025. You can continue using the version of the platform you have without any interruptions. However, after January 1, 2025, you will no longer have access to new versions that are released after that date. You can still use the version you have, and you are free to migrate your hardware or upgrade to any version that was available before January 2, 2025.

If you miss the renewal for one year and then decide to renew, you will need to pay the yearly renewal fee for the missed period, in addition to the fee for the new period. If you miss 6 months after the initial expiration date, you can still renew by paying the annual fee, and the renewal will be calculated based on the original expiration date of your license, not from the moment you choose to renew. If you require further clarifications on this, please contact us, and we will be happy to explain.

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.

The total number of instances you can deploy is determined by the specific license purchase you make. Your Perpetual License grants you a fixed count of licensed instances, beginning with one Production Instance included in the Base Price. You can increase this total count permanently at any time by purchasing additional Production or Development Instances with a one-time fee. The license covers the total number of instances you have purchased, and you cannot run more nodes concurrently than your total licensed instance count.

Yes, self-managed TBMQ is cloud-agnostic and can be migrated as needed.

Security depends on your infrastructure setup, but TBMQ 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.

No, we do not do it for many reasons. Firstly, as a broker 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.

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.

During the first launch of TBMQ PE, built-in License Server Client generates an “Activate Instance Request” to the License Server. This request contains the license key and version info about the current platform installation. License Server looks up the subscription info based on the license key and replies with the instance id, subscription plan data, and some magic bytes. License Client stores this information locally and uses instance id and some magic bytes for the next license check requests. More details in the License Server documentation.

No, there is no trial option for perpetual licenses. To trial a self-managed system, you can use self-managed subscriptions.

Cancellation of the perpetual license means the license key will be removed from the License Server. Once the license key is removed, the TBMQ environment using this key will be stopped immediately.

Yes, you can convert your self-managed subscription to a perpetual license by purchasing the perpetual license and replacing the license key in the configuration files. For more details, please contact us.

No, refunds are not offered for perpetual license purchases.

The perpetual license includes dedicated support, providing access to the support portal with an initial response time of 24 hours.

Access to our dedicated Support Portal is included with the Direct Help Desk and Priority Help Desk support tiers, as well as for Perpetual license holders. The support service includes expert assistance with platform installation and migration for default deployments, along with resolving any questions related to the platform's out-of-the-box functionalities, as detailed in our documentation. All support inquiries are managed through a single queue, and our commitment is to provide an initial response within 24 hours to address your needs promptly. For specialized services such as custom consulting, code reviews, health assessments, or bespoke development projects, tailored solutions are available; our support engineers will efficiently guide you to the best resources if a request falls outside the standard platform scope.

Yes, you can purchase additional services such as managed services, advanced SLAs, consultancy, development, and training. For more details, please contact our sales team.

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

Yes, we offer full maintenance services for instances deployed on your infrastructure. These services can be customized based on your needs and are provided under an additional SLA, ensuring regular monitoring, updates, and issue resolution. For more details please contact us.

If your license is a Perpetual License or if you have the Direct Help Desk or Priority Help Desk tier on your subscription, you will access support through our dedicated ticketed system managed directly by our TBMQ expert team. You can log in and submit requests via the Support portal.

The pricing for TBMQ Private Cloud is structured around a single, transparent model based on the capacity and features you require. Every deployment includes a base capacity of 5,000 Sessions and 1,000 messages per second (msg/sec) of Throughput, backed by a 99.9% Uptime SLA. Your total monthly cost is determined by the purchased capacity beyond these base limits and any selected add-ons, such as Multi-AZ Deployment or scaling of Network Traffic capacity. If you exceed your licensed Session or Throughput capacity, this is considered an overage and requires an immediate license capacity adjustment to maintain continuous service.

Yes, we offer a 10% discount on the TBMQ Private Cloud service if you choose to pay annually upfront. The annual subscription provides cost savings and simplifies billing by consolidating all monthly capacity, instance, and add-on 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 complete provisioning and maintenance of your dedicated environment. This includes platform licensing, system monitoring, infrastructure management, software updates, security patching, 24/7 availability monitoring, and SLA-backed support. The fee also includes a default allocation of sessions limit, storage, and message rate capacity depending on your needs.

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, you may incur additional monthly charges for Network Traffic usage that exceeds the included monthly limit. This usage is billed at the rate of $0.10 per GB.

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.

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 will 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.

Yes, you can enhance your Private Cloud subscription with several optional add-ons to customize your deployment. The available add-ons are Multi-AZ Deployment, which ensures greater fault tolerance by spreading your service across multiple availability zones; Dev and QA Instances, which provide dedicated, isolated environments for testing and staging; and Network Traffic, which allows you to purchase data transfer capacity beyond the included monthly limit.

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

Yes. Short-term bursts up to 10% above the stated msgs-per-second ceiling for 5 minutes or less are absorbed automatically and carry no penalty.

The Home dashboard contains information about the number of active and persisted sessions. The monitoring dashboard shows per-minute message rates for both incoming and outgoing MQTT traffic. Storage usage is calculated from multiple internal sources and is available upon request. We are working on making storage metrics visible directly within the platform dashboards.

Trial access is available by deploying TBMQ Community Edition, which lets you explore the core MQTT features in your own environment.

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

Yes, you can reduce your licensed capacity in the TBMQ Private Cloud service if your message rate and resource usage decrease. Since we operate on a single flexible model, reducing capacity means coordinating with the TBMQ team to adjust your licensed Sessions, Throughput, and Instance count to a level that matches your current operational needs. These adjustments are coordinated to ensure service continuity and SLA compliance.

Upgrades are possible at any time, but they are not initiated automatically. The ThingsBoard team continuously monitors your resource usage and message throughput. If your consumption exceeds your current licensed capacity, our team will notify you and guide the process of adding capacity. This ensures uninterrupted service and compliance with SLA guarantees. You can also request an upgrade proactively if you anticipate growth or require additional capabilities.

There is 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/Redis/Kafka dump of all your admin data—including clients, subscriptions, telemetry—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, high-availability services are available as an optional add-on for the TBMQ Private Cloud service. This feature, known as Multi-AZ Deployment, ensures greater fault tolerance and reliability by deploying your dedicated environment across multiple availability zones and is backed by an enhanced Uptime SLA.

The Dev and QA Instances add-on provides dedicated, isolated broker environments specifically for development, staging, testing, and CI/CD workflows. The primary purpose is to ensure that all testing, integration, and code changes are executed without impacting the stability, performance, or data integrity of your live Production environment.

Network Traffic refers to the total volume of data transfer, including both incoming data to the broker and outgoing data to your applications. The base Private Cloud service includes a specific allocation of network traffic (200 GB). The Network Traffic add-on allows you to extend the usage that exceeds the included allocation. Any usage beyond the included monthly limit is billed monthly at the rate of $0.10 per GB.