metronix-memory vs omnigraph
Self-hosted agent memory stack in Docker: Postgres + Qdrant + Neo4j hybrid retrieval, a temporal knowledge graph, ontology layer and freshness checks behind one MCP-native API. — versus — Lakehouse graph database for agent context — graph, vector and full-text retrieval fused in one runtime on branchable Lance/S3 storage; agent fleets write on isolated branches and merge Git-style.
Both fuse graph, vector and full-text retrieval into one agent-context runtime. OmniGraph is a lakehouse database with Git-style branch/merge for agent fleets; Metronix is a batteries-included memory service you point an agent at.
| metronix-memory | omnigraph | |
|---|---|---|
| Stars | 95 | 1.1k |
| Forks | 9 | 267 |
| Language | Python | Rust |
| License | Apache-2.0 | MIT |
| Last activity | 3 days ago | today |
| Topics | memory, rag, knowledge-graphs | memory, knowledge-graphs |
| Curated connections | 6 | 10 |
metronix-memory — the curator's take
Reach for it when you want one self-hosted box doing dense + sparse + graph retrieval and keeping long-lived facts fresh, and you're willing to run four datastores to get it. Skip it if you only need per-project session recall — a SQLite memory plugin is a fraction of the operational surface. Read the benchmark table with care: they are the author's own N=1 runs under a self-defined protocol, and the honest signal in them is that retrieval scores (Recall@10 85-95%) far outrun end-to-end answers (53-63%) — finding the evidence was never the hard part.
omnigraph — the curator's take
Reach for it when many agents must share one evolving knowledge store and you need blame, rollback and review on their writes — branch-per-agent with merge gates is the feature nothing else in this space has; also strong when retrieval genuinely needs graph + vector + full-text fused, not a vector store with metadata filters. NOT a drop-in vector DB: you take on a server, cluster.yaml, schemas and Cedar policy — for plain RAG recall, Chroma is answering queries before you've finished omnigraph's docs. Young project on a credible Rust/Lance foundation; expect sharp edges and a moving API.