Reinsurance Technology

Reinsurance clause documentation by graphs.

RI-TOOL transforms complex reinsurance clause language into formal, executable DAG graphs — eliminating ambiguity across your entire organization.

Built for reinsurance professionals — ceding companies, reinsurers, brokers, actuarial consultants, run-off specialists


How does it work?

Each tenant is an autonomous workspace with its own specific settings, clause library, graphs, contracts and user profiles. A single organisation can run multiple tenants.

🏢

Ceding company

Your portfolio, segmented by placement channel.
One tenant per direct placement. One per broker channel — AON, Guy Carpenter, others. One for your acceptance book if you write it. Each workspace carries its own clause library, validated graphs, and contract instances. Your Senior validates for that channel. Your Actuary formalises for that book.
🌐

Reinsurer

One global book, or one workspace per geography.
Structure your tenant architecture around your underwriting organisation — by territory, by line of business, or by treaty portfolio. Every clause formalised in one region becomes a seed for the next. No duplication. No reconciliation across spreadsheets.
🤝

Broker

A dedicated workspace for each placement relationship.
Run a tenant for a cedant group. Run another for a reinsurer panel — whether placing direct or working through a market intermediary. Structure clause libraries that reflect the wording conventions of each relationship. Share formalised clause graphs with all parties in the placement chain, without sharing the workspace itself.
📐

Consulting & Actuarial

One tenant per client. Portable, auditable, yours.
Each client engagement gets its own isolated workspace. Clause graphs built for one client stay strictly within that tenant. When the engagement closes, the workspace is a complete, auditable record of every formalised clause — ready for handover or archive.
📦

Run-off specialists

One tenant per mandate. Formalise the inherited book.
Run-off portfolios depend on understanding clause language written years or decades ago. Each mandate gets its own workspace — encode legacy clauses into DAG graphs, make implicit dependencies explicit, make inherited contracts navigable. When the mandate transfers, the tenant transfers with it.
🖥️

RI software vendors

Embed structured clause formalisation in your platform.
Your clients already manage reinsurance data in your system. RI-TOOL adds the layer they are missing — structured, DAG-formalised clause libraries that connect underwriting language to actuarial models. One tenant per client in your portfolio. White-label ready, API-accessible, fully isolated per tenant.
⚖️

Claims adjustors

One tenant per mandate. The clause is already there.
When a loss event occurs, the clause graph was built at underwriting time. Every condition, every dependency, every threshold — already formalised. A dedicated tenant per mandate gives your adjustors an exact, structured view of what was agreed. Not what someone remembers.

How a tenant works

Graphs

Using our DAG editor you can build Actuary graphs linked to clauses. One clause, multiple possible graphs. Additionally, you can create Risk model and RI Towers graphs. And link them together.

Technical account templates

The SOA Senior defines technical account templates as DAG graphs. FORMULA-type nodes connect directly to Manager graph nodes.

Clause/Contract instantiation

For a given contract, the Manager instantiates an Actuary graph from those available for the clause and the reinsurance contract type. Then fills the instantiated graph according to the dimension instructions defined on the graph nodes.

Everything is updated/visible in real time

Modified data is immediately available to authorised profiles. A single user can hold one or more profiles — each tenant decides. The tool adapts to your organisation.

An EAV data model (Entity – Attribute – Value)

This approach allows each tenant to formalise everything according to ITS specificities. It is notably found in the definition of graph node dimensions which contain the filling instructions at instantiation time. Each tenant thus has total freedom in formulation. An organisation occupying multiple tenants can vary the definition logic according to its needs or those of a particular mandate.

Online user guides

Each profile has its own user guide accessible from its menu. This guide explains in particular the examples provided free of charge at registration.

Standard Reinsurance Clauses

Explore the main clause types used in reinsurance treaties — formalized on RI-TOOL


Reinsurance Glossary

Key terms and definitions used in international reinsurance markets


Data protection for each tenant

A dedicated set of user accounts for each tenant

🔒
AES-256-GCM — Bank-grade encryption at rest
Every document is encrypted server-side the instant it is received. The plaintext never touches the disk. The GCM authentication tag detects any tampering at decryption time.
🗝
One key per tenant — absolute isolation
Your 256-bit key is generated with a CSPRNG, stored outside the web root with restricted permissions (0640), never transmitted over the network. Your data is unreadable without your key — even if another tenant's were exposed.
🧠
Decryption in RAM only
Preview and search decrypt documents exclusively in server memory. Plaintext is used, then discarded. No temporary cleartext file is ever left on disk. A filesystem compromise yields only encrypted blobs.
🔍
Profiled access — full audit trail
9 profiles with defined perimeters. Each actor has a precise scope and a full audit trail.

The schema shared by tenant profiles

Clause structured wording Actuary graph DAG — nodes · links · dimensions formalisation Risk Modeler site · peril · coverage exposure Program Manager tower programmes structure ref Manager contract instance + values instantiation SOA graph statement of account FORMULA Core flow Risk exposure Programme structure SOA link Instantiation CORE — CLAUSE FORMALISATION RISK optional SOA optional Clause graphs DAG — nodes · links · dimensions inter-graph Contract instance clause graph + contract values instantiation Risk graphs site · peril · coverage exposure link Statement graphs Technical accounts production FORMULA link PROGRAMME optional Tower programmes structure ref Core flow (required) Risk exposure (optional) SOA accounting (optional) Programme structure (optional)

Discover the profile guides provided per tenant


356 reinsurance terms. 14 languages.


You will be up and running quickly with the provided examples

Risk Graph Examples

Clause Graph Examples

Technical Account Graph Examples (Statement of Account - SOA)

RI TOWER & RISK MODEL EXAMPLES

Risk Building Blocks

🧱 RISK LEGO PRIMITIVES
Build any risk clause. From 6 reusable graph patterns.
Conditional floor, capped value, rate application, weighted average, LOOKUP scale, multi-input accumulator. Every reinsurance risk clause reduces to combinations of these 6 primitives. Copy, rename, assemble.
#01 Conditional Floor#02 Capped Value#03 Rate × Base#04 Weighted Average#05 LOOKUP Rate Application#06 Multi-Input Accumulator
Explore the risk building blocks →

CAT NAT Building Blocks

🌪 CAT LEGO PRIMITIVES
Build any Cat XL cover. From 5 natural catastrophe primitives.
Event aggregation, 72-hour clause (aggregate & large-claim variants), annual aggregate limit, occurrence counter — each a standalone DAG. Link via SUBGRAPH to compose full Cat XL structures.
#01 Event Aggregation#02a 72h Aggregate#02b Large Claim Filter#03 Annual Aggregate Limit#04 Occurrence Counter
Explore the Cat XL building blocks →