Comparison
statewave vs automem
Verdict
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; pick automem if autoMem leverages both graph and vector database technologies to provide AI assistants with durable relational memory.
Markdown twin · statewave alternatives · automem alternatives
GraphCanon updated 3d
vs
Trust & integrity
| Signal | statewave | automem |
|---|---|---|
| Maintenance | Very active (1d since push) As of 3w · github_public_v1 | Active (7d since push) As of 3d · github_public_v1 |
| Provenance | Not a fork · Personal account As of 3w · 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
- statewave
- Open-source memory runtime for AI agents
- automem
- Graph-vector memory service for durable, relational AI assistant memory
Stars
- statewave
- 289
- automem
- 802
Forks
- statewave
- 22
- automem
- 102
Open issues
- statewave
- 14
- automem
- 15
Language
- statewave
- Python
- automem
- Python
Adopt for
- 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.
- automem
- AutoMem leverages both graph and vector database technologies to provide AI assistants with durable relational memory.
Persona
- statewave
- -
- automem
- -
Runtime
- statewave
- -
- automem
- -
License
- statewave
- Apache-2.0
- 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
- statewave
- Jul 30, 2026
- automem
- Aug 14, 2026
Categories
- statewave
- AI Agents, Vector Databases
- automem
- AI Agents, Vector Databases
Trust and health
Maintenance
- statewave
- Very active (96%)
- automem
- Active (82%)
Days since push
- statewave
- 1d
- automem
- 7d
Open issues (now)
- statewave
- 14
- automem
- 15
Stars delta
- statewave
- Unknown
- automem
- +9 (30d)
Open issues delta
- statewave
- Unknown
- automem
- +4 (30d)
Owner type
- statewave
- User
- automem
- Organization
Full report
- statewave
- Trust report
- automem
- Trust report
Choose statewave if…
- License: statewave is Apache-2.0, automem is MIT.
- Tags unique to statewave: agent-memory, ai-agents, memory, pgvector.
- 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.
Choose automem if…
- License: automem is MIT, statewave is Apache-2.0.
- Pricing: Free for open-source use, with no explicit commercial licensing information provided..
- Tags unique to automem: ai-memory, anthropic, falkordb, graph-database.
- 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 (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 (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: statewave 289 · automem 802 (synced Aug 1, 2026).
Common questions
- What is the difference between statewave and automem?
- statewave: Open-source memory runtime for AI agents. 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 statewave over automem?
- Choose statewave over automem when License: statewave is Apache-2.0, automem is MIT; Tags unique to statewave: agent-memory, ai-agents, memory, pgvector; 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 choose automem over statewave?
- Choose automem over statewave when License: automem is MIT, statewave is Apache-2.0; Pricing: Free for open-source use, with no explicit commercial licensing information provided.; Tags unique to automem: ai-memory, anthropic, falkordb, graph-database; Use AutoMem when you need an AI assistant capable of maintaining rich, relational memories over time.
- 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.
- 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 statewave or automem more popular on GitHub?
- automem has more GitHub stars (802 vs 289). Stars measure visibility, not whether either tool fits your constraints.
- Are statewave and automem open source?
- Yes - both are open-source projects on GitHub (statewave: Apache-2.0, automem: MIT).
- Where can I find alternatives to statewave or automem?
- GraphCanon lists graph-backed alternatives at statewave alternatives and automem alternatives (statewave 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, statewave or automem?
- statewave: Very active. 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 statewave and automem?
- GraphCanon publishes per-repo trust reports with dated maintenance, provenance, and scan summaries: statewave trust report; automem trust report.