Photo: Growtika / Unsplash
What to weigh before you shortlist:
- Scope: device connectivity only, or also device management, OTA updates, rules and end-user apps
- Hosting: public cloud service, vendor-managed SaaS, self-hosted, or a mix with an edge runtime
- Protocols your devices already speak (MQTT, HTTPS, LwM2M, LoRaWAN, OPC UA) and the SDKs on offer
- Pricing unit: per message, per connected minute, per device, per megabyte or a flat subscription
- Exit cost: how devices are re-pointed and how data, registry and certificates are exported
- Vendor continuity: ownership, roadmap and support terms over the lifetime of your devices
At a glance
| Company | Good fit for | Headquarters |
|---|---|---|
| Amazon Web Services | Teams already building their backend on AWS | United States |
| Blynk | Product makers who need a branded mobile app quickly | United States |
| Cumulocity | Equipment makers and industrial firms that need cloud and on-prem options | Germany |
| Golioth | Firmware teams on microcontrollers who want OTA, logs and data routing | United States |
| HiveMQ | High-volume MQTT messaging and industrial unified namespace projects | Germany |
| Losant | OEMs building branded, multi-tenant monitoring apps | United States |
| Microsoft | Azure and Microsoft Fabric users who build their own app layer | United States |
| Particle | Teams wanting hardware, SIM and cloud from a single vendor | United States |
| ThingsBoard | Teams that want to self-host with a large dashboard toolkit | United States |
| Ubidots | Integrators reselling branded sensor dashboards | Colombia |
Listed in alphabetical order, not ranked. Nobody pays to appear on a shortlist, and paid directory placements get no preference here (see the editorial policy).
“IoT platform” covers products that do very different jobs. A hyperscaler service such as AWS IoT Core gives you a secure device endpoint and a rules layer, and leaves the application to you. A low-code platform gives you dashboards and customer apps on day one, but expects your devices to fit its model. A broker vendor sells messaging at scale and little else. Many buying mistakes start with comparing products from different groups as if they were the same thing. The guide to IoT platforms explains the layers in more detail.
What should the platform do for you?
List the jobs before you list the vendors. A typical connected product needs five: device connectivity and authentication, device management and OTA updates, data routing and storage, rules and alerts, and an application for operators or customers. Hyperscalers cover the first and parts of the next two, and expect you to build the rest. Application platforms cover the last three well and the first two to varying depths. Device-first services concentrate on firmware, logs and updates.
Write down which jobs you will build and which you will buy, then score vendors only on what you plan to buy. Hundreds of dashboard widgets are irrelevant if your customers will use your own app.
Which hosting model fits?
There are three basic models: a managed public cloud service, vendor SaaS, and self-hosting. Self-hosting gives you control over where data lives and lets you run on sites with no internet link, at the price of handling upgrades, backups and security patches yourself. SaaS moves that work to the vendor. Many industrial projects end up hybrid, with an edge runtime on site that buffers data when the link drops and a cloud tier for fleet-wide views. Ask whether the edge component is the same software as the cloud one or a separate product with its own release cycle.
How do pricing models compare?
Pricing units vary more than prices. AWS IoT Core bills connection time by the minute, messages in 5 KB increments, shadow and registry operations, and each rule evaluated and action executed, as its pricing page lists. Azure IoT Hub is sold in Basic and Standard tiers, and device management and IoT Edge need Standard. Device-first services tend to bill per active device and per megabyte; application platforms usually sell subscriptions by device count or feature set.
Model costs with your real traffic: payload size, reporting interval, how many rules each message triggers, and how long you keep raw data. Under 5 KB metering, a 6 KB payload counts as two messages, so trimming a payload can halve a line item. Then add the people who build and run whatever the platform leaves out, often the largest share of total cost of ownership.
Where does lock-in come from?
In IoT, vendor lock-in sits mostly in the device. Firmware built on a vendor SDK, certificates issued by the vendor’s CA, provisioning endpoints written to flash and proprietary device shadow semantics all have to change when you leave, and some devices in the field cannot be updated at all. Standard interfaces lower the exit cost: plain MQTT with your own topic structure, LwM2M for device management and Sparkplug for industrial data.
Services also change under you. Microsoft stopped creation of new Azure IoT Central applications on September 23, 2026 and will keep existing ones running through September 20, 2029, according to its IoT Central evolution page. Ownership changes count too: Particle is now part of Digi International, and Losant’s site now describes it as a SUSE company. Licenses move as well: the ThingsBoard documentation states that version 4.4 is source-available. None of this rules a vendor out, but each is a reason to read the support and license terms.
Questions to ask the vendor
- What does it take to move a device off your platform: which endpoints, credentials and firmware changes?
- Can we export raw data, the device registry and certificates in a documented format, and at what cost?
- Which parts run at the edge, and what happens when a site loses its connection for a day?
- How long are the SDK versions our firmware will ship with supported?
- Can you price a sample month from our actual message profile?
- What notice do you give before retiring a service, plan or API version?
If device messaging is the part you are designing first, MQTT vs HTTP covers which protocol fits which kind of device traffic.
How we built this list
The picks come from the IoT platforms category of our directory. We chose well-known vendors that cover the main platform types (hyperscaler services, application platforms, device-first services and MQTT infrastructure) and checked each description against the vendor’s official site on October 22, 2026. The list is alphabetical, not ranked, no vendor paid to appear, and we have not tested the products ourselves.
The shortlist
Amazon Web Services
Cloud provider offering AWS IoT Core, Greengrass and FleetWise for connecting and managing device fleets · Seattle, United States · founded 2006
Good fit for: Teams already building their backend on AWS.
AWS IoT Core accepts MQTT (including MQTT 5), HTTPS, MQTT over WebSockets and LoRaWAN, and its rules route messages to other AWS services; Greengrass, Device Management and SiteWise cover edge, fleets and industrial data. It fits teams whose backend already runs on AWS. The catch is that you assemble the application yourself from many separately metered services, so cost modeling takes real work.
Products: AWS IoT Core, AWS IoT Greengrass, AWS IoT Device Management, AWS IoT Device Defender, AWS IoT SiteWise, AWS IoT FleetWise, AWS IoT TwinMaker, FreeRTOS.
Blynk
Low-code platform for connected hardware with white-label mobile apps and device management · United States · founded 2014
Good fit for: Product makers who need a branded mobile app quickly.
A low-code platform for companies shipping a connected product: a device library, a no-code builder that publishes branded iOS and Android apps, fleet provisioning, user roles, rules and OTA firmware updates with staged rollouts and rollback. Strongest when the product needs a customer-facing mobile app. Heavy industrial analytics is not its focus, so plan a separate data layer if you need one.
Cumulocity
Independent IoT platform spun out of Software AG for device management, streaming analytics and apps · Düsseldorf, Germany · founded 2012
Good fit for: Equipment makers and industrial firms that need cloud and on-prem options.
An industrial IoT platform covering device management from onboarding to decommissioning, streaming analytics, dashboards, a digital twin manager and DataHub exports to data lakes. Devices connect through thin-edge.io, protocol adapters or SDKs, and the same solution can run in the cloud, at the edge, on premises or air-gapped. It is a full platform, which can be more than a small fleet needs.
Golioth
A device-to-cloud platform for Zephyr-based IoT products: OTA updates, logging, settings and data pipelines. · San Francisco, United States (remote-first) · founded 2020
Good fit for: Firmware teams on microcontrollers who want OTA, logs and data routing.
A device-to-cloud service for embedded teams: a firmware SDK, fleet control with device cohorts for targeted updates, remote logging, device settings and YAML pipelines that route data to other clouds without firmware changes. Works over Wi-Fi, cellular, Ethernet, Thread, or Bluetooth through gateways. Now part of Canonical. It does not build end-user dashboards or apps for you.
Products: Golioth Firmware SDK, Connect, Fleet Control, Pipelines, LightDB Stream, Logs, Location, Device Settings.
HiveMQ
Enterprise MQTT platform for connected vehicles, industrial data and large-scale device messaging · Landshut, Germany · founded 2012
Good fit for: High-volume MQTT messaging and industrial unified namespace projects.
An MQTT-based data platform: the HiveMQ broker, self-managed or fully managed, HiveMQ Edge for factory protocols, and extensions, with strong material on MQTT 5 and Sparkplug. A good fit when messaging at scale is the core requirement, for connected vehicles or a plant-wide unified namespace. It is not a device management or app-building platform, so pair it with other tools for OTA and dashboards.
Products: HiveMQ Platform, HiveMQ Broker, HiveMQ Cloud, HiveMQ Edge, HiveMQ Data Hub, HiveMQ Extensions, HiveMQ Community Edition.
Losant
Low-code enterprise IoT platform with visual workflows, dashboards and end-user experiences · Cincinnati, United States · founded 2015
Good fit for: OEMs building branded, multi-tenant monitoring apps.
A low-code application platform: a visual workflow engine, dashboards, multi-tenant end-user experiences with custom branding, and an edge agent that integrates with PLCs. It targets OEMs, industrial companies and telecoms building monitoring products. Losant is now a SUSE company, part of its edge business, so ask how the roadmap and licensing will evolve.
Products: Visual Workflow Engine, End-User Experiences, Data Visualization, Devices & Data Sources, Edge Compute, Application Templates, Notebooks, Developer Sandbox.
Microsoft
Azure IoT Hub, IoT Operations, Digital Twins and Device Update services on Microsoft's cloud · Redmond, United States · founded 1975
Good fit for: Azure and Microsoft Fabric users who build their own app layer.
Azure IoT Hub handles device connectivity over MQTT, AMQP and HTTPS, with the Device Provisioning Service for zero-touch onboarding and IoT Edge for modules on site; IoT Operations targets industrial sites. It suits Azure shops and Fabric users. Azure IoT Central, the managed application layer, no longer accepts new applications, so new projects build on IoT Hub and assemble the rest.
Products: Azure IoT Hub, Azure IoT Operations, Azure IoT Edge, Azure Digital Twins, Device Update for IoT Hub, IoT Hub Device Provisioning Service, Azure Device Registry, Azure IoT Central.
Particle
An integrated IoT platform combining cellular and Wi-Fi hardware, device OS, connectivity and cloud management. · San Francisco, United States · founded 2012
Good fit for: Teams wanting hardware, SIM and cloud from a single vendor.
An integrated stack: cellular and Wi-Fi boards and modules, Device OS firmware, the EtherSIM global SIM, OTA updates with controlled rollouts, and a cloud with an event bus, serverless Logic and over 250 integrations. It fits teams who want hardware, connectivity and cloud from one supplier. The flip side is coupling to Particle hardware. Digi International completed its acquisition of Particle in January 2026.
Products: Device OS, Particle Device Cloud, EtherSIM, Boron, Photon 2, M-Series and M-SoM, Tachyon, Ledger.
ThingsBoard
Source-available IoT platform (Apache 2.0 up to 4.3, BSL 1.1 from 4.4) for device management, rule chains and dashboards · United States · founded 2016
Good fit for: Teams that want to self-host with a large dashboard toolkit.
Device management, rule chains, alarms and more than 600 dashboard widgets, with connections over MQTT, HTTP, CoAP and LoRaWAN, and industrial protocols such as Modbus, OPC UA and BACnet through its IoT Gateway. Runs on premises, air-gapped or as ThingsBoard Cloud. From version 4.4 the code is source-available rather than open source, so read the license before building a commercial service on it.
Products: ThingsBoard Community Edition, ThingsBoard Professional Edition, ThingsBoard Cloud, ThingsBoard Edge, ThingsBoard IoT Gateway, Trendz Analytics.
Ubidots
IoT application builder with dashboards, alerts and white-label apps for sensor data · Colombia · founded 2013
Good fit for: Integrators reselling branded sensor dashboards.
An application builder for sensor data: dashboards, an events and rules engine, white-label apps on your own domain, and ingestion over MQTT, HTTP, TCP or UDP, plus integrations with AWS IoT, Particle and The Things Industries. Aimed at industrial and utility users and at integrators reselling branded monitoring. Its site centers on data and apps, so check device management and OTA needs separately.
Picks, products and the notes above were checked on the vendors' official sites on October 22, 2026. Plans and prices change; the official page is the reference. A vendor missing or described wrongly? Tell us.