Long-term memory across sessions — governed, bi-temporal and traceable, and built on a real knowledge engine, not a scratchpad.
Relata DB 3.0 exposes one HTTP/JSON API with an OpenAPI 3.1 document, Python, TypeScript and Go SDKs, MCP, read-only GraphQL and Arrow over HTTP. The Postgres, Redis, MongoDB, S3, Neo4j/Bolt, ClickHouse and Arrow Flight doors are retired; see the migration guide.
Relata is one database that fixes all three — memory with a backbone.
Agents remember across sessions — and can justify any decision with a traceable chain.
Provenance, time-travel and policy baked into every row and every query.
One HTTP/JSON API with an OpenAPI document, Python, TypeScript and Go SDKs, and MCP tools for agents.
Memory · governed tools · RAG · multi-agent · governance. One agentic database that meets you at rung one and scales with you all the way up.
Governed, temporal knowledge for security, finance, evidence and AI workloads, on one machine. Each use case below states what was exercised and what was not.
Hover to expand →
Hover to expand →
Hover to expand →
Hover to expand →
Hover to expand →
Hover to expand →
Hover to expand →
Hover to expand →
Problem-first walkthroughs using only 3.0 surfaces, each ending with the scenario that exercised it and its recorded defects.
Contract-gated ingest, native window rules, alert triage, hash-verifiable evidence, pivot and graph hunt.
Competing claims from a registry and a CRM, review and correction without overwriting, legal hold, and replay as of any date.
Store and link normalized transfers with history. Detection heuristics stay in your code; no sanctions feed ships.
Resumable evidence uploads, a fenced OpenETL work-item handoff, detections and incident timelines.
Retrieval with citations and replay, memory with masking and purpose, and MCP tools. Masked cells never reach the model.
Typed objects, conditional writes, a change feed and SDKs on one tenant. Many tenants in one deployment is Enterprise.
Verifiable erasure receipts, legal hold precedence, and backup with offline restore.
Data enters the knowledge graph, connections form, and when the agent is asked — it recalls the exact path and answers with provenance.
Hover to explore why one database is enough for memory, search, graph, governance and more.
mem0 and cognee are great memory SDKs. RelataDB is the knowledge engine underneath — with temporal history and governance they don’t offer.
Governance, provenance and policy from the ground up. Deploy on-prem, air-gapped, or in your own environment — your data stays under your control.
PURPOSE + cell-level masking on every read and write, every door.
Bi-temporal rows with provenance — what the system believed, when, and why. Tamper-evident audit is Enterprise.
One binary on one machine: laptop, container, on-prem or air-gapped. Clustering is Enterprise.
Erasure with receipts, legal hold, backup and offline restore.
One binary on one machine — laptop, container or server. No external database, no GPU. Clustering is Relata Enterprise DB.
mem0 and cognee are memory SDKs. RelataDB is the knowledge engine underneath — a real database with bi-temporal history, provenance, identity resolution, and governance built in. Plus one HTTP API, three SDKs and MCP.
Sovereign by design. Deploy on-prem or air-gapped on your own machine. Policy, provenance, and cell-level masking apply to reads and writes. No data leaves your control.
Yes, if you used the compatibility doors. Postgres, Redis, MongoDB, S3, Neo4j/Bolt, ClickHouse and Arrow Flight are retired in 3.0; use the HTTP API or an SDK. The migration guide maps each one.
Yes. It is open source and runs on one machine: Docker, bare metal, or macOS. Authentication is always required; the quickstart shows how to mint a token.
Relata DB 3.0 is open source (AGPL-3.0-only). Relata Enterprise DB, with clustering, several tenants and tamper-evident audit, is priced separately: talk to us.
Yes. Agents get governed MCP tools and long-term memory (remember · recall · forget · justify), bi-temporal and access-controlled. Multiple agents share one knowledge plane on one node.