Commissioned Research
Top 10 Best IoT Software of 2026

GITNUXSOFTWARE REVIEW

AI In Industry

Top 10 Best IoT Software of 2026

Editorial roundup of iot software options for teams, outlining key tradeoffs and fit, including ThingsBoard, Ubidots, and Balena.

22 min readUpdated Editorially scoped research
How we ranked these tools
01Editorial Scope

Vendors set the topic, but our editors set the inclusion criteria and the evaluation framework before research starts.

02Source Research

Search agents gather the source set and the review record, including transcriptions of video reviews and podcasts.

Read our full methodology →

Framework: Features 40% · Ease 30% · Value 30%

Gitnux may earn a commission through links on this page. This does not influence our reviews. Editorial policy

IoT software determines how device data is ingested, modeled, and routed into dashboards and alerts, and how updates, access controls, and audit trails work across fleets. This comparison helps analysts and operators weigh tradeoffs between managed connectivity like cloud IoT hubs and application platforms that manage rules, telemetry, and edge deployment workflows.

ThingsBoard is the best pick for teams that need device provisioning plus governance and hands-on telemetry automation, because its visual rule engine turns incoming data into server-side actions feeding dashboards and webhooks, whereas Balena is a stronger fit for containerized edge fleets needing release-based OTA updates across many hardware variants.

Editor’s top 3 picks

Three quick recommendations before you dive into the full comparison below — each one leads on a different dimension.

Editor pick
1

ThingsBoard

The ThingsBoard rule engine enables server-side telemetry automation using a configurable processing graph.

Best for: Fits when teams need device provisioning, RBAC governance, and visual automation driving telemetry actions.

2

Ubidots

Editor pick

Telemetry rule engine that triggers automations and device actions from stored metrics and live events.

Best for: Fits when IoT teams need rule-based automation with dashboards and API access, mainly over MQTT and HTTP.

3

Balena

Editor pick

Release-based fleet deployment that updates running edge devices by application version, not manual per-device scripting.

Best for: Fits when teams need containerized edge workloads with release-driven OTA updates and fleet-level automation.

Comparison Table

1
ThingsBoardBest overall
SMB
9.1/10
Overall
2
8.7/10
Overall
3
edge
8.6/10
Overall
4
enterprise
8.3/10
Overall
5
8.1/10
Overall
6
enterprise
7.7/10
Overall
7
API-first
7.6/10
Overall
8
SMB
7.1/10
Overall
9
6.8/10
Overall
10
6.6/10
Overall
#1

ThingsBoard

SMB

Open-source IoT platform for device management, data collection, rule processing, and dashboards.

9.1/10
Overall
Features9.1/10
Ease of Use9.0/10
Value9.2/10
Standout feature

The ThingsBoard rule engine enables server-side telemetry automation using a configurable processing graph.

ThingsBoard ingests telemetry and events into a built-in time-series data store, then processes them through a server-side rule engine that supports conditional logic and chained actions. It provides an asset hierarchy and device management workflow so organizations can group devices, bind telemetry to assets, and manage ownership at the RBAC layer. Integration depth comes from protocol adapters for common industrial and messaging patterns and from REST-based APIs for provisioning, telemetry retrieval, and configuration automation.

A key tradeoff is that building complex automation often requires translating workflows into rule nodes rather than writing a general-purpose stream processor. ThingsBoard fits when a team wants rapid setup of dashboards, notifications, and webhook calls from live telemetry without building a custom event processing service. It fits less when most automation must be implemented in an external microservice and only minimal UI and rule processing are needed.

Pros
  • +Visual rule engine routes telemetry to dashboards, webhooks, and notifications
  • +Asset hierarchy supports organizational mapping across fleets and deployments
  • +Time-series storage and retention align with common telemetry use cases
  • +RBAC supports multi-tenant governance for device and asset access
Cons
  • –Rule graphs can become hard to maintain for high-branching logic
  • –Custom protocol adapters may require additional development effort
  • –Advanced data transformation often depends on rule configuration patterns
  • –Operational tuning needs active management for high-ingestion environments
Use scenarios
  • Industrial IoT operations

    Alarm routing from device telemetry

    Faster incident response

  • Device management teams

    Fleet onboarding and lifecycle tracking

    Lower onboarding friction

