Compatibility and retired doors
Through 2.5.8, Relata could listen on the wire protocols of other databases (the "doors"). In 3.0 these public listeners are retired. Their listeners, routes and wire decoders no longer ship, and the RELATA_<DOOR>_ENABLE, _BIND and _PORT variables for them have no effect. Stored rows and provenance are kept.
What is retired
| Retired | Use instead |
|---|---|
| MongoDB wire | HTTP/JSON ingest and query; map documents to typed rows |
| PostgreSQL wire and pgvector drivers | POST /v1/query, the SDKs, or MCP tools |
| Redis RESP | HTTP/JSON operations on governed rows |
| ClickHouse HTTP and native | POST /v1/query and the ingest routes |
| Neo4j HTTP and Bolt | A Cypher subset on POST /v1/query with x-query-dialect: cypher, or SQL graph operators |
| S3-compatible listener | The HTTP Files API under /v1/files (not S3-compatible) |
| Arrow Flight | POST /v1/query/arrow and POST /v1/ingest/bulk |
/sparql | SQL over KnowledgeTriple |
Full detail, including Kafka legacy rows: Migrating from retired doors.
What remains
| Interface | Where | Notes |
|---|---|---|
| HTTP/JSON | /v1/*, OpenAPI 3.1 at GET /openapi.json | The public API contract |
| GraphQL | POST /v1/graphql | Read-only translated subset, not a GraphQL engine |
| MCP | POST /mcp, /v1/mcp/* | JSON-RPC 2.0 over HTTP; list tools with GET /v1/mcp/tools |
| A2A | /v1/a2a/* | Agent tasks and LangGraph-style checkpoints |
| Search | /v1/search, /v1/search/multi | BM25, vector and hybrid |
| Internal cluster gRPC | authenticated, internal | Not a client interface; Enterprise track |
| Admin listener | loopback 127.0.0.1:9091 | /admin/* only |
SDKs: Python, TypeScript and Go are the supported consumer SDKs. Other languages use HTTP, optionally with a client generated from the OpenAPI document, which is not an officially supported SDK.
The route changes are listed in HTTP route restructure. To see which interfaces a running server is serving, query GET /admin/system on the loopback admin listener (see the migration guide).
What the retirement does not change
Governance still applies on every remaining interface: type grants, column masking, purposes, tenant scoping and the audit log. Bi-temporal history and provenance are unchanged. See Governance and audit.