RT-IoT Hub
Cloud-ready IoT connectivity with device management, OTA, and telemetry.
RT-IoT Hub is the connectivity layer we stopped rewriting. Across water metering, HVAC cloud integration and smart-home deployments the same problems kept arriving in a different order: devices speak different protocols, firmware has to move safely across a fleet that is never fully online, and somebody needs to see what the field is actually doing. The Hub is the part of that work we made reusable.
It sits between your devices and your application. Devices connect over MQTT, CoAP or plain HTTP; the Hub normalises them into one device model, holds the declared state for each one, and reconciles it when a device reconnects. Firmware rolls out in stages you control rather than all at once. Telemetry lands in dashboards from the first day rather than after the first integration sprint.
Multi-protocol gateway
MQTT, CoAP and HTTP arrive on one ingress path and leave as one device model.
Staged OTA updates
Roll firmware to a cohort, watch it, then widen — or stop.
Device twin
Declared state per device, reconciled the moment it reconnects.
Telemetry dashboards
Live metrics per device and across the fleet, without building a UI first.
Provisioning and identity
Each device gets its own credentials at manufacture, not a shared key.
Offline tolerance
Queued state and resumable transfers for devices on intermittent links.
Provision
The device receives its identity and certificates during manufacturing.
Connect
It reaches the gateway over whichever protocol its hardware supports.
Reconcile
The Hub compares reported state against declared state and closes the gap.
Operate
Telemetry streams to dashboards; OTA campaigns roll out in controlled stages.
Smart Energy
Metering fleets reporting consumption from sites with unreliable connectivity.
Industrial IoT
HVAC and equipment estates that need remote configuration and firmware control.
Medical & HealthTech
Connected devices where every firmware version in the field must be accounted for.
