What is new in Relata DB 3.0
Relata DB 3.0 is the open source edition (AGPL-3.0-only): a governed, bi-temporal knowledge database on one machine, with no clustering and none of the enterprise reliability and assurance layer. Clustering, high availability, several tenants, managed users and tamper-evident audit belong to Relata Enterprise DB, the next product line. See Editions.
What changes for you
| Area | In 3.0 | Read more |
|---|---|---|
| HTTP API | Every public data-plane route moves under /v1/. Hard break, no aliases. | Route restructure |
| Protocol doors | PostgreSQL wire, Arrow Flight, S3-compatible listener, Redis RESP, MongoDB wire, ClickHouse (HTTP and native), Neo4j HTTP, Bolt and the /sparql endpoint are retired. Stored data is kept. | Migrating retired doors |
| Supported interfaces | HTTP/JSON with an OpenAPI 3.1 document, read-only GraphQL (a translated subset), MCP, A2A, and search. SDKs: Python, TypeScript, Go. | Interfaces |
| Retrieval | Optional version-pinned citation records for query, search, GraphQL and MCP results, with replay. | Retrieval evidence |
| Investigations | An end-to-end path from ingest to an archived, later retrievable case record. | Investigation and archive workflow |
| Migration | A rehearsed (not qualified) SIEM/SOC cutover procedure and a supported-path matrix. | SIEM/SOC migration |
| Operations | Offline backup, verify and restore; WAL generation rollover; capacity planning. | Backup and restore, Capacity and WAL retention |
| Governance | Cell-level ACL, masking, purposes and a minimal local audit log in the open edition. | Governance and audit |
Editions
| Relata DB (3.0) | Relata Enterprise DB (next) | Relata Cloud | |
|---|---|---|---|
| Source | Public, AGPL-3.0-only | Private, signed binaries | Private |
| Engine (bi-temporal storage, SQL, graph, search, vector, ingest) | Yes | Yes | Yes |
| HTTP/JSON, MCP, read-only GraphQL, Python/TypeScript/Go SDKs | Yes | Yes | Yes |
| Cell-level ACL, masking, classifications | Yes | Yes | Yes |
| Tenants | One | Many | Many |
| Clustering, high availability, replication | No | Yes | Yes |
| Audit | Minimal local log | Tamper-evident, signed, exportable | Same |
| Backup and restore | Yes | Plus point-in-time and disaster recovery | Managed |
Route families that belong to the Enterprise edition (tenant administration, managed users, platform administration, tamper-evident audit proof and export, cluster operations) are not compiled into the open build, are absent from its OpenAPI contract and answer an enterprise-*-required problem response if called.
server and cluster values of RELATA_PROFILE are being retired: the open build accepts only free. Do not read the table above as a claim that the repository split is complete.Supported interfaces
- HTTP/JSON under
/v1/, described by the OpenAPI 3.1 document atGET /openapi.json. Probes (/health,/health/live,/health/ready,/version) and discovery stay unversioned. - GraphQL:
POST /v1/graphql, read-only. A hand-written translator for a documented subset (field selection,limit,where, variables, restricted introspection), not a GraphQL engine. - MCP:
POST /mcp(JSON-RPC 2.0, buffered JSON mode) and the/v1/mcp/*tool routes. Discover tools from the running server withGET /v1/mcp/tools. - A2A:
/v1/a2a/tasksand/v1/a2a/checkpoints/*. - Search:
POST /v1/search,POST /v1/search/multi, saved searches under/v1/search/saved. - Cypher subset: sent to
POST /v1/querywith thex-query-dialect: cypherheader and translated to SQL. The Neo4j HTTP and Bolt listeners are retired. - Python, TypeScript and Go SDKs are the only supported consumer SDKs. Other languages call HTTP or generate a client from the OpenAPI document; a generated client is not a supported SDK. No Rust consumer SDK is supported.
Authentication is required: data-plane requests carry a token minted from the registry, not the bootstrap secret. Writes go through the ingest routes, never through POST /v1/query, which is read-only.
Data in: OpenETL
Relata DB stores, indexes and retrieves data. It does not fetch or transform it. Connectors (Kafka, TAXII, MISP), Sigma conversion, document preparation, model-backed extraction and media processing belong to OpenETL, a separate tool that loads prepared rows through bulk ingest. Relata may call one configured embedding endpoint for queries only. Several of these were removed from the tree in the 3.0 cycle; media processing is still partly present and is moving out.
What is not established yet
Read 3.0 evidence status before planning a go-live. In short: no workload is recorded as qualified, restart after very large ingests has failed on Linux in recorded runs, an in-place 2.7.1 to 3.0 data upgrade is not tested, and the SIEM/SOC migration has been rehearsed only on a synthetic fixture.