TagoIO vs. ThingsBoard

Compare TagoIO and ThingsBoard on hosting model, dashboards, custom logic, white-labeling, and total cost, including ThingsBoard CE self-hosting trade-offs.

Updated

ThingsBoard and TagoIO are both full-featured IoT platforms with device management, dashboards, and rules. The core difference is the delivery model: ThingsBoard is best known as software you can host yourself, with commercial editions layered on top, while TagoIO is a managed platform with dedicated deployments available when projects need isolation. Which one fits usually comes down to how much infrastructure your team wants to own.

ThingsBoard is an open-source IoT platform developed by ThingsBoard, Inc. The Community Edition (CE) is free under Apache 2.0 and self-hosted. The Professional Edition (PE) adds white-labeling, granular RBAC, customer hierarchies, platform integrations (LoRaWAN network servers, Sigfox, cloud services), and the scheduler, available self-managed or through ThingsBoard Cloud and managed private cloud. The stack is Java and Spring with Kafka, PostgreSQL, and optionally Cassandra or TimescaleDB, with ThingsBoard Edge for local processing. Version 4.x brought SCADA symbols, calculated fields, AI rule nodes, and a reworked pricing structure in early 2026.

TagoIO is a full-stack IoT platform delivered as a managed service: 500+ device connectors, MQTT and HTTPS ingestion, time-series buckets with retention up to 9 years, drag-and-drop and Blueprint dashboards, serverless Analysis scripts in Node.js, Deno, or Python, Actions for rules, and TagoRUN white-label portals. TagoDeploy provides dedicated instances in 12+ AWS regions, and TagoCore is a free, open-source edge engine.

TagoIO vs. ThingsBoard comparison matrix

TagoIO ThingsBoard CE ThingsBoard PE / Cloud
Delivery Managed cloud, dedicated via TagoDeploy Self-hosted, you operate everything Self-managed license or managed SaaS
License / source Proprietary platform; TagoCore edge engine is open source Apache 2.0 Commercial
Protocols MQTT, HTTPS, LoRaWAN / Sigfox / satellite via connector integrations MQTT (incl. Sparkplug B), CoAP, HTTP, LwM2M, SNMP; OPC-UA/Modbus/BACnet via IoT Gateway Same as CE plus platform integrations (LoRaWAN NS, Sigfox, AWS/Azure)
Dashboards Built in, Blueprint dashboards for fleets Built in, large widget library, SCADA symbols Same, plus white-label branding
Custom logic Serverless Analysis in Node.js, Deno, Python Visual Rule Engine; deeper customization in Java/Angular Visual Rule Engine plus PE features
White-label end-user apps TagoRUN portal, custom domain, mobile app option Not included White-labeling in PE/Cloud
Ops burden None (managed) or handled in TagoDeploy Kafka, database tuning, upgrades, HA are yours Reduced on Cloud; self-managed PE still yours
Pricing model Free tier; Starter $49/mo; Scale $199/mo; TagoDeploy from $850/mo; service-based usage Free software plus your infrastructure and ops cost PE from ~$10/mo (10 devices) to $499/mo (1,000); Cloud $49 to $749/mo tiers
Compliance ISO 27001, GDPR Whatever you certify yourself Vendor-operated for Cloud

Self-hosting is the real variable

ThingsBoard CE is one of the most complete free IoT platforms available, and for teams with the skills and mandate to run their own stack, that is a real advantage: full control, data on your servers, no subscription. The cost shows up as operations, provisioning and tuning Kafka and databases, planning HA, applying upgrades, and owning security and compliance yourself. Features many production deployments want, white-labeling, granular RBAC, customer hierarchy, LoRaWAN integrations, sit in the paid PE tier, so a growing CE project often becomes a PE or Cloud subscription plus the infrastructure it runs on.

TagoIO removes that layer entirely. The platform is operated for you under an ISO 27001-certified program, and when a project needs isolation, custom limits, or a specific region, TagoDeploy provides a dedicated instance without a migration to different software.

Dashboards and end-user delivery

Both platforms have strong dashboard builders; ThingsBoard’s widget library is extensive and its SCADA symbols suit industrial HMI-style views. TagoIO’s Blueprint dashboards address fleet scale, one layout serving hundreds of devices, and TagoRUN extends dashboards into a full end-user product: branded portal, user signup and access policies, custom email templates, and a mobile app under your own name. In ThingsBoard, white-labeling and customer-facing hierarchy are PE features, and a branded mobile app is your own build.

Custom logic

ThingsBoard’s visual Rule Engine chains processing nodes and covers a lot without code; extending beyond it means Java development against the platform. TagoIO’s model is code-first but serverless: write an Analysis in Node.js, Deno, or Python, and the platform runs it on triggers, schedules, or dashboard events. Platform analytics also carry past dashboards, turning telemetry into forecasts and predictions. Which model is more comfortable depends on your team; visual chains suit integrators who avoid code, scripts suit developers who want normal languages and libraries.

The bottom line

ThingsBoard fits best when self-hosting is a requirement or a strength: data sovereignty mandates, air-gapped environments, or teams that want Apache 2.0 software they control end to end, with commercial tiers available as needs grow.

TagoIO fits when you want the platform operated for you, dashboards and white-label portals as product features rather than license tiers, and a path from free prototype to dedicated instance without changing software. Both are proven platforms; the decision is mostly about who runs the infrastructure and where the application layer comes from.