ThingsBoard CE vs PE 2026: When the Free Edition Is Enough – and Which PE Features You Can Build Yourself

WZ-IT operates thingshost. Current hosting starts from €159.80 net/month; setup and service level follow the proposal. Former package prices, location lists and cost comparisons in this dated article describe the previous offer, not current WZ-IT terms. View current service scope.

ThingsBoard is one of the most mature open-source IoT platforms on the market – and at the same time, every project sooner or later faces the same question: Community Edition or Professional Edition? The obvious assumption – that the free CE is a stripped-down demo version and the "real" platform begins only at PE – is wrong. ThingsBoard itself calls the Community Edition the most feature-rich open-source IoT platform in the world – and that is no marketing exaggeration.

Multi-tenancy, clustering for millions of devices, the rule engine including AI nodes, real-time dashboards, and even the mobile app are fully included in CE. Around 80 percent of all code changes flow into the free edition. The real decision is therefore not "free versus complete," but: do you need the specific enterprise features of the Professional Edition – and if so, which of them can be covered with complementary open source or a bit of your own work to stay on the free CE? This article compares both editions using the official feature matrix, works through the costs of the ThingsBoard Cloud, and gives an honest decision aid – including a clear statement of where CE hits limits that cannot be sensibly worked around.

Also worth reading: ThingsBoard Hosting: Cloud vs. Self-Hosted vs. Managed · ThingsBoard vs. AWS IoT Core

The two editions at a glance

Both editions share the same core. Included in CE and PE alike are device connectivity via the standard protocols MQTT, CoAP, HTTP, SNMP, and LWM2M, the industrial IoT gateway with Modbus, OPC-UA, and BACnet connectors, the modeling of devices and assets as digital twins, the rule engine for data processing and alarming, real-time dashboards, multi-tenancy, and a cluster-capable architecture for millions of devices. Audit logging and user management are also part of the shared foundation.

The Professional Edition builds on top of that. It contains everything from CE and adds the functions that are relevant above all for enterprise scenarios and for marketing your own IoT products. PE is therefore not "CE with the actually important features," but CE plus a clearly delimited enterprise layer.

The complete feature matrix

The surprising finding: the left column is very long. For the majority of classic IoT use cases – connecting devices, processing data, visualizing, alarming – CE delivers everything needed. The PE column is almost entirely an enterprise and go-to-market layer.

What only PE can do – and whether you really need it

Three areas are most often cited as reasons for PE – and they deserve a closer look: one is not PE-exclusive at all, one can be rebuilt with complementary open source, and one is a genuine PE domain.

LoRaWAN/Sigfox – and the ChirpStack alternative

The native LoRaWAN integration with over 400 prebuilt payload decoders is PE-exclusive and very convenient. If you want to stay on CE, you put a dedicated LoRaWAN network server like ChirpStack in front: ChirpStack receives and decodes the sensor data and forwards it via MQTT or HTTP to ThingsBoard CE. This costs a bit more setup effort and maintaining the decoders, but it avoids the PE license. If you don't want to operate ChirpStack yourself, you can also get it as a managed service from our sister brand chirphost.

SSO/OAuth2 is included in CE – advanced RBAC is the PE limit

A common misconception: that SSO is PE-only. In fact, the Community Edition natively supports OAuth 2.0 and OIDC and can be connected directly to external identity providers like Authentik, Keycloak, Okta, Auth0, or Azure – including mapping external accounts to tenants and customers. No upstream reverse proxy is needed. If you also want a managed IdP instance, Authentik is available as a managed service from our sister brand authhost. The real PE limit is advanced RBAC: granular custom roles and fine-grained permissions are PE-exclusive. Anyone who only needs SSO login is fine with CE; anyone who has to model complex role-based access with custom roles needs PE.

White-labeling, reporting, solution templates – a genuine PE domain

This is where the rebuild ends. White-labeling (selling ThingsBoard as your own product), automated reporting to customers, the 400+ codec library as a convenience function, and solution templates are PE domains that cannot be cleanly replaced with open source. If you need these functions commercially, PE is the right – and often more economical – choice.

The cost question