Show 2 more scenarios
  • Integration engineers

    Bi-directional system connectivity

    Reduced custom plumbing

    APIs and connector adapters manage configuration and expose telemetry for downstream services.

  • Field service organizations

    Operational dashboards for distributed sites

    Better maintenance planning

    Dashboards visualize live metrics and fleet status using time-series data and asset structure.

Best for: Fits when teams need device provisioning, RBAC governance, and visual automation driving telemetry actions.

#2

Ubidots

SMB

IoT application enablement platform for device data ingestion, dashboards, alerts, and analytics.

8.7/10
Overall
Features8.7/10
Ease of Use8.7/10
Value8.7/10
Standout feature

Telemetry rule engine that triggers automations and device actions from stored metrics and live events.

Ubidots provides a workflow-oriented rule engine for turning telemetry into events, notifications, and actuator commands. Dashboards and widgets consume stored metrics and help teams validate deployments from ingestion to visualization. A device lifecycle workflow exists for provisioning device identities and tracking device state in a way that maps to fleet operations.

A key tradeoff is that deeper protocol support and edge-specific behaviors often require additional adapters outside Ubidots. Ubidots fits best when teams already publish telemetry via MQTT or HTTP and need centralized rules, dashboards, and an API to integrate with ticketing, analytics, or internal services.

Pros
  • +Rule engine converts telemetry into notifications and actuator calls
  • +Device organization supports fleet-level views for operations teams
  • +HTTP and MQTT integration enables app and gateway connectivity
  • +Dashboards use stored time-series data for quick verification
Cons
  • –Advanced southbound protocol coverage may require external adapters
  • –Complex topic namespace and payload codec design needs careful setup
  • –High-volume ingestion tuning can require governance around rules and retention
  • –Cross-tenant governance features feel lighter than enterprise device platforms
Use scenarios
  • Field operations teams

    Monitor device health across multiple sites

    Faster incident detection and routing

  • Industrial automation engineers

    Coordinate control commands from telemetry

    Lower custom backend workload

Show 2 more scenarios
  • Platform integration teams

    Send telemetry to internal services

    Consistent data access patterns

    The northbound API supports pulling telemetry and events into existing applications.

  • Device onboarding teams

    Provision identities for new devices

    Reduced onboarding friction

    Device lifecycle tooling tracks device registration and enables group-level management.

Best for: Fits when IoT teams need rule-based automation with dashboards and API access, mainly over MQTT and HTTP.

#3

Balena

edge

Platform for deploying, updating, and managing fleets of connected Linux devices at the edge.

8.6/10
Overall
Features8.6/10
Ease of Use8.6/10
Value8.6/10
Standout feature

Release-based fleet deployment that updates running edge devices by application version, not manual per-device scripting.

Balena combines fleet provisioning, remote application updates, and hardware-focused deployment tools for edge and constrained device runtimes. It packages device workloads as containerized services and manages lifecycle at the fleet level, which reduces manual scripting across teams.

Balena also exposes an API and supports automation around device and application states, which helps integrate telemetry ingestion pipelines and operational workflows. Its strongest fit comes when edge nodes need repeatable setup and predictable OTA firmware update behavior tied to releases.

Pros
  • +Release-based OTA updates coordinate multi-container app changes across fleets
  • +Fleet provisioning supports consistent device setup across many hardware variants
  • +API supports automation for device state, logs, and application deployments
  • +Container-native workflow aligns edge services with reproducible builds
Cons
  • –Deep integration with non-container workflows needs custom adapters
  • –Topic namespace design and payload codec choices still require customer discipline
  • –Advanced device governance like RBAC granularity can be limiting for strict org models
  • –Edge-to-cloud sync patterns require careful engineering for offline buffering
Use scenarios
  • IoT support reliability teams

    Track device health during fleet releases

    Faster update issue investigation

  • Edge developers

    Promote containerized changes across fleets

    More consistent software rollouts

Show 2 more scenarios
  • IoT software teams

    Push container updates to connected devices

    Reliable remote application delivery

    Deploy containerized application releases through a repeatable OTA workflow to Linux edge nodes.

  • Embedded device teams

    Coordinate firmware and application versions

    Controlled coordinated fleet updates

    Deliver firmware and applications using the same controlled process with versioned release artifacts.

