Qubitro vs Azure IoT Hub
A managed device connectivity and messaging service that handles device identity, bidirectional messaging and routing into the rest of Azure, and deliberately leaves storage, dashboards and analytics to other services.
Azure IoT Hub is a managed connectivity and messaging service: device identity, secure bidirectional messaging, device twins, and routing onward into the rest of Azure. Microsoft describes it as a central message hub, and that scope is deliberate. It has no dashboards, no visualisation and no alerting, and no query layer over telemetry history — the IoT Hub query language covers twins and jobs, and message routing filters and forwards messages rather than notifying anyone. Nor is there meaningful storage: the built-in endpoint retains messages for one day by default and seven at most.
So the comparison is not feature against feature. It is an assembly against a product. With IoT Hub you get an excellent ingest and device-management layer and then choose your own storage, stream processing, analytics and front end — Storage, Event Hubs, Service Bus, Cosmos DB, Fabric, Functions — each with its own meter and its own operational surface. Qubitro is the whole path in one place: connect, decode, store, display, alert, and hand a branded portal to the customer.
Where Azure is stronger, it is clearly stronger. One million device identities per hub, device twins and fleet-wide jobs, the Device Provisioning Service for zero-touch factory provisioning, Entra ID and Private Link, sovereign and government clouds. If you already live in Azure or your fleet runs to the hundreds of thousands, that is the right answer and this page is not going to argue otherwise.
What Azure IoT Hub does well
- Scale very few platforms can match — up to a million device and module identities per hub, with throughput multiplied by units
- A mature bidirectional device-management model: device and module twins with desired and reported property reconciliation, direct methods with timeouts, fleet-wide jobs, and brokered file upload
- The Device Provisioning Service is a genuine differentiator — zero-touch just-in-time provisioning with X.509 and TPM, built for factory-line burn-in where devices exist before they are assigned to anyone
- Security and enterprise depth: per-device identity with SAS or X.509, TLS on every endpoint, Entra ID and Azure RBAC, Private Link, ARM and Bicep, Azure Policy, and sovereign and government clouds
- Reliability engineering documented unusually candidly — a 99.9% SLA on paid tiers, zone redundancy at no extra cost where available, and paired-region replication with customer-initiated failover
Side by side
| Azure IoT Hub | Qubitro | |
|---|---|---|
| What the product covers | Connectivity, device identity, messaging and routing | Connectivity plus storage, dashboards, alerting and portals |
| Dashboards | None — built in a separate Azure service | Included, pre-built per device template |
| Data storage | Built-in endpoint keeps one day by default, seven at most; route elsewhere to retain | Time-series storage with configurable retention |
| Device onboarding | Twins and SDKs; payload decoding is yours to write | 291 templates across 58 manufacturers with decoder and starter dashboard |
| Protocols | MQTT 3.1.1 subset on fixed system topics, AMQP 1.0, HTTPS; no MQTT 5 — that preview was deprecated and Microsoft now points MQTT 5 workloads at Event Grid's MQTT broker | MQTT 3.1.1 and 5, HTTP/HTTPS REST, webhooks, LoRaWAN via network server integrations |
| Fleet provisioning | DPS — zero-touch X.509 and TPM provisioning, custom allocation across hubs | Portal and API onboarding; no factory-line provisioning service |
| White-label | Not applicable — you build the front end | Custom domain, branding and per-tenant theming |
| Pricing shape | Tiered prepaid units carrying a daily message quota, metered in 4 KB chunks, with each routing destination billed separately | Usage-based from $2 per device per month, free tier available |
Choose Azure IoT Hub if
- Your organisation already runs on Azure — Entra ID, Azure RBAC, Private Link, Bicep, Azure Policy — and especially if you have an enterprise commitment to spend down
- The work is regulated, sovereign or public-sector: government and sovereign clouds, contractual data residency, a formal SLA with service credits, and a vendor-risk profile a small supplier will not clear
- Very large fleets, or devices manufactured before they are sold or assigned. A million-identity registry is real headroom, and DPS with TPM and X.509 is built for exactly that factory-line case
- You need deep device management or an industrial edge — desired-state configuration through twins, fleet-wide jobs, staged updates, and IoT Edge for offline operation
Choose Qubitro if
- You want storage, dashboards, alerting and a branded portal as part of the platform rather than as four or five further services to assemble, secure and bill
- You onboard commercial LoRaWAN and cellular sensors repeatedly and would rather select a decoder than write one
- There is no platform team to own capacity units, watch for throttling, or maintain routing pipelines and the front end that sits on top of them
- You resell to end customers and need per-customer white-label with per-device pricing simple enough to put in a quote
Common questions
- How does Azure IoT Hub pricing compare to Qubitro?
- The models are shaped differently, so a like-for-like figure is misleading. Azure IoT Hub is not priced per device — you buy tiered, prepaid units that carry a daily message quota, and a billable message is counted in 4 KB chunks, so a 100-byte reading and a 4 KB reading cost the same while a 6 KB one costs two. Most operations meter as messages, not just telemetry: cloud-to-device, direct method requests and their responses separately, twin reads, updates and queries. Overrunning the daily quota does not produce an overage charge — it stops the hub: sends and receives are blocked until the next UTC day unless you add units, and there is no native autoscale. Crucially, the hub is only the ingest line of an IoT bill; DPS, Device Update and every routing sink you land data in are separately metered. Qubitro is per device from $2 per device per month, with storage, dashboards and alerting included.
- Does Azure IoT Hub include dashboards and data storage?
- No, and it does not claim to. The built-in endpoint retains messages for one day by default and seven at most, so it is a buffer rather than a data store. To keep and view telemetry you route it to Blob or ADLS Gen2, Event Hubs, Service Bus, Cosmos DB or a Fabric eventstream — that last one still in preview — and build the visualisation on top yourself. Note that Time Series Insights was retired in July 2024, so any architecture diagram that ends there needs redrawing. Qubitro includes time-series storage with configurable retention, dashboards and alerting in the platform.
- Is Azure IoT Central being retired?
- This is repeated everywhere and it is not something Microsoft has announced. It traces back to an in-product system message posted in February 2024 which Microsoft corrected over the following days, calling it erroneous, and reaffirmed that retirements follow the standard Azure process with three years' notice. As of August 2026, Microsoft's public documentation shows no retirement date for IoT Central and new applications can still be created. Worth knowing which product you are costing, too: IoT Central is the per-device application platform, IoT Hub is the per-unit connectivity service, and they price nothing alike.
The fastest way to judge this is to connect one device. The free tier needs no card, and if your hardware is in the template library you will have a dashboard in minutes.