available
Every field has a source
Click any term and you land on the page, schedule, or event that produced it.
Extraction service, reviewed by underwriting
ReRao Reinsurance OS
From inboxto quote-ready.
ReRao reads every broker submission, shows where each number came from, and hands your team a reviewed packet to quote from. Nothing gets retyped.
Every field cites its source
People approve, not agents
Audit trail included
How it works
What happens to a submission, step by step.
The file is read once. Every term keeps the page it came from. Exceptions go to a named person. The audit trail stays attached, and nothing is re-keyed.
SUB-2026-GOLDEN-PCAT-XOLIsla Verde Insurance Group
22 Accepted Facts1 Open NIGO
Extracted Contract Facts
Treaty Type
Property CAT Excess of Loss
Total Limit
$120,000,000 xs $20,000,000
Blended RoL
7.58% ($9,100,000 premium)
Coverage Scope
Wind, Surge & Named Storm
Governed Exception Routing
Missing 2025 Zonal Loss History
Zone 005 historical record requires underwriter sign-off prior to market release.
Audit Status
ReviewReadyPacket v1 Sealed
Immutable hash: 20260810-pcat-golden
Human Review StatusReferred to Senior Desk
Built for the whole value chain.
Intake
Nothing gets lost on the way in.
Emails, slips, schedules, and bordereaux land in one record — with the source attached from the first review.
For broker teams
Broker intake workflow (in preview)
Evaluate
Agents read the file. People make the call.
Extraction, appetite, and exception checks arrive with their sources and their confidence — and stop at a person for approval.
For underwriters and reviewers
Extraction and review services in the repo
Place
Keep every market on the same record.
Quotes, deal-room activity, and market replies stay attached to the submission — and to who approved what.
For brokers and markets
Deal-room and quote-slip screens
Govern
Hand over a file that holds up.
Overrides, outputs, and evidence export together, so audit and model risk can check the same thing your team did.
For operations and risk
Audit evidence bundle (design)
Why you can check us
Every claim shows its source.
Each claim here is labelled shipped, in preview, or planned — with the file it came from. If we cannot point to it, we do not claim it.
available
People approve, not models
Every review gate records who accepted what, when, and why — before anything moves on.
Broker review and quote-slip workflow
preview
Runs where you need it
Cloud, your own environment, or data that cannot leave the region.
Sovereign deployment configuration
preview
Connects to what you run
APIs and signed webhooks, each labelled by how ready it actually is.
Public API and webhook contracts
The controls your security team will ask about.
Isolation, access, evidence, and deployment — each shown with its actual status, not an adjective.
Row-level isolation
Tenant access is enforced at the database boundary, not only in application filters.
Audit evidence
Per-submission evidence bundles keep agent and human decisions reviewable.
SOC 2
Public copy must state audit status rather than certification completion.
Integration surface
What is actually available.
Clerk SSO
availableOrganization-scoped auth with SAML/OIDC support through Clerk.
Postgres RLS
availableTenant isolation enforced at the database layer.
Email ingestion
previewInbound email stays in design-partner framing until automatic submission creation is verified end to end.
Signed webhooks
availableOutbound events are framed as an evaluation integration surface with signature and delivery semantics.
Send us one submission. We will run it end to end.
A scoped evaluation on your file, in your environment if you need it. You keep the record and the evidence.
Evaluation path
1submission, end to end
4points where a person approves
0fields retyped