ThingsBoard alternatives in 2026: picking an IoT platform for a small industrial fleet

By Synacl · 7 min read · Published 11 Sep 2026

ThingsBoard is the platform most people find first when they search for an open-source IoT dashboard, and for good reason: it is mature, self-hostable and can do almost anything. It is also a lot of platform for a plant with forty meters and one electrician. This guide compares the realistic alternatives for a small industrial fleet — tens to a few hundred devices, mostly Modbus, RS485 and simple sensors — by the things that actually decide the outcome: who hosts it, how devices get in, what the pricing model does as you grow, and how much engineering you need on staff.

Prices below were checked in September 2026 against each vendor's public pricing page and they change often; treat them as the shape of the offer, not a quote. Synacl is our product, so the last section is ours to argue and the rest is written to be fair.

What ThingsBoard is good at, and where it gets heavy

ThingsBoard comes in three forms. Community Edition is Apache-2.0 licensed and self-hosted: you get device management, a rule engine, a widget library with dozens of widget types and a dashboard builder, and you pay in servers and attention rather than licence fees. Professional Edition adds white-labelling, integrations and multi-tenant features under a paid licence. ThingsBoard Cloud is the hosted version, billed per device and per stored data point: a free tier of 5 devices, paid tiers from about $49 a month, up to a Business tier around $749 a month for 1,000 devices, with extra devices at roughly $0.30 each.

Where it shines: you need a rule engine you can program in depth, you want to own the stack, or you are integrating a dozen protocols through the separate ThingsBoard IoT Gateway (a Python service you run on an edge box). Where it gets heavy: the gateway is a second product to deploy and keep alive, Modbus devices are configured in JSON files or the gateway UI rather than the platform, self-hosting means PostgreSQL or Cassandra plus Kafka at scale, and the data-point billing on Cloud punishes sensors that report often. If your team has a developer who enjoys this, it is a fine choice. If your team is an installer with a laptop, it is a project.

The alternatives, one by one

Blynk

Blynk grew up as the app-builder for makers and has moved towards businesses. Its strength is the phone app: drag a few widgets, connect an ESP32 with the Blynk library, done. The free plan is deliberately small; paid plans start around $29 a month and step up quickly. Modbus and RS485 are not first-class — you write the firmware that reads the bus and publishes values. Best for: a product team building a consumer or light-commercial device that ships with its own firmware and needs a branded mobile app.

Datacake

Datacake is a low-code platform with unusually good LoRaWAN support and a generous free tier of 5 devices. Paid plans are per device bundle (around $25 a month for 25 devices). Device data is decoded with JavaScript payload decoders you maintain per device type. Modbus reaches it through third-party gateways. Best for: LoRaWAN sensor fleets and anyone whose devices already speak MQTT or HTTP with a payload they can decode in a few lines.

Ubidots

Ubidots offers polished dashboards, an events engine and white-label options on higher tiers. The free tier is 3 devices; the Professional plan is around $99 a month, and the Industrial and Enterprise tiers add SCADA-style features on request. Like Blynk and Datacake, the device side is your problem — it ingests MQTT and HTTP. Best for: teams that want a clean, presentable dashboard product on top of devices they already control.

Arduino Cloud

If your hardware is Arduino-branded or ESP32 boards flashed with Arduino sketches, Arduino Cloud is the path of least resistance: the IDE, the device provisioning and the dashboard are one product. The free tier covers a couple of devices; paid plans are a few dollars a month. It is a maker and education platform first; industrial protocols, fleet operations and alerting are thin. Best for: classrooms, prototypes and small projects that will stay small.

Node-RED, InfluxDB and Grafana

The DIY stack: Node-RED for flows and Modbus (its Modbus nodes are excellent), InfluxDB for time series, Grafana for dashboards and alerts, Mosquitto for MQTT. All free, all self-hosted, endlessly flexible. The cost is ownership: backups, upgrades, TLS, user management, and the knowledge living in one person's head. Best for: a single site with a capable engineer who wants total control and has no need for multi-tenant access or a mobile app.

AWS IoT Core, Azure IoT Hub

These are primitives, not platforms. You get a secure MQTT broker at any scale and pay per message and per connection minute, then you assemble storage, dashboards, alerting, device provisioning and OTA yourself from other services. Superb when you have a cloud team and unusual requirements; expensive in engineering time when you do not. Best for: software companies building their own IoT product on top.

Comparison at a glance

How to choose in ten minutes

Answer four questions and most of the table disappears.

1. Do your devices already speak MQTT or HTTP with firmware you control? If yes, every hosted platform works and you are choosing on dashboards and price. If no — they are Modbus meters, RS485 probes, 4–20 mA transmitters on a PLC — you need a gateway, and the question becomes who provides and maintains it.
2. Is self-hosting a requirement or a preference? A requirement (data residency, air gap, policy) points at ThingsBoard CE or the DIY stack. A preference usually evaporates the first time an upgrade breaks at 2 a.m.
3. How often do sensors report? Per-data-point billing (ThingsBoard Cloud) is fine at one reading a minute and painful at one a second. Per-device billing does not care.
4. Who will run it day to day? If the answer is an electrician, an installer or a plant manager, the platform must do provisioning, firmware updates and diagnostics from a browser, or the work lands back on whoever set it up.

Where Synacl fits, and where it doesn't

Synacl was built for the case the table leaves half-served: industrial-ish hardware, a small fleet, and no software team. The gateway is not a separate product — it is an ESP32 you flash from the browser, provision over USB, and update over the air with its settings kept. Modbus RTU and RS485 devices are configured in the platform, register by register, with scaling and units on each tag; GPIO, I²C, 1-Wire, SPI, UART and CAN devices hang off the same gateway, and devices that already speak MQTT or HTTPS connect directly without one. On top sit live dashboards with SCADA-style widgets and P&ID mimics, threshold and event rules with email, webhook and MQTT actions, gateway-local macros that keep running when the internet does not, uptime history, and a white-label portal for installers who run fleets for several customers.

Pricing is per plan by device count with no per-message component; the first five devices are free, and the paid tiers are on the pricing page. It is a hosted service in USD and INR.

Where it is not the right pick: if you must self-host, if you need a general-purpose workflow engine to build custom applications, or if you are past several thousand devices with an enterprise SLA conversation to have, ThingsBoard PE, the DIY stack or the cloud primitives will serve you better. We would rather you pick the right tool than pick ours.

If you want to see the gateway path end to end, the ESP32 Modbus RTU to a cloud dashboard guide walks through a real RS485 sensor from wiring to alert in about fifteen minutes.