Use cases

Relata DB 3.0
These pages describe Relata DB 3.0: one machine, one tenant, HTTP/JSON under /v1/, no protocol doors. Nothing here is a qualification of a workload. Read 3.0 evidence status.

Each page uses only surfaces that exist in the 3.0 open build: the HTTP/OpenAPI API, the Python, TypeScript and Go SDKs, MCP, read-only GraphQL, Arrow over POST /v1/query/arrow, native rules at /v1/rules, the files API, the change feed, OTLP ingest, the memory door, retrieval evidence, erasure and legal hold, and backup with offline restore. Every page ends with an "Exercised by" section naming the scenario that ran against a real node and the defects it recorded.

Use caseWhat it showsPage
SIEM / SOCContract-gated ingest, window rules, alert triage, hash-verifiable evidence, pivot and graph huntSIEM / SOC
Financial crimeCompeting claims about a customer, review and correction, legal hold, bi-temporal replayFinancial crime
Blockchain threat intelligenceWhat Relata stores and links around transfer data; detection heuristics live outside the databaseBlockchain threat intel
Physical securityEvidence footage through the files API and the OpenETL work-item handoffVideo evidence
Governed RAG and memoryRetrieval with citations, replay and version pinning; agent memory with masking and purposeGoverned RAG and memory
SaaS backendsA single-tenant application backend, and what needs EnterpriseSaaS backends
ComplianceErasure with receipts, legal hold precedence, backup and offline restoreErasure, legal hold and backup

The write contract all of them share

POST /v1/query is read-only. Writes go through the ingest routes, PUT /v1/objects or POST /v1/commit. A queued write returns accepted, not yet durable: the row will be visible after the ingest task completes and the indexes catch up. A caller that needs the write on stable storage before it continues opts in with X-Relata-Durability: sync, and a reader that must see a given write can wait for it with the freshness headers. See Ingestion.

Pages removed from this section

Earlier pages for AML sanctions screening, law-enforcement link analysis, telecom CDR, maritime AIS, OSINT identity fusion, "consolidate your polyglot stack", Sigma detection and the per-role pages relied on retired protocol doors, retired SQL operators (SANCTIONS_SCREEN, CRYPTO_TRACE, WIRE_RECONSTRUCTION, BENEFICIAL_OWNERSHIP_CHAIN), Sigma import, report signing or multi-tenancy. They remain valid for the released 2.5.8 line; for 3.0 see Migrating retired doors and the SIEM/SOC migration.