Product
The reinsurance operating system starts with the record.
ReRao connects submissions, agents, reviewers, market movement, and audit evidence into one source-grounded workflow layer.
Operating record
Product proof surfaceBroker submissions stay visible from intake to audit.
Animated queues show how files become events, agent work becomes evidence, and human decisions stay reviewable.
OS event bus
Broker submission packet
Input
Source artifacts
source data enters the workflow
Output
Evidence bundle
reviewable state exits the workflow
Submission received
Source and state visibleFour planes. One decision record.
The product story is organized around how work moves through ReRao, not around isolated feature cards.
Intake plane
Broker emails, files, portals, and APIs become classified work items with source evidence and clear handoff state.
Agent plane
Specialized agents extract, validate, assess, compare, reconcile, and draft without losing the review record.
Event plane
Submission, quote, bordereaux, decision, and agent events feed projectors and dashboards.
Evidence plane
Agent outputs, human overrides, and field provenance stay reviewable from intake to export.
5 shipped agents, 12 explicitly non-shipped.
Agent maturity is explicit. The catalog uses shipped, tuning, preview, and development labels rather than presenting every agent as production-ready.
Agentic workflow layer
ReRao starts where the work starts: a source-grounded command system for broker intake, extraction, human review, placement handoffs, quote-slip authority, and audit evidence in one chain.
apps/api/app/agents/
Operating record
Submissions, documents, quotes, deal-room activity, and audit evidence stay stitched to one operational timeline.
broker and quote-slip contexts
Sovereign control
Cloud and controlled-environment deployment patterns support sensitive reinsurance evaluations.
docker-compose.sovereign.yml
Integration surface
OpenAPI, webhooks, event schemas, and enterprise connectors slot into existing systems without breaking the record.
OpenAPI + webhook routers
Workflow reel
Workflow state is designed to be observable.
The reel shows the broker submission operating system in motion: unified file intake, structured extraction with citation, human-in-the-loop exception routing, quote handoff, and a permanent decision log.
Submission received
Broker intake
Inbound emails, slips, schedules, and bordereaux collapse into one review-ready submission queue.
source
Broker team
evidence
source files preserved
outcome
Submission queue created
Submission received
source files preserved
Submission queue created
Inspect intake packetEvery public proof point carries a maturity marker.
This status model is used across product, integration, security, and sovereign pages.
Put a real broker packet on the command surface.
Bring a real submission packet into a scoped design-partner evaluation for broker intake, placement handoffs, operations, or sovereign deployment.
Evaluation requested
Review-ready