The YAS Platform

Operating System for
Robotic Risk.

Insurance for deployment. Assurance for autonomy.

Rail 1 delivers practical insurance products deployable today — physical damage, liability, operator cover. Rail 2 is a YAS-led assurance infrastructure built in parallel — telemetry-led triggers, pooled reserve logic, and faster response workflows for connected autonomous fleets.

Two Protection Rails

How YAS Works

Rail 1
YAS Insurance — Day 1

Practical insurance products deployable now. Physical damage, liability, and operator cover — structured through insurer underwriting for robotics, EV fleets, and mobility operators across Hong Kong, Malaysia, and Vietnam.

No telemetry required · Available today

Physical damage & mechanical breakdown
Operator personal accident
Third-party property & bodily injury
Fleet program and pilot structures
See Rail 1 Flow
Rail 2
YAS Assurance — Pool Rail

A YAS-led assurance structure built in parallel — pool reserve logic, telemetry-led triggers, and faster response workflows for connected autonomous fleets. Requires continuous telemetry API integration.

Requires telemetry integration · Building now

Pool-backed reserve architecture
Fiat and crypto-supported funding paths
Telemetry-led trigger and response playbooks
Evidence-backed faster payout workflows
See Rail 2 Flow

Rail 1 · YAS Insurance

Insurance Day 1: How It Works

From fleet onboarding to active coverage — a structured process that gets operators protected without waiting for the autonomous future.

Day 0

Fleet Intake

Operator submits fleet type, geography, use case, and unit count. YAS maps to appropriate product structure.

Day 0–1

Risk Assessment

Coverage class, operator history, deployment environment, and asset specs evaluated against underwriting criteria.

Day 1

Policy Binding

Premium structured. Policy certificate issued. Coverage confirmed across: physical damage, liability, operator PA.

Ongoing

Active Coverage

Coverage active for the fleet. Incident reporting channel open. Claims routed to assessment workflow.

Event-driven

Claims & Renewal

Claim filed → evidence submitted → assessment → settlement. Annual renewal with updated fleet data.

What's Covered

Coverage Scope: Rail 1

Asset
  • Physical damage to the machine
  • Mechanical breakdown
  • Repair & maintenance
  • Extended warranty support
People
  • Operator personal accident
  • Employer liability
  • Buyer principal liability
  • 24/7 incident support
Third Party
  • Third-party property damage
  • Third-party bodily injury
  • Regulatory compliance
  • Public liability
Program
  • Fleet blanket structures
  • Pilot program cover
  • Custom endorsements
  • Multi-unit policies

Coverage Matrix

Rail 1 vs Rail 2 at a Glance

Rail 1 is deployable today. Rail 2 capabilities require telemetry API integration and are being built in parallel.

Rail 1 — Insurance (Available today)
Rail 2 — Assurance (Parallel build)
Not applicable
Asset Protection
Physical Damage
Mechanical Breakdown
Extended Warranty
Telemetry-Triggered Alerts
People & Operators
Operator Personal Accident
Employer Liability
Behavioral Drift Monitoring
Incident Evidence Packet
Third Party
Third-Party Property Damage
Third-Party Bodily Injury
Cyber-Physical Exposure
Near-Miss Classification
Program & Fleet
Pilot Program Structure
Fleet Blanket Cover
Fleet Protection Score
Dynamic Risk Triggers

Console Preview

Three Operating Views.

Monitoring for operators, Underwriting for insurers, Assurance for the Rail 2 pool — each with a distinct data surface and decision workflow.

