Memoria vs memory-os
Rust memory layer for AI agents with Git-style version control — snapshot, branch, merge and rollback over MatrixOne's copy-on-write engine, plus hybrid vector + full-text retrieval. — versus — A 7-layer memory operating system for Hermes Agent: Qdrant vectors, structured facts, fabric recall, an auto-curated wiki, and surgical context injection.
Both are persistent agent memory layers; memory-os is a 7-layer Qdrant-based memory OS, Memoria is a Rust versioned store with time-travel rollback and provenance chains.
| Memoria | memory-os | |
|---|---|---|
| Stars | 422 | 1.3k |
| Forks | 53 | 120 |
| Language | Rust | Python |
| License | Apache-2.0 | MIT |
| Last activity | 27 days ago | 1 months ago |
| Topics | memory | memory |
| Curated connections | 4 | 3 |
Memoria — the curator's take
Pick it when memory auditability and reversibility matter — you want to branch an agent's memory, roll back a bad write, or trace the provenance of every fact, and you're fine running MatrixOne underneath. Overkill if you just need a simple recall store (memmachine, memmolt) or fully-local files (memanto) — the versioning engine and DB dependency are the cost. Young project, Apache-2.0.
memory-os — the curator's take
The most architecturally ambitious take on agent memory we've mapped: seven distinct layers from raw vectors to an auto-curated wiki, each with its own recall path, so the agent gets the RIGHT kind of memory injected rather than a similarity dump. The catch is coupling: it's built FOR Hermes Agent — adopting the architecture elsewhere means porting, not installing; and 7 layers is real operational surface for a ~1.3k-star project.