Comparison
memory-os vs statewave
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.
Markdown twin · memory-os alternatives · statewave alternatives
GraphCanon updated 4d
vs
Trust & integrity
| Signal | memory-os | statewave |
|---|---|---|
| Maintenance | Steady (72d since push) As of 4d · github_public_v1 | Very active (1d since push) As of 3w · github_public_v1 |
| Provenance | Not a fork · Personal account As of 4d · github_public_v1 | Not a fork · Personal account As of 3w · github_public_v1 |
| OSV dependency advisories | No lockfile (source not queried) As of 1mo · osv@v1 | No lockfile (source not queried) As of 1mo · osv@v1 |
| deps.dev advisories | Not queried deps.dev@v1 | Not queried deps.dev@v1 |
| OpenSSF Scorecard | Not queried openssf-scorecard@v1 | Not queried openssf-scorecard@v1 |
Tagline
- 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
Stars
- memory-os
- 1.3k
- statewave
- 289
Forks
- memory-os
- 124
- statewave
- 22
Open issues
- memory-os
- 9
- statewave
- 14
Language
- memory-os
- Python
- statewave
- Python
Adopt for
- memory-os
- 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
- 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
- memory-os
- -
- statewave
- -
Runtime
- memory-os
- -
- statewave
- -
License
- memory-os
- MIT
- statewave
- Apache-2.0
Last pushed
- memory-os
- Jun 10, 2026
- statewave
- Jul 30, 2026
Categories
- memory-os
- AI Agents, Vector Databases
- statewave
- AI Agents, Vector Databases
Trust and health
Maintenance
- memory-os
- Steady (60%)
- statewave
- Very active (96%)
Days since push
- memory-os
- 72d
- statewave
- 1d
Open issues (now)
- memory-os
- 9
- statewave
- 14
Stars delta
- memory-os
- +41 (30d)
- statewave
- Unknown
Open issues delta
- memory-os
- +2 (30d)
- statewave
- Unknown
Full report
- memory-os
- Trust report
- statewave
- Trust report
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.
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.
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 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.
Explore
Sources
Every stat on this page traces to a dated GitHub sync, license file, enrichment field, or trust scan.
- GitHub stars (ClaudioDrews/memory-os) · observed Aug 21, 2026
- GitHub forks (ClaudioDrews/memory-os) · observed Aug 21, 2026
- Last push (ClaudioDrews/memory-os) · observed Jun 10, 2026
- License file (MIT) · observed Aug 21, 2026
- Decision facts (enrichment) · observed Jul 12, 2026
- Trust scan (lockfile / OSV) · observed Jul 11, 2026
- GitHub stars (smaramwbc/statewave) · observed Aug 1, 2026
- GitHub forks (smaramwbc/statewave) · observed Aug 1, 2026
- Last push (smaramwbc/statewave) · observed Jul 30, 2026
- License file (Apache-2.0) · observed Aug 1, 2026
- Decision facts (enrichment) · observed Jul 14, 2026
- Trust scan (lockfile / OSV) · observed Jul 11, 2026
GitHub stars on cards: memory-os 1.3k · statewave 289 (synced Aug 21, 2026).
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 and statewave alternatives (memory-os markdown twin, statewave markdown twin), 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 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; statewave trust report.