Best for: Fits when teams need containerized edge workloads with release-driven OTA updates and fleet-level automation.

#4

PTC ThingWorx

enterprise

Industrial IoT platform for application development, asset monitoring, and connected operations.

8.3/10
Overall
Features8.3/10
Ease of Use8.3/10
Value8.3/10
Standout feature

Model-driven asset and capability design that directly drives service logic and automation across device-connected workflows.

PTC ThingWorx targets industrial and edge-connected IoT teams that need application logic next to device integration. It combines a model-driven asset and capability structure with a configurable rules and workflow layer for triggering actions from telemetry.

Pros
  • +Asset and capability modeling maps real industrial hierarchies to runtime services
  • +Built-in rule and workflow execution supports event-driven automation without external orchestration
  • +Extensible services and scripting cover custom integrations and data transformations
  • +Operational monitoring tracks service health and device connectivity for live troubleshooting
Cons
  • –Complex configurations can slow onboarding for teams without prior ThingWorx experience
  • –Deep device lifecycle management often depends on additional connectors and integration work
  • –High-throughput telemetry pipelines may require careful tuning of ingestion and processing
  • –Protocol breadth for industrial protocols can hinge on companion components
Use scenarios
  • Manufacturing application developers and operators

    Automate plant equipment workflows from live telemetry

    Purpose-built connected manufacturing apps

  • Engineering and operations digital twin teams

    Model equipment and sites with operational state

    Shared operational asset view

Show 2 more scenarios
  • Enterprise manufacturing transformation leaders

    Roll out connected apps by site phase

    Incremental enterprise digital thread

    Deploy connected asset and manufacturing applications in stages to expand operational context over time.

  • Quality and process engineering teams

    Route nonconformance events through traceable workflows

    More traceable exception handling

    Link production or asset events with trace context and route issues via structured workflows.

Best for: Fits when industrial IoT teams need modeled assets plus automation tied to device data flows.

#5

Blynk

SMB

IoT software platform for device provisioning, mobile apps, dashboards, and fleet management.

8.1/10
Overall
Features8.1/10
Ease of Use8.2/10
Value8.0/10
Standout feature

Visual dashboard widgets tied to device variables, plus built-in event triggers that drive device control flows.

Blynk runs a cloud-to-device workflow for monitoring and controlling devices with a focus on building interactive dashboards. It provides app-driven UI, device management through named projects, and a rules layer that can trigger actions from incoming telemetry.

Pros
  • +App and dashboard widgets map directly to live telemetry variables
  • +Event-based triggers let rules drive device actions from telemetry changes
  • +Project-based device organization helps teams keep hardware and apps aligned
  • +Clear device connection lifecycle feedback supports day-to-day operations
Cons
  • –Limited visibility into message-level delivery semantics beyond basic status
  • –Advanced protocol diversity depends on gateway or compatible device SDK choices
  • –Complex multi-tenant governance and audit controls are narrower than enterprise IoT suites
  • –Custom data processing often requires external services outside Blynk
Use scenarios
  • IoT developers and operations teams

    Monitor sensors on live dashboard views

    Faster device health monitoring

  • Facilities and agriculture operators

    Trigger alerts from sensor thresholds

    Actionable alerts and responses

Show 2 more scenarios
  • Smart infrastructure and public tech

    Automate rule-based workflows for assets

    Coordinated monitoring and automation

    Apply rule-driven actions to distributed devices for targeted infrastructure responses.

  • Hardware product and prototype teams

    Validate connected-device telemetry interactions

    Quicker prototype validation

    Build working app interfaces and telemetry flows with minimal custom application effort.

Best for: Fits when teams need fast UI-driven device control and simple telemetry-to-action automation.

#6

AWS IoT Core

enterprise

Managed cloud service for connecting, securing, and routing data from IoT devices.

7.7/10
Overall
Features7.7/10
Ease of Use7.7/10
Value7.7/10
Standout feature

Device provisioning with certificate-based fleet onboarding integrated into AWS identity workflows.

AWS IoT Core is a managed cloud IoT service that turns device messages into actionable workflows with AWS-native integration points. It includes a device registry, MQTT-based message ingestion, and device shadows for stateful modeling across unreliable connectivity.

