Home / Capabilities / Device platforms
The system that turns a shipment of units into a fleet you can provision, watch, update and bill for — without a spreadsheet of serial numbers.
The first hundred devices can be managed by hand. The first ten thousand cannot. Somewhere between those numbers a product needs a real platform: identity for every unit, a way to see which firmware each is running, a safe way to move them all forward, and access rules that let a distributor see their own estate and nobody else's.
We build that platform as part of the product rather than as an afterthought, sized to what you are actually shipping. A fleet of two thousand controllers does not need the architecture of a global consumer service, and paying for one is a common and expensive mistake.
Services
Sizing the system to your fleet, your data rates and your commercial model, then writing it down so the decisions survive staff changes.
The day‑two features that support teams live in: find a unit, see its history, reproduce a fault, push a fix to a controlled subset first.
Connecting the platform to the systems your business already runs on, and giving your customers a documented way to build on it.
Software that is watched, patched and improved after launch, with agreed response times rather than best effort.
Questions we get asked
Yes. We build for containerised deployment, so the same system runs on a public cloud, in your data centre, or in a customer's environment where data cannot leave the site.
We migrate fleets. Devices are moved in controlled batches with a fallback at each step, so a migration never depends on every unit behaving on the same night.
By deciding retention and aggregation policy at design time. Most cost surprises come from storing raw telemetry forever because nobody chose what to keep.
That is usually the goal. We work in your repositories with your conventions, review your team's pull requests, and hand over documentation written for engineers rather than for procurement.
Tell us the fleet size, the data you need and who has to see it. We will propose an architecture sized to that, not to a brochure.