Robotics & autonomous systems · AIMO security-robot fleet

The reserve layer for a fleet of autonomous robots.

AIMO runs 100 security-patrol robots across Hong Kong commercial properties. YAS reads their telemetry; YAS Assurance sits on top of Zurich's standard cover as the tail-risk layer — built for eight failure modes a normal policy was never written for.

100
robots in the pilot
8
tail-risk categories
24/7
telemetry stream
Reserve
backed, not pooled premiums
Tail-risk layer above Zurich's Humanoid Safe Deployment Program
The gap

A fleet of autonomous robots fails differently from a single machine.

Standard insurance was built for mechanical failure on one unit. But one bad firmware push can take down an entire fleet at once; 'the robot chose a harmful path' is disputed territory no policy was written for; and downtime, recalls and regulatory shutdowns can run far past a standard policy's caps and waiting periods.

The approach

A reserve-backed pool, priced on what each robot is actually doing.

YAS Assurance is a protection pool, not a policy. Each robot streams telemetry — patrol hours, navigation faults, collisions, sensor health, software version — straight to YAS. Exposure is metered against contracted bands, risk is scored for pricing and live operations, and a defined set of tail-risk events settles from a dedicated, verifiable reserve. It layers on top of Zurich's Humanoid Safe Deployment Program.

Image display
How it works

01

Stream robot telemetry

Each AIMO unit pushes operational data directly to YAS — no central platform in between.
02

Meter exposure & score risk

Actual patrol hours and missions are metered against contracted bands; baseline score prices, live score runs ops.
03

Cover eight tail-risk events

The pool covers the fleet-wide, autonomous and regulatory failures a standard policy excludes or caps.
04

Settle from reserve

Defined ratios, caps and waiting periods — with telemetry-driven alerts to intervene before a loss.
In detail

Eight failure modes a standard policy won't touch

TR-01

Correlated fleet failure

One root cause — a bad firmware push, a shared defect — takes down many robots at once.
TR-02

Autonomous navigation failure

The robot's own decision-making causes harm despite working sensors.
TR-03

Cyber-physical incident

A breach turns into physical damage, disruption or data exfiltration.
TR-04

Extended downtime

Disruption runs past the standard policy's business-interruption cap.
TR-05

Excess liability

A claim exceeds the per-occurrence or aggregate limit.
TR-06

Fleet recall & remediation

A recall or regulatory order forces a fleet-wide retrofit or stand-down.
TR-07

Regulatory shutdown

An authority suspends operations pending a safety review.
TR-08

Surveillance & data liability

Privacy or facial-recognition errors create liability standard policies exclude.
Outcome

Coverage for the risks that actually keep a robotics deployment up at night.

Operators get fleet-wide, autonomous and regulatory protection that standard cover leaves on the table — priced on real usage, backed by reserves they can verify, and paired with interventions that head off losses before they happen.

Tail-risk
the eight events Zurich's policy can't cover
Telemetry
priced on real usage, not estimates
Verifiable
dedicated, auditable reserves