CE itself is free; costs arise only from operation. With PE it depends heavily on the model. The ThingsBoard Cloud bills per device – from about 0.30 US dollars per device, with plan minimums:

On top come data-point limits: every telemetry value counts. A sensor that sends every five minutes generates around 8,640 data points per month – at 500 sensors that is about 4.3 million data points monthly, and overages cost extra.

The most expensive mistake is to go into the per-device-billed cloud out of convenience when a self-hosted or managed CE setup without per-device costs would have been enough. For large sensor fleets the difference quickly reaches five figures per year. The deployment options in detail – cloud, self-hosted, and managed – are compared in our article ThingsBoard Hosting: Cloud vs. Self-Hosted vs. Managed.

Prices in US dollars, as of May 2026, approximate values plus possible data-point overages. Features and prices can change at any time – please check directly with ThingsBoard.

The decision matrix

When CE is enough

• Standard IoT use cases: connecting devices, processing data, dashboards, alarms
• Self-hosting with your own or managed operation
• No need for white-labeling or automated reporting
• LoRaWAN solvable via an upstream ChirpStack
• Authentication via internal user management (or proxy) sufficient

When PE pays off

• White-labeling needed (selling ThingsBoard as your own product)
• LoRaWAN/Sigfox with convenience and 400+ codecs out of the box
• Advanced RBAC with granular custom roles and real role mapping
• Automated reporting to customers
• SLA-bound support required

The most important risk buffer: migration from CE to PE is seamless. You can start on CE, validate the project value, and upgrade only when there is concrete need – without a platform switch and without data loss. So if you start with CE, you don't lock yourself in.

Data sovereignty – where is your data?

A point that often gets lost in pure feature comparisons: ThingsBoard Inc. is based in New York, and the ThingsBoard Cloud runs on AWS infrastructure with EU and US clusters. Even when choosing the EU cluster, a US company remains the operator – the same CLOUD Act and data-sovereignty question applies as with other US cloud services. For personally identifiable or sensitive industrial data, this is a relevant factor. Anyone who needs full data sovereignty runs ThingsBoard CE or PE self-managed or via a German managed provider that keeps the data in EU-sovereign infrastructure, for example as managed ThingsBoard hosting in Germany. How ThingsBoard positions itself against a pure US hyperscaler platform is shown in ThingsBoard vs. AWS IoT Core.

Note: not legal advice. For specific compliance questions, consult data-protection and legal advisers.

Conclusion

The question "CE or PE" is often framed wrongly – as if it were "free but limited" versus "expensive but complete." In reality, the Community Edition is fully sufficient for the vast majority of self-hosting scenarios. PE adds a clearly delimited enterprise layer – LoRaWAN convenience, advanced RBAC with granular role mapping, white-labeling, reporting – that is exactly right for some use cases and simply unnecessary for many others. Some of these features can be partly rebuilt with complementary open source (ChirpStack, Authentik), others deliberately cannot.

Managed ThingsBoard from thingshost does not take the edition decision off your hands, but it does take over operations – for both editions:

• ✓ Community or Professional Edition – we run both
• ✓ Flat rate instead of the cloud's per-device costs
• ✓ Data in German infrastructure instead of US AWS
• ✓ Hosting, updates, backups, monitoring, and support included
• ✓ Try it free for 7 days

What Standard and Premium cost and how the device tiering works is shown in the thingshost pricing for CE and PE.

Agree scope and provisioning with WZ-IT. Provisioning and contract terms are agreed with WZ-IT in the proposal. There is no self-service portal or automatic trial subscription.

Read more: ThingsBoard Hosting: Cloud vs. Self-Hosted vs. Managed and ThingsBoard vs. Grafana.

What the PE licence costs on its own, and what the managed price additionally includes, is worked through on the ThingsBoard Cloud alternative page.

Sources

• ThingsBoard CE vs PE – official comparison
• ThingsBoard Professional Edition – features
• ThingsBoard Pricing
• ThingsBoard Documentation
• ThingsBoard GitHub Repository (Apache 2.0)
• ChirpStack – LoRaWAN Network Server
• Authentik – Open-Source Identity Provider
• thingshost.de – Managed ThingsBoard Hosting