Deliver a group term insurance product for gig workers where coverage activates automatically from verified active work status on the aggregator platform, not a paper enrollment. Civil Registry, Escrow and Conditional Settlement, and Compliance Attestations tie cover to real, verified engagement so irregular, multi-platform workers are protected exactly while they work.
Turn a rigid enrollment gate into automatic, status-driven coverage that follows real work.
01.
The platform signs a verified active-work event and the contract activates coverage automatically, so a worker who goes online is protected without filling in an enrollment form.
02.
The Civil Registry module records each worker's identity and active status, so cover attaches to a verified person rather than an unverifiable self-declaration.
03.
The Escrow and Conditional Settlement module collects the micro-premium for the active period and holds it against the group cover, matching cost to actual engagement.
04.
When verified active status ends, coverage stands down cleanly, removing the manual re-enrollment a worker faces every time they return to the platform.
05.
Compliance Attestations confirm the product meets group-cover eligibility rules for each active worker, keeping an irregular, multi-platform book compliant.
06.
Two further Cerulea Studio modules let cover recognise active status across more than one aggregator, so a worker's protection is not tied to a single app.
Follow a single gig worker from going online to automatic, verified coverage and a clean stand-down.
07:45:10
[SYS] Receiving active-status signal for worker GW_5521...
07:45:10
[CMD] markActive { worker: "GW_5521", platform: "AGG_0x14" }
07:45:11
[AUTH] Verifying platform signature and worker identity...
07:45:11
[OK] Active status AS_66201 anchored at block 5501120.
Cerulea decomposes usage-based gig cover into modular contracts. Each layer verifies status, attests eligibility, activates coverage, and stands it down without manual enrollment.
Usage-based coverage is a horizontal capability. Here is how different actors in the gig economy put the shared ledger to work.
Offer embedded protection that switches on with verified active work, giving riders and drivers cover without an enrollment step and without the platform carrying manual administration.
Key Asset Types
Price and underwrite an irregular, multi-platform book against verified engagement data, matching premium to real exposure instead of guessing at intermittent workforces.
Key Asset Types
Are covered automatically while working across one or more platforms, with no repeated sign-up and a clean lapse when they stop, so protection follows the actual work.
Key Asset Types
Whether you are bridging an insurer's group product system or capturing active status from an aggregator's dispatch platform, Cerulea routes both into one shared coverage ledger.
For insurers on legacy group product systems. Existing cover and premium records are translated into signed on-chain coverage events through the API gateway automatically.
Legacy Product System
Insurer Group Platform
Cerulea API Gateway
Event Hashing & Signing
Cerulea Private Chain
Shared Coverage Ledger
For platforms signalling active status from dispatch. A connector signs each active-work event from a platform wallet and routes it directly to the coverage ledger.
Aggregator Dispatch
Platform Backend
Consortium Validators
Status Consensus
Cerulea Ledger
Shared Coverage Record
Building a usage-based cover network with verified status triggers, per-session premium escrow, and automatic lapse from scratch requires specialised engineers and long platform integration cycles. Calculate your exact deployment speed using Cerulea.
Traditional Deployment
Solidity Coding & Audits
~ 11 Months
Visual Compilation
WASM Logical Artifacts
~ 4 Weeks
The legacy timeline reflects gig-platform integration benchmarks. Connecting an insurer's product system to aggregator dispatch, coding status-triggered activation, and shipping per-session premium logic for an average network takes a baseline of 6 months. Building the same architecture on Cerulea takes a baseline of 2 weeks, because Cerulea Studio visually translates your status and coverage rules into pre-audited WebAssembly binaries and provisions the shared coverage ledger instantly.