Pros
  • +MQTT message ingestion with topic routing that aligns with AWS Rule Engine patterns
  • +Device shadows provide last-known state for clients that reconnect after offline periods
  • +X.509 certificate-based authentication supports scoped identity across device fleets
  • +Built-in rules can forward telemetry into multiple AWS services without building a broker layer
Cons
  • –Rule engine expressions and topic design require careful planning to avoid brittle routing
  • –Offline buffering behavior is limited to specific mechanisms and does not replace gateway store-and-forward
  • –Operational debugging spans IoT Core logs and downstream service logs across AWS accounts
  • –Advanced protocol bridging to industrial protocols typically depends on separate AWS IoT components or connectors
Use scenarios
  • Operations teams in utilities

    Monitor and control field device telemetry

    Faster incident response

  • IoT engineering teams at enterprises

    Sync device state during intermittent connectivity

    Reduced manual reconfiguration

Show 2 more scenarios
  • Security and compliance engineers

    Provision devices with certificate authentication

    Tighter access control

    Manages certificate-based authentication and integrates with AWS identity patterns for controlled access.

  • Product teams building smart devices

    Trigger AWS automation from device events

    Automated device workflows

    Applies IoT rules to route telemetry into AWS services for processing and actuation logic.

Best for: Fits when AWS-heavy IoT programs need managed device onboarding, MQTT ingestion, and rule-based routing into cloud services.

#7

EMQX

API-first

MQTT platform for large-scale IoT messaging, device connectivity, and data integration.

7.6/10
Overall
Features7.6/10
Ease of Use7.6/10
Value7.6/10
Standout feature

MQTT rule engine with built-in topic-driven processing and connector outputs for telemetry pipelines.

EMQX focuses on message queuing and delivery control for MQTT, including configurable QoS handling and topic-based routing into the rule engine. It offers protocol adapters and connector modules so gateway, edge, and enterprise integrations can be wired without building a custom broker from scratch. EMQX exposes a management surface that supports automated configuration workflows such as provisioning updates and operational introspection for running clusters.

Pros
  • +Rule engine routes MQTT telemetry to external systems with configurable transformations
  • +Cluster-ready broker design supports consistent client connectivity at scale
  • +Certificate-based authentication and multi-tenant controls support operational governance
  • +Protocol adapters reduce custom bridge code for heterogeneous device networks
Cons
  • –Rule and topic namespace design mistakes can create hot spots and noisy retries
  • –Advanced governance workflows require disciplined configuration management
  • –Non-MQTT integration paths depend on adapter coverage and connector configuration
Use scenarios
  • Edge platform teams

    Gateway to cloud telemetry routing

    Lower custom integration work

  • Operations teams

    Clustered broker monitoring and control

    Faster troubleshooting

Show 2 more scenarios
  • Device connectivity teams

    Certificate-authenticated fleet access control

    Tighter fleet governance

    X.509-based authentication and tenant isolation help manage large fleets with consistent access rules.

  • Industrial integration teams

    Protocol adapter bridging to systems

    Fewer protocol bridge components

    Protocol adapters connect industrial payload sources to MQTT topics for downstream processing.

Best for: Fits when IoT teams need clustered MQTT connectivity, automation hooks, and rule-driven telemetry routing.

#8

Kaa

SMB

IoT platform for device management, data collection, digital twins, and application development.

7.1/10
Overall
Features7.1/10
Ease of Use7.1/10
Value7.1/10
Standout feature

Fleet device lifecycle management with provisioning and event-driven automation wired for operational control.

Kaa focuses on device lifecycle management and orchestration across fleets rather than only routing telemetry. The system provides northbound APIs for application integration and automation hooks for acting on device events.

Pros
  • +Device onboarding workflows that reduce custom provisioning glue work
  • +Northbound API surface for integrating telemetry, commands, and fleet actions
  • +Automation hooks tied to device events for operational responses
  • +Tenant and role boundaries for segregating fleet operations
Cons
  • –More configuration overhead than broker-only stacks
  • –Automation rules need careful design to avoid conflicting actions
  • –Protocol integration coverage can require additional adapters per environment
  • –Operational troubleshooting depends on understanding Kaa’s internal message flow
