Open insurance standards

Built on open standards, authored for each market.

Trisilva carries the open insurance standard OPIN forward, authors the market profile each market needs, and keeps both open. The insurance backbone built on top is built to those standards from the start.

Tier 3InsureFlow
The Trisilva platform
Extends both
Tier 2Market profile
Trisilva-authored, kept open
Vietnam first
Tier 1OPIN
The open insurance standard
Carried forward

Three tiers, each strictly extending the one beneath it

The stack

Three tiers, each extending the one beneath it.

Nothing in an upper tier redefines the tier below. The foundation is an open standard we carry forward and publish, rather than one we merely consume. What we author on top of it, we keep open too.

InsureFlow
The Trisilva insurance-domain platform: multi-region operating topology, an anti-corruption adapter that maps the shared standard shapes onto each insurer's own private API, a multi-tenant identity catalogue, an audit log, and a Document Service.Tier 3 · extends the two tiers below and inherits every gap they close
Adapter patternIdentity catalogueAudit logDocument Service
Market profile
What one national market requires that a standard cannot decide for everyone: statutory claim-handling timeframes, where data may be held, the identity documents a person is recognised by, currency and address form. Vietnam is the first profile and it is deliberately thin, because anything another market would also need belongs in the tier below instead. A profile never redefines the standard underneath it.Tier 2 · Trisilva-authored, published open
Vietnam firstStatutory timeframesResidencyIdentity documents
OPIN
The Open Insurance standard: a shared vocabulary of insurance entities, enumerations and structural patterns, and the API design over it. The Open Insurance Initiative created it and stopped revising it in 2022. Trisilva carries it forward and publishes it open under MPL 2.0, crediting the initiative as its origin. Everything every market shares sits here, including how a caller signs in, how errors are reported, how long lists are paged, how a repeated request is stopped from applying twice, and the endpoints for a record's lifecycle. What was inherited is kept unmodified alongside, so a reader can tell it apart from what changed.Tier 1 · carried forward, published open
EntitiesEnumerationsAuthError modelIdempotencyLifecycle endpoints

OPIN carried forward, the market profile authored, both kept open, InsureFlow extending them

Why open standards

Three things an open foundation does for your operation.

Your team can check each one for itself.

Portable by design

01

Your data lives in an open, documented model, so the schema your operation is modernised onto is one you can read, publish and keep. The standard is portable by design, and so is every product built on top of it, in every market.

Faster integration

02

Carriers, channels, and partners that speak the same open vocabulary connect to each other without a bespoke translation for every pair. One adapter pattern against one documented standard replaces a fresh integration project per counterparty.

Regulator alignment

03

Open insurance standards give a supervisor a documented, inspectable data model to reason about. Building on them, with a market profile written for the local regulatory reality, makes conformance built into the platform, rather than a report assembled after the fact.

Where we sit

We author the market profile for each market, and we keep it open.

We carry the baseline forward

OPIN is the open insurance standard. The Open Insurance Initiative created it and stopped revising it in 2022, which left twenty structural defects in it with no route to a fix. Trisilva now carries the standard forward and publishes it open under MPL 2.0, crediting the initiative as its origin, so a defect gets fixed at source rather than patched privately by every implementer.

We author the market profile

An open baseline written once cannot cover the operational and regulatory reality of every market. Each market Trisilva enters gets a market profile we author, closing the gaps that would otherwise stop the standard being runnable there. Vietnam is the first.

We keep the profile open

The market profile is published with a public, versioned reference anyone can read, not held as proprietary Trisilva IP. The Vietnam profile is out in the open, so you can check rather than take our word for it. InsureFlow is where our own extensions live, one tier above.

Read the white paper: OPIN v1.5.0-draft, Vietnam profile v0.2

Vietnam is the first market profile. Others follow as Trisilva enters each market, authored the same way and kept open the same way.

Build on a foundation that stays open.

The standard is public, the market profile is open, and the platform is ours to run for you. Start wherever you like.

Singapore · Vietnam · Indonesia · Philippines