Device Management
A single connected device is easy. Ten thousand of them, across three companies and several customers, is an operations problem. Device Management holds fleet identity, secure onboarding, certificate lifecycle, configuration and health reporting for everything the group deploys.
Inside the platform
Identity & provisioning
Per-device identity issued at manufacture, with secure onboarding that does not depend on a shared secret in a config file.
Certificate lifecycle
Issue, rotate and revoke device credentials across a fleet without a truck roll.
Configuration & inventory
What is deployed, where, running which firmware and configuration — answerable without asking a field engineer.
Health & diagnostics
Device health reporting and remote diagnostics, so a failure is characterised before anyone drives to site.
The shape of the work
Device to dashboard — and back again
Connected products fail at the seams. The return path — commands and over-the-air updates — is designed at the same time as the forward path, not bolted on after the first fleet ships.
Used across the group
- Every division with deployed hardware
Ownership
A shared platform. It has no natural home in any single unit, so the group funds it centrally and the shared engineering bench maintains it. Every company and division draws on the same version.
How we decide what is sharedOther platforms
Firmware SDK
The common embedded foundation — hardware abstraction, drivers, secure boot and update, with timing you can reason about.
Read moreOTA Platform
Staged, reversible firmware campaigns across a fleet — the return path designed at the same time as the forward one.
Read morePCB Library
Verified footprints, reference blocks and an approved-parts list — the electronics bench's institutional memory.
Read moreBuilding something that needs Device Management?
Tell us the constraints and we will come back with how this platform would carry them — or say plainly if it would not.