Use scenarios
  • IoT architects and embedded teams

    Connect edge devices to cloud apps

    Coordinated edge to cloud flow

  • Reliability and operations teams

    Alert on device events and telemetry

    Earlier device condition awareness

Show 2 more scenarios
  • Data and IoT analytics engineers

    Ingest sensor streams for analytics

    Telemetry for dashboards and reports

    Collect and process sensor telemetry into pipelines ready for real-time and scheduled analysis.

  • Device operations and platform teams

    Automate fleet onboarding and provisioning

    Reduced manual provisioning effort

    Register devices, establish identities, and run repeatable onboarding workflows at fleet scale.

Best for: Fits when IoT teams need fleet provisioning and event-driven automation with an integration-first API.

#9

Arduino Cloud

SMB

Cloud service for connecting Arduino and compatible devices, managing fleets, and building dashboards.

6.8/10
Overall
Features6.8/10
Ease of Use6.8/10
Value6.8/10
Standout feature

Cloud variables with tight sketch integration make telemetry and actuator wiring fast, without designing a separate northbound API.

Arduino Cloud targets teams that want to connect Arduino hardware to the cloud with minimal backend work and consistent device workflows. It provides managed device provisioning, a web-based dashboard for telemetry and actuator control, and built-in support for Arduino-centric sketches with cloud variables.

Pros
  • +Managed device provisioning and onboarding for Arduino-first projects
  • +Cloud variables link directly to sketches for telemetry and actuator state
  • +Web dashboards reduce custom UI work for common device views
  • +OTA firmware update workflow supported for supported Arduino boards
Cons
  • –Protocol reach is narrow compared with MQTT brokers and industrial gateways
  • –Advanced fleet governance controls are limited for large-scale enterprise operations
  • –Custom message processing and rule logic require external services outside Arduino Cloud
  • –Data export and event streaming options are less flexible than dedicated telemetry pipelines
Use scenarios
  • Maker teams prototyping IoT

    Remote monitor sensor boards from dashboard

    Faster prototype validation

  • Product engineering teams

    Run OTA updates on managed devices

    Reduced deployment risk

Show 2 more scenarios
  • IoT operations teams

    Control actuators with web interfaces

    Lower operational overhead

    Operators trigger actuator actions from the web dashboard while tracking device state changes.

  • Automation and integrations teams

    Sync device data through API layer

    Less custom integration work

    Teams connect external systems to device data via the exposed API layer and workflows.

Best for: Fits when IoT teams need Arduino-focused device management with dashboards and OTA updates, not custom broker integrations.

#10

Microsoft Azure IoT Hub

enterprise

Cloud platform for secure device connectivity, management, and bi-directional messaging.

6.6/10
Overall
Features6.6/10
Ease of Use6.6/10
Value6.6/10
Standout feature

IoT Hub message routing rules connect telemetry to multiple Azure endpoints with filtering and transformation.

Microsoft Azure IoT Hub routes device messages to cloud endpoints and manages device identities and communication at scale. It provides a rule engine that can fan out telemetry to Azure services using message routing, filtering, and transformations.

Pros
  • +Built-in rule engine routes messages to Azure services with filters
  • +MQTT support covers common QoS messaging patterns for telemetry and commands
  • +Device identity and authorization integrate with Azure RBAC and access controls
  • +Operational tooling provides monitoring for ingress, egress, and throttling
Cons
  • –Higher-end automation workflows depend on additional Azure services and pipelines
  • –Complex topic namespace design and payload conventions still require team standards
  • –Gateway offline buffering is not provided inside IoT Hub and must be handled upstream
  • –High-scale deployments need careful partitioning strategy for throughput stability
Use scenarios
  • Industrial IoT operations teams

    Route sensor telemetry to analytics pipelines

    Reduced downtime and faster detection

  • Embedded systems developers

    Ingest device data via MQTT

    Simplified device onboarding

Show 2 more scenarios
  • Enterprise integration architects

    Fan out messages to multiple endpoints

    Lower integration maintenance effort

    Rule engine routes single telemetry streams to multiple Azure destinations with filtering and transformations.

  • Security and identity administrators

    Manage device identities at scale

    Stronger device access control

    IoT Hub provisions and manages device access so authentication and permissions stay consistent across fleets.

