Two families.One underwritingengine.
Which structurecarries which risk.
| Product | Robotics | AI Risk | Digital Assets | MiCAR / CASP | Tokenized Assets | Cyber & Digital Risk |
|---|---|---|---|---|---|---|
| MACHINA-SURE | Applies | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable |
| COBO-SURE | Applies | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable |
| HUMANO-SURE | Applies | Applies | Not applicable | Not applicable | Not applicable | Not applicable |
| MICASURANCE® | Not applicable | Not applicable | Applies | Applies | Not applicable | Not applicable |
| T-SURE™ | Not applicable | Not applicable | Applies | Applies | Not applicable | Applies |
| NOVA™ | Applies | Applies | Applies | Not applicable | Applies | Applies |
Autonomous machines
Machines that move in the physical world. Risk is ordered along the two factors that actually drive it: proximity to people, and how freely the machine moves.
MACHINA-SURE
The classic robot cell sits behind a separating safeguard with no shared workspace. It is the most mature and best-understood robot class, and the loss picture is dominated by maintenance and intervention, the moments the safeguard is open. MACHINA-SURE is written against that structure rather than around it.
Built for
- Manufacturers operating robot cells
- System integrators and cell builders
- Contract manufacturers and their insurers
- Logistics and warehousing automation
What it protects
The fenced cell: the machine, the people who maintain it, and the production that depends on it.
- Core operator liability
Third-party bodily injury and property damage arising from robot operation, including maintenance and intervention where the work is evidenced.
- Machinery and hull
Own damage to the robot from collision, malfunction or internal operating failure.
- Business interruption
Loss of income and additional cost following a covered outage of the cell.
- Control takeover
Loss from manipulation or unauthorised takeover of the robot controller.
- Serial defect and recall
Recall and consequential cost for the integrator where a defect reaches a series rather than a unit.
COBO-SURE
A collaborative robot is designed for contact. The contact is intended and biomechanically limited, which makes the decisive risk factor neither the machine nor the person but the match between the documented risk assessment and the deployment that was actually built. COBO-SURE is written on that match, and covers the gap when it opens.
Built for
- Manufacturers running cobots beside people
- Integrators deploying collaborative applications
- Electronics, medical device and precision assembly
- Laboratories and cleanroom operations
What it protects
The shared workspace, where contact is designed in rather than designed out.
- Core interaction liability
Bodily injury and property damage in collaborative operation, including contact injury despite force limitation.
- Machinery and hull
Own damage to the cobot from collision or malfunction.
- Business interruption
Loss of income following a covered cobot outage.
- Control takeover
Loss from manipulation of the cobot controller.
- Compliance gap
Loss arising from a mismatch between the documented risk assessment and the deployment as built, the failure this class actually produces.
HUMANO-SURE
A free-moving humanoid shares none of the constraints the other two classes rely on. Free movement, fall and misnavigation, fall energy and an energy-dense battery create failure modes no other robot segment has. It is also the most data-scarce class, which is why HUMANO-SURE prices against an evidenced operating environment and autonomy level rather than against a category.
Built for
- Humanoid robot developers and makers
- Operators of humanoid fleets
- Logistics, service and facilities deployments
- Investors with concentrated exposure to a fleet
What it protects
The free-moving machine, and the people it moves among.
- Core liability
Bodily injury and property damage caused by the mobile robot in proximity to people.
- Machinery and hull
Own damage, including fall damage and damage to the battery.
- Business interruption
Loss of deployment of the unit and the additional cost of covering for it.
- Autonomy malfunction
Loss from misnavigation, perception failure or model error, the decision, not only the mechanism.
- Battery and fire
Loss from the energy-dense battery, including fire.
- Sensing and privacy
Loss arising from camera- and sensor-driven data capture in a space occupied by people.
Digital assets
Value that exists as a record. The insurable object is the architecture that holds it: the key material, the register, the redemption right and the regulated firm that operates them.
MICASURANCE®
MICASURANCE is built for operators inside a supervised digital asset perimeter. It aligns the insurance programme with the obligations the business is actually held to, so that the cover, the controls and the evidence presented to a supervisor describe the same firm.
Built for
- Crypto-asset service providers
- Firms in authorisation
- Exchanges operating in the EU
- Custody and safeguarding providers
What it protects
The regulated company and its provable breaches of duty, not the crypto-asset itself.
- Obligation mapping
The operating model is mapped against the obligations that generate insurable exposure, producing a defensible programme rationale.
- Safeguarding layer
Structured around segregation and custody of client assets, with the control evidence maintained continuously rather than annually.
- Governance and liability
Management and professional exposure arising from regulated activity, structured for the entity and its officers.
- Resilience and third party
ICT and dependency exposure addressed alongside continuity obligations, not as a separate purchase.
- Evidence trail
A maintained record designed to be presented, to a supervisor, a counterparty or a board, without reconstruction.
T-SURE™
T-SURE places protection inside the platform rather than beside it. Cover is offered at the point where the user already is: onboarding, custody, transfer. It is administered through infrastructure rather than paperwork.
Built for
- Exchanges and trading venues
- Custodial wallet providers
- Brokerage and payment platforms
- Digital asset neobanks
What it protects
The client’s balance on the venue and the transactions they make there, inside the venue, not the route out of it.
- Platform integration
Protection surfaced natively inside the platform’s own product flow, under the platform’s own interface.
- Programmatic eligibility
Eligibility and risk assessment resolved from platform signals rather than from forms.
- Portfolio underwriting
The platform’s population is underwritten as a portfolio, with pricing informed by observed behaviour.
- Operational reporting
Continuous reporting back to the platform on exposure, uptake and concentration.
- Response pathway
A defined incident route that runs through the platform’s own support and operations model.
NOVA™
Emerging technology risk does not respect product lines. An autonomous system failure is simultaneously a liability event, a cyber event and a technology failure. NOVA is structured as one programme across those boundaries, so that the response is not delayed by an argument about which policy answers.
Built for
- AI and robotics companies
- Autonomous systems operators
- Multi-technology groups
- Investors with concentrated technology exposure
What it protects
The company as a technology business: one programme across liability, cyber, crime, property and D&O.
- Single risk perimeter
One perimeter drawn around the technology exposure, rather than several drawn around insurance products.
- Cross-class structuring
Liability, cyber, technology and physical exposures structured together with deliberate seams.
- Continuous underwriting
The programme responds to observed change in the risk rather than waiting for renewal.
- Unified response
One incident route across all classes, coordinated from the first notification.
- Portfolio view
Aggregation and correlation managed at group level for organisations operating several technologies at once.
Capacity, limits, wordings and commercial terms are not published. They are structured per counterparty and shared directly under engagement.