Skip to content

Claims OS

Where is every claim stuck?

Stage, next hearing, panel advocate, exposure vs reserve — risk-colored, per insurer, on one board.

Request a pilotSee the platform
● DPDPA-aligned● CERT-In● Per-insurer isolation
NRD Claims OS — risk-ranked exposure board

A live answer to 'where is my claim stuck?'

Every open claim, ranked by risk: under-reserved files, hearings inside seven days, gaps the claimant can exploit. Click any claim for its full file — timeline, documents, evidence, hearings and exposure.

NRD per-claim file — exposure vs reserve, evidence and hearings

Ask your book a question

"Repudiated head-injury claims over ₹20 lakh with a hearing in 30 days." Natural-language portfolio query returns the exact slice — then export a board-ready exposure PDF.

Built for a regulated buyer

India-resident · audit-logged · isolated

Data stays in India

All claimant data processed and stored in ap-south-1 (Mumbai). Consent manager, retention TTLs, 72-hour breach workflow.

DPDPA 2023

CERT-In aligned

180-day log retention, 6-hour incident reporting, NTP-synced clocks, continuous monitoring.

CERT-In 2022

Encrypted per-tenant

AES-256 at rest via customer-managed KMS keys. Immutable audit archive on Object-Lock (WORM).

KMS · WORM

Hard tenant isolation

Your claim file never touches another insurer's tenant. Lanes stay separate — enforced, not promised.

per-insurer

Chain of custody

Every retrieved document carries a tamper-evident, timestamped, court-ready certificate.

BSA S.63

Run Claims OS on a slice of your book.

Request a pilot