Best for: Fits when Azure-centered teams need message routing, device identity controls, and command delivery across many device types.

Conclusion

After evaluating 10 iot software, ThingsBoard stands out as our overall top pick — it scored highest across our combined criteria of features, ease of use, and value, which is why it sits at #1 in the rankings above.

Our Top Pick
ThingsBoard

Use the comparison table and detailed reviews above to validate the fit against your own requirements before committing to a tool.

Frequently Asked Questions About Iot Software

How do AWS IoT Core, Azure IoT Hub, and Google Cloud IoT Core handle device state when connections drop?
AWS IoT Core provides device shadows to track desired and reported state during intermittent connectivity. Azure IoT Hub supports device identity and routing rules, but device state management typically pairs with Azure services rather than a single shadow primitive. In practice, these differences affect how teams model state transitions before commands resume.
Which platform is better for MQTT throughput with protocol translation at the broker layer?
EMQX targets high-throughput MQTT connectivity and supports protocol translation near the broker boundary. AWS IoT Core and Azure IoT Hub also handle MQTT ingestion, but the broker layer is managed as part of the cloud service rather than tuned as an edge component. Teams that run the broker close to the site often prefer EMQX for predictable ingestion behavior.
How do rule engines differ across ThingsBoard, EMQX, and Ubidots for telemetry processing?
ThingsBoard uses a visual IoT rule engine that builds a configurable processing graph for telemetry routing and transformations. EMQX adds topic-driven processing inside the MQTT rule engine and pushes connector outputs into external telemetry pipelines. Ubidots applies rules tied to stored metrics and live events, then triggers automations through its northbound API.
What integrations and APIs are available for consuming telemetry and triggering automation from external applications?
Ubidots exposes a northbound API designed for data access and rule-triggered workflows. ThingsBoard also provides a northbound API and can route telemetry into HTTP integrations. Kaa focuses on northbound APIs for fleet integration and event-driven automation tied to device lifecycle actions.
How do these systems support SSO and RBAC, and where does access control get enforced?
ThingsBoard supports role-based access control in multi-tenant deployments and governs access through its admin surface. PTC ThingWorx emphasizes governance through user roles and runtime configuration for connected devices and services. AWS IoT Core and Azure IoT Hub enforce device identity and access through their cloud identity patterns, while app-level RBAC is typically implemented in downstream services.
When onboarding a large fleet, what data migration and provisioning workflows are typically required?
AWS IoT Core provisions devices into its registry using certificate-based fleet onboarding, which changes how identities enter the system. Kaa focuses on provisioning workflows as part of device lifecycle management, which can reduce custom wiring during onboarding. Balena supports fleet provisioning tied to application release and updates, so migration often includes mapping existing devices to fleet manifests.
How does device command delivery differ between command-focused platforms and telemetry-first routing tools?
Azure IoT Hub is built around routing and command delivery across device identities, so command flows map directly to its messaging patterns. Blynk centers on device control flows driven by REST-style patterns and event triggers tied to device variables. EMQX is oriented around MQTT ingestion and rule-based routing, so command delivery typically depends on how integrations map outgoing control topics to device-side handlers.
What breaks if device identity and certificate handling are not aligned with each platform's security model?
AWS IoT Core relies on certificate-based authentication and ties provisioning to its identity workflows, so mismatched certificates can block onboarding and message acceptance. EMQX uses certificate-based authentication paths for clients, and invalid rotation behavior can interrupt telemetry continuity. Azure IoT Hub also manages device identities, so incorrect identity provisioning can cause rule routing and command delivery to fail for affected devices.
Where does edge buffering and edge-to-cloud sync fall short when compared with full cloud-managed ingestion?
Balena supports constrained device runtime packaging and release-driven OTA updates, which helps edge-to-cloud behavior dependably track application version and connectivity. EMQX can buffer and route at the broker boundary when configured for edge or cloud deployment, which reduces reliance on cloud uptime for ingestion. Cloud-managed services like AWS IoT Core and Azure IoT Hub handle message acceptance centrally, so outages can shift the burden to client-side retry and any companion buffering logic outside the service.

Tools reviewed

