Can you add OTA updates to devices we already shipped?

Usually, yes — if the device has a spare partition or enough storage for an A/B scheme, and a way to reach the network. We assess the bootloader and partition layout first; where the current hardware can’t support safe updates, we tell you plainly rather than ship a risky one.

How do you stop a bad update from bricking the fleet?

Every update is atomic and reversible: the new image is written to an inactive A/B partition, verified, and only booted if it passes a health check — otherwise the device falls back to the last good image on its own. Rollouts also go to a canary group first, so a bad build is caught before it reaches everyone.

Do we have to use a particular OTA platform?

No. We build on Mender, balena, AWS IoT Device Management or Eclipse hawkBit when a managed platform fits, and on an open stack (SWUpdate or RAUC with your own update server) when you need to own it. The choice follows your hardware and constraints, not a vendor.

Can you manage devices we didn’t build?

Yes. We enrol existing fleets into one registry, normalise their status and versions, and give you a single place to provision, update and monitor mixed hardware.

All services

Fleet & OTA management

Fix every device in the field from your desk.

Provision, update and watch your whole fleet — without a truck roll.

A device in a customer’s hands shouldn’t mean a bug you can never fix. We build the system that ships firmware and software to your whole fleet over the air — staged, reversible and watched — so you can patch a flaw, add a feature or recover a device remotely, without sending anyone out and without bricking the ones already working.

Let’s manage Open Kanban

A map of a deployed device fleet with per-device update status

01 / What it gives you

Every device, under your control.

Devices that set themselves up

Zero-touch provisioning — a unit powers on, claims its identity and joins the fleet on its own, so nobody configures devices by hand on the line.

Ship updates over the air

Push firmware and software to the whole fleet remotely — the same way you release to a web app, to devices you’ll never physically touch again.

Staged, never all at once

Roll out to a canary group first, watch it, then widen — and if something looks wrong, pause or roll back before it reaches everyone.

Know the state of the fleet

Live health, connectivity and firmware version for every device, with remote diagnostics — so you find the problem before the support call does.

02 / Stack

The technology we build with.

Industry-standard, boring in the good way: tools with a future, that the next engineer will know too.

OTA & device management

Mender
Robust A/B firmware OTA with rollback
balena
Container-based fleet deployment
AWS IoT Device Management
Managed device registry and jobs at scale
Eclipse hawkBit
Open update server for rollout control

Delivery & on-device

MQTT
Lightweight command and status channel
Delta updates
Delta updates to cut bandwidth and time
A/B partitions
A/B partitions for safe, atomic swaps
SWUpdate & RAUC
SWUpdate and RAUC for embedded Linux

Monitoring & dashboards

Grafana
Fleet health and rollout dashboards
Prometheus
Per-device metrics and version tracking
Alerting & webhooks
Alerts on failed updates and offline units
OpenTelemetry
OpenTelemetry traces from device to cloud

03 / Approach

How we build things that last.

Staged rollouts by default

Every release goes to a small canary group first and widens only once it’s proven — a bad build never reaches the whole fleet at once.

A rollback that actually works

A/B partitions and health checks mean a failed update falls back to the last good image on its own — a device is never left bricked.

Zero-touch from the factory

Devices provision and enrol themselves on first boot, so scaling the fleet never means scaling the manual setup work behind it.

Nothing updates blind

Each rollout is watched end to end — who got it, who succeeded, who fell back — so you act on what the fleet is actually doing.

04 / Standards

Best practices we don’t skip.

We adhere to industry standards and proven methods on every project — they are what makes the estimate hold.

Use A/B partitions so every update is atomic and reversible
Roll out to a canary group before the whole fleet
Roll back automatically when a device fails its health check
Sign and verify every image so only trusted firmware runs
Ship delta updates to save bandwidth on metered links
Make updates resumable so a dropped connection never bricks a device
Track firmware version and health for every device in the fleet
Alert on failed updates and devices that drop offline

05 / Infrastructure

Where it runs, and how it stays up.

Zero-touch provisioning and a device registry for the whole fleet
Signed, delta OTA delivery with A/B partitions and resume
Staged and canary rollouts with automatic rollback on failure
Fleet dashboards, remote diagnostics and update alerting

Start

Ready to reach every device in the field?

Tell us about your fleet and how you ship to it today. A senior engineer — not a sales rep — writes back.

Let’s manage IoT security

Fix every device in the field from your desk.

Provision, update and watch your whole fleet — without a truck roll.