Abstract global reinsurance market atlas with cyan route arcs.
Agentic AI-native reinsurance OS

Navigate risk. Coordinate capital. Operate with certainty.

ReRao turns reinsurance submissions, agents, reviewers, market handoffs, and audit evidence into one source-grounded operating record.

Market atlas

Operating record in motion

Evidence linked

London

market placement

Broker and market handoffs stay tied to one record.

Zurich

capital view

Portfolio and treaty context remain reviewable.

Bermuda

risk capital

Submission, quote, and authority context travel together.

Singapore

regional operations

Operations and audit evidence are export-ready by design.

Source-grounded

Documents, fields, and decisions stay cited.

Market-aware

Placement movement stays tied to one record.

Governed

Authority and audit state remain visible.

The record moves across every operating lane.

ReRao starts at broker intake, then carries source context through evaluation, placement, operations, and audit review.

Intake

Capture submissions without losing source context.

Broker emails, slips, schedules, and bordereaux enter one operating record with provenance visible from the first review.

Actor

Broker teams

Proof

Broker intake target workflow

intake.record.updated

source context preserved

Submission command center

Broker submission command system

Command proof
Design-partner command reel. No customer data, production identifiers, or production underwriting outcomes are shown here; the reel uses sanitized submission content to show intake, cited extraction, exception routing, human authority, and a permanent audit trail.

ReRao broker workflow: an inbound broker email and supporting treaty files are grouped into a submission packet, structured extraction surfaces cedant, treaty, limit, TIV, exposure, and exception fields, a human review gate accepts or rejects facts, and evidence remains attached to the audit record.

Proof reads like infrastructure, not a claim sheet.

Every public capability keeps its maturity, source, and review boundary visible for buyers, security teams, and investors.

Source-tracing inspection

source cited
authority visible
audit exportable
Repo-backed

Source-grounded work

Every surfaced field points back to the document, schedule, or event that produced it.

Extraction confidence and broker review services

Repo-backed

Human authority

Review gates keep acceptance, override rationale, and authority visible before downstream handoff.

Broker review completion and slip readiness endpoints

Preview

Sovereign posture

Sensitive evaluations can be scoped against cloud, controlled-environment, and data-residency constraints.

docker-compose.sovereign.yml

Preview

Open integration surface

API contracts, signed webhooks, and core-system targets are labeled by maturity instead of implication.

OpenAPI and webhook routers

One market file, different questions.

ReRao keeps each persona inside the same evidence model instead of forcing every team to rebuild context.

Turn broker submissions into source-grounded review packets.

Broker teams get a clean intake desk, source-linked reviewed facts, exception/NIGO tracking, quote-slip and MRC draft readiness, approval/export/send gates, and audit handoffs that stay tied to the evidence record.

Classify inbound files
Extract slip and schedule fields with source links
Resolve exceptions and complete human review
Prepare quote-slip/MRC draft readiness
Approve, export, send, and package audit evidence

Design-partner workflow example. Audit-ready evidence only; no customer outcome or automated authority implied.

Maturity labels stay visible.

Integration and security claims keep repo-backed, preview, roadmap, and audit status separate.

Repo-backed

Clerk SSO

Identity

Organization-scoped auth with SAML/OIDC support through Clerk.

Repo-backed

Postgres RLS

Data

Tenant isolation enforced at the database layer.

Preview

Email ingestion

Intake

Inbound email stays in design-partner framing until automatic submission creation is verified end to end.

Repo-backed

Signed webhooks

Developers

Outbound events are framed as an evaluation integration surface with signature and delivery semantics.

Repo-backed

Row-level isolation

Tenant access is enforced at the database boundary, not only in application filters.

Repo-backed

Audit evidence

Per-submission evidence bundles keep agent and human decisions reviewable.

Design-partner review

Bring a real reinsurance workflow into the atlas.

Start with a scoped evaluation across broker intake, placement handoffs, operations, audit evidence, or deployment constraints.

Evaluation requested

Review-ready
Review pathBroker intake through the review packet
Evidence trailSource links, exceptions, and audit context
Evaluation scopeEvaluation language only, no live outcome claims