Primary sources checked during evaluation.

Referenced in the comparison table and product reviews above.

How to Choose the Right Iot Software

Options differ most in how well they expose device workflows through integration depth and automation and how precisely the data model is kept consistent across device-to-cloud flows. When we compare products, we look for strong admin and governance controls you can verify, not just marketing claims.

Integration depth via API and webhooks

Why it matters

In iot software, the value often comes from stitching device events into your existing tools without manual steps. Integration depth via API and webhooks matters when you need fast reaction to device state changes and predictable automation.

How to check

Ask the demo team to show a sample workflow: create an event from a device, then trigger a webhook/API call into an external service. Check whether events include correlation fields (device id, timestamp, reason) and whether retries and response statuses are visible.

Consistent data model and schemas

Why it matters

In iot software, inconsistent schemas turn automation into custom glue code. A consistent data model helps you keep device attributes, commands, and telemetry aligned across device types and over time.

How to check

Request a look at the schema or mapping view for a few device types (e.g., sensors with different units). Try exporting or querying the same fields twice and confirm the field names, types, and units stay stable and documented.

Automation flows for device commands

Why it matters

Device control is where automation shows its real limits. Automation flows for device commands matter when you need repeatable actions like configuration changes or staged resets tied to device state.

How to check

During the demo, ask for a command workflow that depends on current device state (for example, only run after an online check). Verify you can inspect the command lifecycle: created, sent, acknowledged, failed, and how failures are handled.

Admin and governance controls with RBAC

Why it matters

As device fleets grow, admin and governance controls prevent accidental changes and unclear ownership. RBAC plus audit capability is critical for safely operating iot software across teams.

How to check

Ask to review roles and permissions in the console: who can view devices, issue commands, change configuration, and manage users. Then request an audit log example showing who changed what and when, and whether it includes before/after values.

Operational observability for device status

Why it matters

In iot software, you need to understand what happened when devices misbehave. Observability helps you debug ingestion, delivery, and command outcomes without guessing.

How to check

Ask to see device health/status pages and logs for a test device that goes offline and comes back. Confirm you can trace a single device event through timestamps and see delivery/ack outcomes for commands.

Provisioning workflow for new devices

Why it matters

Provisioning determines how quickly teams can add devices without fragile manual steps. A clear provisioning workflow also reduces operational drift when devices change ownership or configuration.

How to check

In the demo, ask for the steps to onboard a new device: what fields are required, where you enter credentials/identifiers, and how you bind it to the right configuration. Check whether you can simulate onboarding in a sandbox-like environment without impacting live devices.

Red flags

  • APIs and webhooks are shown only as screenshots, not as working end-to-end traces
  • Schemas change names/types across device types without clear migration guidance
  • RBAC and audit logs are vague or missing for configuration and command actions

Fit by situation

  • If our team needs event-driven automation into other systems, prioritize integration depth via API and webhooks.
  • If we run multiple device types with long-lived deployments, prioritize consistent data model and schemas.
  • If several operators manage fleets across roles, prioritize admin and governance controls with RBAC.
Commissioned Research

Funding and competing interests

This study was co-funded by several of the vendors assessed in it. No single vendor funded it. Funders could propose the market studied.

They had no role in selecting vendors, setting or weighting criteria, analysing data or drawing conclusions, and they received the same factual-accuracy check as every other vendor assessed.

Market definition, inclusion rules and criteria weights were fixed by an editor before research began and did not change afterwards. Editorial process →

Keep exploring

FOR SOFTWARE VENDORS

Not on this list? Let’s fix that.

Our best-of pages are how many teams discover and compare tools in this space. If you think your product belongs in this lineup, we’d like to hear from you—we’ll walk you through fit and what an editorial entry looks like.

Apply for a Listing

WHAT THIS INCLUDES

  • Where buyers compare

    Readers come to these pages to shortlist software—your product shows up in that moment, not in a random sidebar.

  • Editorial write-up

    We describe your product in our own words and check the facts before anything goes live.

  • On-page brand presence

    You appear in the roundup the same way as other tools we cover: name, positioning, and a clear next step for readers who want to learn more.

  • Kept up to date

    We refresh lists on a regular rhythm so the category page stays useful as products and pricing change.