Why teams pick EdgeHub
Managing a fleet of deployed IoT devices is a different problem to managing a fleet of cloud services. Cloud services can be updated in seconds with zero downtime. A firmware update to a device in the field can brick it if the update process is interrupted, can be rejected by a device that has drifted from the expected baseline, or can introduce a bug that makes the device unresponsive — at which point physical recovery is the only option.
EdgeHub treats the update process as a risk-managed operation rather than a deployment pipeline. Every firmware artifact is signed before it leaves the system. The dual-bank bootloader on the device means a bad update is self-recovering — three failed boot attempts and the device reverts to the previous firmware automatically. The cohort rollout means a problem with the new firmware is discovered on 1% of the fleet, not 100%.
The remote configuration push feature reduces the number of firmware releases required. Parameters that change — sampling intervals, alert thresholds, connection retry delays — can be updated via MQTT without a firmware release. This keeps firmware updates rare and deliberate rather than frequent and routine, which is the right risk posture for devices in the field.
Who it is for
EdgeHub is used by IoT product companies managing deployed device fleets, industrial automation OEMs with equipment in the field, connected consumer product companies, and any organisation that needs to update firmware on devices it cannot physically reach.