Use case · Long-lifecycle fleets
Devices that stay patched for as long as they are on the wall.
When a manufacturer stops updating a model, every fleet built on it starts collecting known vulnerabilities that will never be fixed. Ours do not age out, because we maintain the operating system ourselves.
What maintained security means in practice
Critical fixes within a week
On the standard build. Two weeks where a system carries significant customization.
Major upgrades over the air
Devices that left the factory on Android 13 run Android 17 today, with no site visit.
Updates that undo themselves
Each update installs alongside the running system. If a device fails to start it, it rolls back on its own.
You approve every update
Nothing is forced onto your fleet. Patches go out when you say so.
Proof of what is running
Each device proves in hardware that it is genuine and running exactly the software you approved. Your own server can check.
Absent means absent
If you decline a component, such as unattended remote control, it is left out of your image, and attestation proves it is not there.
What your auditor will ask for
Regulated buyers buy records, not claims. Our security bulletins list what we have fixed, with dates.
On an annual support agreement we put the rest in writing: a patch SLA, a software bill of materials for each release, source escrow, a named support contact, and a defined support horizon.
Planning a fleet?
Start with a developer device to evaluate, and talk to engineering about the lifecycle you need.