Source-grounded work
Every surfaced field points back to the document, schedule, or event that produced it.
Extraction confidence and broker review services

ReRao turns reinsurance submissions, agents, reviewers, market handoffs, and audit evidence into one source-grounded operating record.
Market atlas
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.
ReRao starts at broker intake, then carries source context through evaluation, placement, operations, and audit review.
Intake
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
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.
Every public capability keeps its maturity, source, and review boundary visible for buyers, security teams, and investors.
Source-tracing inspection
Every surfaced field points back to the document, schedule, or event that produced it.
Extraction confidence and broker review services
Review gates keep acceptance, override rationale, and authority visible before downstream handoff.
Broker review completion and slip readiness endpoints
Sensitive evaluations can be scoped against cloud, controlled-environment, and data-residency constraints.
docker-compose.sovereign.yml
API contracts, signed webhooks, and core-system targets are labeled by maturity instead of implication.
OpenAPI and webhook routers
ReRao keeps each persona inside the same evidence model instead of forcing every team to rebuild context.
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.
Design-partner workflow example. Audit-ready evidence only; no customer outcome or automated authority implied.
Integration and security claims keep repo-backed, preview, roadmap, and audit status separate.
Identity
Organization-scoped auth with SAML/OIDC support through Clerk.
Data
Tenant isolation enforced at the database layer.
Intake
Inbound email stays in design-partner framing until automatic submission creation is verified end to end.
Developers
Outbound events are framed as an evaluation integration surface with signature and delivery semantics.
Tenant access is enforced at the database boundary, not only in application filters.
Per-submission evidence bundles keep agent and human decisions reviewable.
Start with a scoped evaluation across broker intake, placement handoffs, operations, audit evidence, or deployment constraints.
Evaluation requested
Review-ready