Who Relata is for
RelataDB is one engine, but it earns its keep differently for each team. This page is the map — pick your role, see what Relata does for you that your current stack doesn't, and jump to the deep page. Every capability listed is shipped today (verified against source), with a concrete starting point.
Don't see your team? The common thread is: messy, sensitive, connected data that must be provable. If that's you, Relata fits. Relata vs others has the honest "when NOT to use it" too.
At a glance
| Team | What you replace / augment | The Relata wedge | Start here |
|---|---|---|---|
| Security / SecOps / Threat Intel | SIEM + sidecar + graph DB | Detection rules that fire at commit time, Sigma import, MITRE-tagged alerts, investigation graph, tamper-evident audit | For Security Teams |
| Finance / AML / KYC | Sanctions screening + transaction monitoring + data warehouse | Deterministic identity fusion across phone/email/IBAN/crypto, UBO + wire/crypto/hawala tracing, regulator-ready audit | For Finance & AML |
| Legal / Compliance / Audit | e-discovery + records management + audit log | Court-grade query replay (EXPLAIN_REPLAY), PROV-O provenance per fact, legal holds, WORM, GDPR DSAR, signed PDF reports | For Legal & Compliance |
| AI Agent builders | Vector DB + memory tool + graph + governance glue | 10 cognitive memory verbs, MCP tools, governed RAG, framework adapters, A2A, multimodal embedding | For AI Agent Builders |
| Data / Analytics / Big Data | Polyglot stack (Postgres + Neo4j + Elastic + Qdrant + Iceberg) | One query plane: relational + graph + vector + FTS + temporal, open Parquet/Arrow interchange, gds.* portability | Hybrid Search · Graph Analytics |
| Investigators / Analysts | Link analysis tool + spreadsheet + email | Self-forming identity graph, PATHS_BETWEEN, bi-temporal "what did we know when", governed sharing | LEA Investigation Graph |
What every team gets (the common core)
Regardless of role, four things are built in — not bolted on:
- Identity resolution — phone / email / IBAN / IMEI / MMSI / VIN / crypto address… standardized deterministically (76 canonical types), and any two records sharing one auto-link into the graph.
- Bi-temporal history — every row carries
valid_from/to(when it was true) +system_from/to(when Relata learned it). "What did we know on Tuesday?" is oneAS OFquery. - Provenance on every fact — PROV-O lineage + a tamper-evident audit hash chain. Every belief is traceable to its source.
- Cell-level governance — Cedar-inspired ABAC, PURPOSE tracking, org isolation, GDPR Art. 17 erasure.
Plus your existing tools work unchanged: 13 wire protocols (MongoDB / Postgres+pgvector / Redis / Neo4j / ClickHouse / S3 / Bolt / Flight / HTTP / gRPC / MCP / SPARQL) from one binary. See Compatibility & Doors.
Pick a starting point
- "I want to try it in 60 seconds with my existing client." → Compatibility & Doors
- "Show me a worked example in my industry." → Use cases (AML, LEA, telecom, maritime, cyber, OSINT, RAG)
- "I build AI agents." → For AI Agent Builders · AI in RelataDB
- "I run production." → Deployment · Deploying Protocol Doors
See also
- Relata vs others — honest comparison, including when NOT to use Relata
- How it works — the conceptual mental model
- Limits & Caveats — what honestly ships vs. roadmap