Operator view
Insurer view
Assurance view
YAS Console — Fleet Dashboard
Illustrative
Fleet Groups
HK EV Taxi Fleet
831 active · 14 offline
HK Patrol Robot Fleet
21 active · 1 offline
MY Service Robot Fleet
16 active · 0 offline
Coverage Status
Rail 1 Active
845 Units Covered
Renews Apr 2026
Fleet Protection Score
87/100
+2 this week
Units Active
831/845
14 offline
Active Events
3
1 near-miss · 2 minor
Coverage Health
98.3%
831 of 845 in-bounds
Fleet Protection Score — Breakdown
Illustrative data
Operational Safety28/30
Reliability & Uptime18/20
Incident History18/20
Exposure Environment12/15
Compliance & Governance11/15
Recent Events
01:08EV-247Near-miss — pedestrian crossing sensor threshold exceededNear-miss
00:54EV-089LiDAR channel 4 calibration drift detectedMinor
00:31EV-412Route deviation logged — auto-correctedNormal
00:15ALLDaily fleet health report generated — FPS 87Info
Operator view
Selected-fleet example: coverage status, fleet score, active alerts, renewal readiness
Insurer view
Illustrative insurer context: event evidence, underwriting, and claims support
Assurance view
Illustrative assurance context: triggers, reserve logic, and response actions

Illustrative console interface — actual product in development

Rail 1 · Underwriting

Underwriting Workbench

The insurer's workbench for each fleet submission — deployment, telemetry, evidence, and coverage structure reviewed in one operating surface.

Deployment
Fleet group, geography, use case, and unit count structured at intake
Telemetry
Connectivity tier assessed: offline, partial, or live
Evidence
Asset history, deployment context, and incident record scored 0–100
Decision
Underwriting decision, pricing structure, and coverage pathway
YAS Underwriting Workbench — deployment profile, evidence strength, and decision output

Illustrative interface — product in development

Rail 1 · Operator View

Monitoring

Live fleet visibility for operators — selected fleet group, active events, telemetry status, and protection state in one operational view.

Deployment
Fleet group, unit state, and operating zone updated in real time
Telemetry
Signal health per unit — sensor uptime, connectivity tier, and last heartbeat
Evidence
Event packet completeness: sensor data, video, route trace, operator notes
Decision
Escalation routing — monitor, alert, isolate, or route for review
YAS Monitoring — live fleet coverage, FPS, and event feed

Illustrative interface — product in development

Rail 2 · Assurance Response

Assurance Control Center

The assurance operating surface for YAS assessment, pricing, reserve review, capital coordination, and payout workflow, with a human gate at each critical decision.

Deployment
Fleet group, YAS risk tier, pricing inputs, and pre-agreed trigger parameters per client
Telemetry
Live signal quality score — high / medium / low — gating automation eligibility
Evidence
Incident packet completeness: telemetry trace, confidence score, coverage match
Decision
Reserve earmark, pricing outcome, payout approval, decline with evidence record, or escalation
YAS Assurance Control Center — trigger state, evidence strength, reserve logic, and payout workflow

Illustrative interface — product in development

Rail 2 · YAS Assurance

How the assurance pool works.

A YAS-led assurance pool can run parallel to insurance using YAS assessment, pricing, reserve logic, and response triggers supported by fiat, stablecoin, and selected major-crypto capital rails.

Step 01
Ingest
Telemetry In
ROS2 · CAN/OBD-II · GPS · IMU · Sensor Health · Operator Context
Step 02
Score
FPS Update
Safety events · Reliability · Exposure · Compliance → Fleet Protection Score
Step 03
Detect
Anomaly Engine
Drift vs baseline · Sensor degradation · Environmental spike · Policy exception
Step 04
Classify
Event Tiers
Normal · Near-miss · Minor · Major · Critical → appropriate workflow routed
Step 05
Respond
Action Rail
Notify · Isolate · Reserve earmark · Evidence packet · Assisted claim workflow

Human-in-the-loop checkpoints at Classify and Respond — automation scoped to pre-agreed triggers only

Signal Inputs

  • · Telemetry and fleet operating data
  • · Asset health and maintenance state
  • · Route / environment / deployment context

Pool Logic

  • · Trigger thresholds set in advance
  • · Unit / fleet score linked to reserve logic
  • · Human-reviewed event classification before release

