Use cases#

Problem-first walkthroughs with real SQL and SDK code — one per GA vertical. Each page states the problem, the RelataDB shape that solves it, and an honest account of what works today.

Who it's for#

• Who Relata is for — by role: platform engineers, security/finance/legal teams, and AI-agent builders
• From 4 databases to 1 — collapsing a polyglot stack into one governed engine
• For Security Teams — SOC co-pilot with real memory and audit
• For Finance & AML — funds-flow, KYC, and fraud graphs
• For Legal & Compliance — court-admissible, replayable records
• For AI Agent Builders — persistent, governed agent memory

Vertical playbooks#

• AML — Sanctions Screening — screen a counterparty and trace beneficial ownership in one governed query
• LEA — Investigation Graph — link-analysis case file with provenance on every edge
• Telecom — CDR Co-location — turn raw call-detail records into a queryable subscriber graph
• Maritime — Dark-Fleet Detection — AIS gaps, transhipment, and ownership fusion
• Cyber — Sigma Detection — hunt with Sigma rules directly over governed telemetry
• OSINT — Identity Fusion — resolve a subject's full footprint from one identifier
• App Dev — Governed RAG — retrieval that respects the same ACL as a direct query

See also: Concepts for the model behind each workload and Comparisons for how RelataDB stacks up against alternatives.