MemoryHub packages governed shared memory for AI-agent fleets on OpenShift AI
The Red Hat AI Americas field build combines MCP access, scoped storage, provenance and audit controls in a reference architecture for teams running many agents.
MemoryHub, a field-built reference project from Red Hat AI Americas, treats AI-agent memory as a governed platform service rather than a private scratchpad attached to one assistant. The project’s repository now describes both a local edition for individual developers and a cluster edition for teams running agents on Red Hat OpenShift AI.
What the pattern changes
The project starts from a useful operational distinction: a single developer may be well served by local files or an assistant’s built-in memory, while a fleet of agents needs identity, access boundaries and a record of what information influenced an action. MemoryHub’s cluster design puts PostgreSQL and pgvector behind an MCP server, then adds scoped access control, version history, provenance branches, contradiction handling and audit events, according to the project documentation.
That makes memory a shared platform concern. Project-scoped records can be reused by agents working in the same context, while broader scopes support cross-project or organizational knowledge. The repository says every read, write, update and deletion is subject to scope enforcement, and that enterprise-scoped memories require human approval.
The OpenShift AI deployment
The cluster edition is designed for OpenShift AI and packages PostgreSQL with pgvector, MinIO object storage, OAuth 2.1 support, on-cluster embedding and reranking models, and a PatternFly-based dashboard. The README also describes air-gapped deployment, Red Hat UBI images and an installation path driven by oc and make install.
Agents reach the service through MCP, a typed Python SDK or a command-line client. The MCP layer exposes memory operations over streamable HTTP, while the SDK and CLI handle search, reads, writes and project configuration. A separate local edition uses SQLite and can be installed without cluster infrastructure.
Where platform teams should be cautious
This is a field build, not a supported Red Hat product. Its repository is active and broad, but it also marks several areas—including an operator, expanded observability and some integrations—as planned work. Teams evaluating it should treat the architecture as a reference pattern, validate the access-control and retention behavior against their own policies, and avoid assuming roadmap items are complete.
The more important contribution is the boundary it draws. Once agents share operational knowledge, retrieval quality is only one part of the problem; authorization, provenance, contradiction handling and forensic reconstruction become platform requirements. MemoryHub gives OpenShift AI teams a concrete implementation to examine rather than leaving those controls as an abstract governance checklist.
sources
comments · 0