Capital Rails

  • · Fiat reserve accounts
  • · Crypto-supported treasury / settlement paths
  • · Configurable by market and partner structure

Response Playbook

  • · Notify and isolate where needed
  • · Build evidence packet from telemetry
  • · Support reserve / payout workflow execution
Assurance Capital Flow
Contributors
Pool capital
Treasury
Fiat / crypto rails
Reserve Layer
Held against triggers
Review Gate
Human approval
Payout Path
Operator / partner / claimant

Reserve capital is allocated against pre-agreed trigger logic, held through review, and released through the appropriate response or payout path.

Assurance Pool Dashboard
Assurance control center
Assurance Lifecycle States
Monitoring
Normal pool surveillance
Alert
Signal or threshold concern
Triggered
Pre-agreed logic activated
Under Review
Human gate in progress
Reserved
Capital earmarked
Closed
Paid / declined / reset
Assurance Modules
Telemetry Monitoring
Live fleet inputs
Score Engine
Protection score logic
Trigger Engine
Threshold execution
Reserve Logic
Pool allocation rules
Payout Workflow
Fiat / crypto release path
Audit Trail
Evidence + history

Operating Model

Two rails. Different protection needs.

Two complementary rails, fundamentally different operating models. Both are necessary — neither replaces the other.

Use Rail 1 when
  • You need coverage active before you have telemetry infrastructure
  • Your fleet is partially or not connected — offline assets still need protection
  • Your insurer or regulator requires a traditional policy certificate
  • You're running a pilot program and need quick, structured cover
Use Rail 2 when
  • Your fleet has continuous telemetry and a live data API you can expose
  • You want risk pricing that reflects actual fleet behaviour, not declared value
  • You need pre-agreed trigger logic and faster evidence-backed payout flows
  • You're building toward fully autonomous operations and need scalable pool protection
Dimension
Rail 1 — Insurance
Rail 2 — Assurance
Trigger
Incident reported
Telemetry threshold crossed
Pricing
Annual policy premium
Dynamic, score-adjusted
Coverage basis
Declared asset value
Real-time fleet exposure
Data required
Operator declaration
Continuous telemetry stream
Claims process
Evidence → adjuster → pay
Telemetry packet → faster decision
Human loop
All steps
Classification + response gates
Settlement time
Days to weeks
Target: hours (pre-agreed cases)
Suitable for
All fleets today
Connected fleets with data API

Rail 2 settlement timelines and trigger automation are subject to regulatory approval, product development milestones, and insurer capacity agreements.

Platform Capabilities

Built for the Operating Layer

Real-time Telemetry

Direct integration with robotic OS and fleet telematics for sub-second risk monitoring.

Edge Risk Scoring

On-device risk evaluation that detects behavioral drift before incidents occur.

Automated Triggers

Pre-agreed playbooks that fire the moment a threshold is crossed — human review gate maintained.

Multi-Market Ready

Configurable insurance and assurance rail designed for HK, Malaysia, and Vietnam with multi-market expansion.

Architecture

Full-Stack Protection.

From sensor to settlement — a unified infrastructure layer.

01

Ingestion Layer

ROS2, telematics APIs, OBD-II/CAN, IMU/LiDAR summaries, operator context ingested in real time.

02

Intelligence Engine

Fleet Protection Score updated continuously. Behavioral drift, sensor health, and environment signals processed by risk models.

03

Execution Rail

Pre-agreed triggers route events to: notify, isolate, reserve, or assisted claim workflow. Human review gate maintained.

Markets

Operating Markets

🇭🇰

Hong Kong

Regional commercial hub and programme headquarters

🇲🇾

Malaysia

Partner development and market distribution

🇻🇳

Vietnam

Embedded distribution and growth market

Deploy the
Protection Rail.

Ready for Rail 1 coverage today, or building toward Rail 2 integration — contact us to get started.