The short answer: there is no single ThingsBoard alternative, because the well-known open-source IoT platforms serve different layers. ThingsBoard is the broad application platform (device management, dashboards and a rule engine in one). Node-RED is the flow and integration tool. EdgeX Foundry is the industrial edge framework. Eclipse Ditto is a pure digital-twin layer. OpenRemote is the complete solution for smart buildings and energy. This article compares the five factually along purpose, device management, dashboards, rules, scaling, license and self-hosting, and shows when each one fits.
What "ThingsBoard alternatives" really means
People searching for alternatives often compare tools that do not do the same thing. An IoT solution consists of several architecture layers: devices and radio, connectivity and protocols, application logic, visualization. Some platforms cover only one layer, others several. The honest question is therefore not "which is best?" but "which layers does my project need to fill, and which tool covers them most cleanly?". All five are self-hostable and free of cloud lock-in. Four are open source; ThingsBoard only up to version 4.3, since version 4.4 (29 September 2026) the Business Source License 1.1 applies, with device limits for free use (ThingsBoard, announcement). They differ widely in feature scope and operational effort.
Comparison table: ThingsBoard, Node-RED, EdgeX, Ditto, OpenRemote
| Criterion | ThingsBoard | Node-RED | EdgeX Foundry | Eclipse Ditto | OpenRemote |
|---|---|---|---|---|---|
| Purpose | Broad IoT application platform | Low-code flows, integration | Industrial edge data framework | Digital-twin layer (API-first) | Smart-building / energy suite |
| Device mgmt | Strong (device profiles, provisioning, RBAC) | Weak (no device registry) | Device services (Modbus, OPC UA, BACnet) | Twin state, no protocol stack | Asset mgmt, auto-provisioning |
| Dashboards | Full, freely built | Add-on (Dashboard 2.0) | No native UI | Explorer UI only | Built-in dashboard builder |
| Rules | Rule engine (rule chains) | Visual flows | Rules via eKuiper | Conditions/API, no engine | When-then, flow, Groovy, JS |
| Scaling | Horizontal (cluster, microservices) | Vertical, mostly single instance | Edge nodes, microservices | Horizontal (millions of twins) | Single-realm stack, multi-tenant |
| License | up to 4.3 CE: Apache 2.0; from 4.4: BUSL 1.1 | Apache 2.0 | Apache 2.0 (LF Edge) | EPL-2.0 | AGPLv3 |
| Self-host | Yes (Docker/Kubernetes) | Yes (Node.js/Docker) | Yes (Docker/Snap) | Yes (Docker/K8s/Helm) | Yes (Docker) |
| Current (October 2026) | 4.4 (Sep 2026), LTS 4.3 | 5.0 (Jun 2026) | 4.0 "Odesa" LTS | 3.9 (patch 3.9.8, Oct 2026) | 1.32.0 (Oct 2026) |
The five platforms in profile
ThingsBoard is the most comprehensive of the five and what most people mean by "IoT platform": device management via device profiles, native transports (MQTT, HTTP, CoAP, LwM2M), freely built dashboards, a rule engine (rule chains) and multi-tenancy (thingsboard.io). The current release is ThingsBoard 4.4 (September 2026). With this version ThingsBoard changed its license: the Community Edition up to 4.3 stays under Apache 2.0 and receives security updates until 20 July 2027. From 4.4 there is a single product under the BUSL 1.1 with all former Professional features, free up to 100 devices on one server for commercial use, licensed beyond that. The consequences are covered in the post ThingsBoard 4.4 under BUSL 1.1. More in What is ThingsBoard? and the comparison ThingsBoard vs ChirpStack.
Node-RED is not a platform replacement but a low-code flow tool (nodered.org). You wire nodes visually into data flows: input via MQTT or HTTP, transform, output to a database, API or platform. Since Node-RED 5.0 (June 2026) with a reworked editor and built-in dark theme, licensed under Apache 2.0 (OpenJS Foundation). Node-RED has no real device registry, no multi-tenancy, and dashboards only via the Dashboard 2.0 add-on. It shines as a glue layer and prototyping tool, often right next to ThingsBoard. We use it regularly, see Node-RED expertise.
EdgeX Foundry is an edge-first framework by the Linux Foundation (LF Edge) for industrial brownfield environments. Through device services it connects Modbus, OPC UA and BACnet natively, normalizes data at the edge and passes it upstream. The current release is EdgeX 4.0 "Odesa" as a long-term-support release (patch 4.0.2 "Palau"), under Apache 2.0. EdgeX deliberately ships no application UI of its own; rules run through the embedded engine eKuiper. Typical use: as an edge data layer in front of a platform like ThingsBoard, not as its replacement.
Eclipse Ditto is a digital-twin framework, not a complete product. It models each device as a "Thing" with desired and reported state and offers a clean, API-first abstraction (HTTP, WebSocket, plus AMQP/MQTT/Kafka connectivity). The current release is Ditto 3.9 (patch 3.9.8 of October 2026, GitHub releases) under EPL-2.0, scaling horizontally to millions of twins. What is missing: ready-made dashboards (only an Explorer UI), radio protocols and a visual rule engine. Ditto is the right choice when you build your own application around a stateful device API, not when you need a finished operator front end.
OpenRemote is the complete solution for the built environment: asset management with customizable asset types, map visualization, automation via when-then, flow, Groovy and JavaScript rules, multi-tenancy via realms and a built-in Insights dashboard builder. The current release is OpenRemote 1.32.0 (October 2026) (GitHub releases). The license matters: OpenRemote is AGPLv3. If you offer it as a network service and modify the code, you must disclose those changes. For smart buildings and energy management it is often the fastest complete solution, but stricter than the Apache 2.0 candidates for free reuse inside a product.
There are further open-source building blocks too, such as the backend framework Kuzzle. For most sovereign IoT projects, however, the choice lands on the five above.
When each platform fits
- You need a finished platform with device management, dashboards and rules in one: ThingsBoard. The default for LoRaWAN and sensor projects with custom dashboards.
- You need to connect protocols, transform data or prototype fast: Node-RED, often alongside ThingsBoard.
- You integrate industrial and legacy assets at the edge (Modbus, OPC UA, BACnet): EdgeX Foundry as the edge layer, with a platform above it.
- You build a custom application around a stateful device API: Eclipse Ditto as the digital-twin layer.
- You run smart buildings or energy management and want everything in one package: OpenRemote, mindful of the AGPLv3.
In practice you often combine several building blocks, for example Node-RED or EdgeX at the edge, ThingsBoard as the application platform and Grafana for specialized dashboards.
License and cost, honestly
The core software of Node-RED, EdgeX, Ditto and OpenRemote is license-free, for ThingsBoard the Community Edition up to 4.3. Apache 2.0 (ThingsBoard CE up to 4.3, Node-RED, EdgeX) is permissive and uncritical for commercial products. EPL-2.0 (Ditto) is weak copyleft, also manageable. AGPLv3 (OpenRemote) requires disclosure of changes once you offer the software as a network service; for self-hosted operation this is usually controllable but should be checked deliberately.
The real cost driver is not the license but servers, operation and maintenance. License costs arise mainly with ThingsBoard from 4.4: beyond the free limit of 100 devices on one server, the commercial license costs from 99 USD per month (Business 499 USD for 1,000 devices) or, as a perpetual license, from 4,999 USD one-time; ThingsBoard Cloud charges from 0.30 USD per additional device per month, managed private cloud from 1,499 USD per month (per thingsboard.io/pricing, October 2026). Existing CE installations can move to 4.4 free of charge at their current size through the Community Grant. A full breakdown is in ThingsBoard pricing. This is exactly where open-source, self-hosted platforms win over managed IoT clouds (AWS IoT, Azure IoT, Cumulocity), whose per-device and per-message billing explodes with device count. More in the comparison IoT self-hosted vs. cloud.
Operation and support
We plan, build and operate sovereign, self-hosted IoT platforms on your infrastructure (Proxmox, Hetzner, on-prem), GDPR-compliant from Germany and without cloud lock-in. Which building block fits depends on your use case; we select vendor-neutrally and honestly instead of pushing you into one platform. More on our pages for ThingsBoard and Node-RED, in the IoT hub and on IoT platform development. For a no-obligation initial consultation, book a meeting directly.
