--- title: "memory-os vs statewave" type: "comparison" canonical_url: "https://www.graphcanon.com/compare/claudiodrews-memory-os-vs-smaramwbc-statewave" tools: ["claudiodrews-memory-os", "smaramwbc-statewave"] --- # memory-os vs statewave *GraphCanon updated Aug 21, 2026* ## Verdict Pick memory-os if memory-OS is a memory operating system tailored for Hermes Agent, focusing on local-first, self-hosted persistent storage and seamless integration with any LLM provider using Qdrant as the vector database; pick statewave if statewave focuses on reproducibility and provenance in memory management for AI agents, using Postgres plus pgvector for self-hosted operations rather than relying on query-time retrieval. [memory-os](https://github.com/ClaudioDrews/memory-os) reports 1.3k GitHub stars, 124 forks, and 9 open issues, last pushed Jun 10, 2026. [statewave](https://statewave.ai) has 289 stars, 22 forks, and 14 open issues, last pushed Jul 30, 2026. Figures are from public GitHub metadata via [memory-os's repository](https://github.com/ClaudioDrews/memory-os) and [statewave's repository](https://github.com/smaramwbc/statewave). | | [memory-os](/tools/claudiodrews-memory-os.md) | [statewave](/tools/smaramwbc-statewave.md) | | --- | --- | --- | | Tagline | A 7-layer memory operating system for Hermes Agent with persistent memory and context injection | Open-source memory runtime for AI agents | | Stars | 1,332 | 289 | | Forks | 124 | 22 | | Open issues | 9 | 14 | | Language | Python | Python | | Adopt for | Memory-OS is a memory operating system tailored for Hermes Agent, focusing on local-first, self-hosted persistent storage and seamless integration with any LLM provider using Qdrant as the vector database. | Statewave focuses on reproducibility and provenance in memory management for AI agents, using Postgres plus pgvector for self-hosted operations rather than relying on query-time retrieval. | | Persona | - | - | | Runtime | - | - | | License | MIT | Apache-2.0 | | Categories | AI Agents, Vector Databases | AI Agents, Vector Databases | ## Trust and health _Sourced signals - not a safety guarantee. No winner column._ | | [memory-os](/tools/claudiodrews-memory-os.md) | [statewave](/tools/smaramwbc-statewave.md) | | --- | --- | --- | | Maintenance | Steady (60%) | Very active (96%) | | Days since push | 72d | 1d | | Open issues (now) | 9 | 14 | | Stars delta | +41 (30d) | Unknown | | Open issues delta | +2 (30d) | Unknown | | Full report | [trust report](/tools/claudiodrews-memory-os/trust.md) | [trust report](/tools/smaramwbc-statewave/trust.md) | ## Decision facts: memory-os - **Adopt for:** Memory-OS is a memory operating system tailored for Hermes Agent, focusing on local-first, self-hosted persistent storage and seamless integration with any LLM provider using Qdrant as the vector database. ## Decision facts: statewave - **Adopt for:** Statewave focuses on reproducibility and provenance in memory management for AI agents, using Postgres plus pgvector for self-hosted operations rather than relying on query-time retrieval. ## Choose when ### Choose memory-os if… - License: memory-os is MIT, statewave is Apache-2.0. - Tags unique to memory-os: ai-memory, context-injection, docker, ground-truth. - - You are working with Hermes Agent and require a sophisticated memory management solution that operates locally. ### Choose statewave if… - License: statewave is Apache-2.0, memory-os is MIT. - Tags unique to statewave: agent-memory, ai-agents, llm, memory. - statewave ships Docker support for self-hosted deployment. - Use when needing reproducible and documented context bundles to ensure consistent agent performance over time, as Statewave's design specifically supports provenance tagging for each context bundle. ## When NOT to use memory-os - - If you are looking for a completely cloud-managed service without any local setup or maintenance needs. - - Your use case does not align with Hermes Agent; Memory-OS is specifically designed to complement this agent's functions and won't provide the same benefits when used independently. ## When NOT to use statewave - Avoid if your application cannot leverage or benefit from a self-hosted memory runtime setup specifically using Postgres and pgvector. - Not suitable for cases where query-time document retrieval is preferred over maintaining provenance-tagged, static context bundles. ## Common questions ### What is the difference between memory-os and statewave? memory-os: A 7-layer memory operating system for Hermes Agent with persistent memory and context injection. statewave: Open-source memory runtime for AI agents. See the comparison table for live GitHub stats and shared categories. ### When should I choose memory-os over statewave? Choose memory-os over statewave when License: memory-os is MIT, statewave is Apache-2.0; Tags unique to memory-os: ai-memory, context-injection, docker, ground-truth; - You are working with Hermes Agent and require a sophisticated memory management solution that operates locally. ### When should I choose statewave over memory-os? Choose statewave over memory-os when License: statewave is Apache-2.0, memory-os is MIT; Tags unique to statewave: agent-memory, ai-agents, llm, memory; statewave ships Docker support for self-hosted deployment; Use when needing reproducible and documented context bundles to ensure consistent agent performance over time, as Statewave's design specifically supports provenance tagging for each context bundle. ### When should I avoid memory-os? - If you are looking for a completely cloud-managed service without any local setup or maintenance needs. - Your use case does not align with Hermes Agent; Memory-OS is specifically designed to complement this agent's functions and won't provide the same benefits when used independently. ### When should I avoid statewave? Avoid if your application cannot leverage or benefit from a self-hosted memory runtime setup specifically using Postgres and pgvector. Not suitable for cases where query-time document retrieval is preferred over maintaining provenance-tagged, static context bundles. ### Is memory-os or statewave more popular on GitHub? memory-os has more GitHub stars (1,332 vs 289). Stars measure visibility, not whether either tool fits your constraints. ### Are memory-os and statewave open source? Yes - both are open-source projects on GitHub (memory-os: MIT, statewave: Apache-2.0). ### Where can I find alternatives to memory-os or statewave? GraphCanon lists graph-backed alternatives at [memory-os alternatives](/tools/claudiodrews-memory-os/alternatives) and [statewave alternatives](/tools/smaramwbc-statewave/alternatives) ([memory-os markdown twin](/tools/claudiodrews-memory-os/alternatives.md), [statewave markdown twin](/tools/smaramwbc-statewave/alternatives.md)), ranked by typed relationship edges rather than popularity votes. ### Is there a machine-readable version of this comparison? Yes. The markdown twin at [this comparison](/compare/claudiodrews-memory-os-vs-smaramwbc-statewave.md) mirrors this page for agents and LLM crawlers, with the same stats table and FAQ answers. ### Which is better maintained, memory-os or statewave? memory-os: Steady. statewave: Very active. Compare maintenance labels, days since push, and release cadence in the trust section below - stars alone do not measure maintenance. ### Where are the full trust reports for memory-os and statewave? GraphCanon publishes per-repo trust reports with dated maintenance, provenance, and scan summaries: [memory-os trust report](/tools/claudiodrews-memory-os/trust); [statewave trust report](/tools/smaramwbc-statewave/trust). --- **Machine-readable endpoints** - JSON: [`/api/graphcanon/graph?tool=claudiodrews-memory-os`](/api/graphcanon/graph?tool=claudiodrews-memory-os) - LLM index: [/llms.txt](/llms.txt) - Full corpus: [/llms-full.txt](/llms-full.txt) _GraphCanon - The knowledge graph for AI development. https://www.graphcanon.com/_