Retired protocol doors

Relata DB 3.0
This page describes Relata DB 3.0, the current release. In 2.5.8 the door recipes that used to live here still apply.

The recipes for enabling a compatibility door, overriding its RELATA_<DOOR>_BIND and publishing its port no longer apply in 3.0: the MongoDB, PostgreSQL/pgvector, Redis, Neo4j HTTP, Bolt, ClickHouse, S3-compatible and Arrow Flight listeners do not ship. There is nothing to enable and no door port to publish.

What to publish instead

A 3.0 node serves HTTP/JSON, read-only GraphQL, MCP, A2A and search on one port, plus a loopback-only admin listener.

ListenerDefaultExposure
HTTP data planeRELATA_PORT (9090), bind 127.0.0.1Set RELATA_HTTP_BIND to expose it. Exposure requires TLS (in-process with RELATA_TLS_CERT and RELATA_TLS_KEY, or at a proxy with RELATA_PLAINTEXT_OK=true).
Admin127.0.0.1:9091Do not publish. Reach it from the host, a port-forward or a sidecar.

Authentication is mandatory. The data plane accepts registry-minted tokens, not the bootstrap secret RELATA_BEARER_TOKEN; mint one on the admin listener with RELATA_ADMIN_TOKEN. A container needs explicit RELATA_* environment to start, so copy the compose file from Installation rather than running the image with no environment.

Publish only the HTTP port you need; every published port is attack surface.

Migrating clients

See Migrating from retired doors for where each former door's clients go, and Protocols for the interfaces that remain.