Writing from the team building the platform: open standards, audit-clean operations, and the mechanics of running insurance on modern infrastructure.
The standard is at v1.5.0-draft and Vietnam's profile sits on top of it at v0.2. What the standard settles, where it is still thin, and what an open licence does and does not protect an insurer from.
Read the white paper →
Vietnam's new personal data framework put a clock on every claim. The harder problem is that anonymising a photograph destroys the signal an insurtech vendor needs.
Insurers across Asia connect to each partner one relationship at a time. Why an open insurance standard, not a vendor's model, is what carriers should accept.
One motor claim from first notice to settlement, with the nine service levels that decide who owes the next action and by when. Plus a plain statement of which parts run today and which are still architecture.
How an embedded policy is issued inside a transaction, allocated to an insurer behind it, and reconciled afterwards across four regulators. The design of the engine, not a count of deployments.
Separation between insurers is a property of a design. Proving it to a regulator is a record. What each one requires, where data residency fits, and the read-side question a write-side audit trail does not answer.
A test for AI-first that a buyer can actually apply, what it rules out, and an honest assessment of our own product.
What an outcome has to contain before a fee can attach to it: the edge cases, the calendars, the attribution problem, and why we have not signed one of these yet.
Whose vocabulary wins at the boundary decides what every later integration costs. What the translation layer buys, what it costs every month afterwards, and the question that tells you whether a platform really holds the line.
New writing lands here as it is published. Filter by type to read only what you came for.
The longer-form pieces that set out how the platform is built and how it is run.
The standard is at v1.5.0-draft and Vietnam's profile sits on top of it at v0.2. What the standard settles, where it is still thin, and what an open licence does and does not protect an insurer from.
Read the white paper →Separation between insurers is a property of a design. Proving it to a regulator is a record. What each one requires, where data residency fits, and the read-side question a write-side audit trail does not answer.
Read the white paper →What an outcome has to contain before a fee can attach to it: the edge cases, the calendars, the attribution problem, and why we have not signed one of these yet.
Read the white paper →Subscribe, and the next paper reaches you the day it is published.
