Comparison
memory-os vs automem
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 automem if autoMem leverages both graph and vector database technologies to provide AI assistants with durable relational memory.
Markdown twin · memory-os alternatives · automem alternatives
GraphCanon updated 3d
vs
Trust & integrity
| Signal | memory-os | automem |
|---|---|---|
| Maintenance | Steady (72d since push) As of 3d · github_public_v1 | Active (7d since push) As of 3d · github_public_v1 |
| Provenance | Not a fork · Personal account As of 3d · github_public_v1 | Not a fork · Organization account As of 3d · 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
- automem
- Graph-vector memory service for durable, relational AI assistant memory
Stars
- memory-os
- 1.3k
- automem
- 802
Forks
- memory-os
- 124
- automem
- 102
Open issues
- memory-os
- 9
- automem
- 15
Language
- memory-os
- Python
- automem
- 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.
- automem
- AutoMem leverages both graph and vector database technologies to provide AI assistants with durable relational memory.
Persona
- memory-os
- -
- automem
- -
Runtime
- memory-os
- -
- automem
- -
License
- memory-os
- MIT
- automem
- AutoMem is licensed under the MIT License, which means it is free to use, modify, and distribute as long as license terms are met.
Last pushed
- memory-os
- Jun 10, 2026
- automem
- Aug 14, 2026
Categories
- memory-os
- AI Agents, Vector Databases
- automem
- AI Agents, Vector Databases
Trust and health
Maintenance
- memory-os
- Steady (60%)
- automem
- Active (82%)
Days since push
- memory-os
- 72d
- automem
- 7d
Open issues (now)
- memory-os
- 9
- automem
- 15
Stars delta
- memory-os
- +41 (30d)
- automem
- +9 (30d)
Open issues delta
- memory-os
- +2 (30d)
- automem
- +4 (30d)
Owner type
- memory-os
- User
- automem
- Organization
Full report
- memory-os
- Trust report
- automem
- Trust report
Choose memory-os if…
- Tags unique to memory-os: context-injection, docker, ground-truth, hermes-agent.
- - You are working with Hermes Agent and require a sophisticated memory management solution that operates locally.
- More GitHub stars (1.3k vs 802) - visibility, not fit.
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 automem if…
- Pricing: Free for open-source use, with no explicit commercial licensing information provided..
- Tags unique to automem: anthropic, falkordb, graph-database, llm.
- automem ships Docker support for self-hosted deployment.
- Use AutoMem when you need an AI assistant capable of maintaining rich, relational memories over time.
When NOT to use automem
- Avoid using AutoMem if your application does not benefit from persistent memory or relational context, as it might add unnecessary overhead.
- If you require a simpler key-value storage system for less complex or non-relational data, AutoMem's graph and vector capabilities may be overkill.
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 (verygoodplugins/automem) · observed Aug 21, 2026
- GitHub forks (verygoodplugins/automem) · observed Aug 21, 2026
- Last push (verygoodplugins/automem) · observed Aug 14, 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 on cards: memory-os 1.3k · automem 802 (synced Aug 21, 2026).
Common questions
- What is the difference between memory-os and automem?
- memory-os: A 7-layer memory operating system for Hermes Agent with persistent memory and context injection. automem: Graph-vector memory service for durable, relational AI assistant memory. See the comparison table for live GitHub stats and shared categories.
- When should I choose memory-os over automem?
- Choose memory-os over automem when Tags unique to memory-os: context-injection, docker, ground-truth, hermes-agent; - You are working with Hermes Agent and require a sophisticated memory management solution that operates locally; More GitHub stars (1.3k vs 802) - visibility, not fit.
- When should I choose automem over memory-os?
- Choose automem over memory-os when Pricing: Free for open-source use, with no explicit commercial licensing information provided.; Tags unique to automem: anthropic, falkordb, graph-database, llm; automem ships Docker support for self-hosted deployment; Use AutoMem when you need an AI assistant capable of maintaining rich, relational memories over time.
- 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 automem?
- Avoid using AutoMem if your application does not benefit from persistent memory or relational context, as it might add unnecessary overhead. If you require a simpler key-value storage system for less complex or non-relational data, AutoMem's graph and vector capabilities may be overkill.
- Is memory-os or automem more popular on GitHub?
- memory-os has more GitHub stars (1,332 vs 802). Stars measure visibility, not whether either tool fits your constraints.
- Are memory-os and automem open source?
- Yes - both are open-source projects on GitHub (memory-os: MIT, automem: MIT).
- Where can I find alternatives to memory-os or automem?
- GraphCanon lists graph-backed alternatives at memory-os alternatives and automem alternatives (memory-os markdown twin, automem 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 automem?
- memory-os: Steady. automem: 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 automem?
- GraphCanon publishes per-repo trust reports with dated maintenance, provenance, and scan summaries: memory-os trust report; automem trust report.