Skip to main content
AVM-WR-021/02RegisterIssued 2026-07-25

The robot works without the cloud. Here is what that actually means.

Where we draw the line between the robot’s own job and the platform’s job, and what that costs us.

Designed in Britain, answerable in Britain.

Engineering

The robot’s core runs on the robot. If your broadband dies tonight, it still does its job.

Underneath that sentence is a line we had to draw somewhere. On the robot’s side: navigation, patrol, monitoring, fall detection, anomaly detection and the safety responses. On the platform’s side: live video to your phone, alerts reaching you, fleet dashboards, and updates.

The line is drawn so that nothing safety-related sits on the far side of a broadband connection. A robot that stops watching for a fall because a router rebooted has failed at the one moment it was bought for.

That choice costs us. On-device work needs capable hardware, which sets a floor under the price. Behaviour changes have to be reconciled when a robot comes back online rather than simply read from a server. And we carry the awkward duty of telling you which features genuinely pause when the link drops — live video does, because live video is the link.

What does not pause is the job. Alerts queue and send the moment the connection returns.