--- title: "statewave vs automem" type: "comparison" canonical_url: "https://www.graphcanon.com/compare/smaramwbc-statewave-vs-verygoodplugins-automem" tools: ["smaramwbc-statewave", "verygoodplugins-automem"] --- # statewave vs automem *GraphCanon updated Aug 21, 2026* ## 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. [statewave](https://statewave.ai) reports 289 GitHub stars, 22 forks, and 14 open issues, last pushed Jul 30, 2026. [automem](https://automem.ai/) has 802 stars, 102 forks, and 15 open issues, last pushed Aug 14, 2026. Figures are from public GitHub metadata via [statewave's repository](https://github.com/smaramwbc/statewave) and [automem's repository](https://github.com/verygoodplugins/automem). | | [statewave](/tools/smaramwbc-statewave.md) | [automem](/tools/verygoodplugins-automem.md) | | --- | --- | --- | | Tagline | Open-source memory runtime for AI agents | Graph-vector memory service for durable, relational AI assistant memory | | Stars | 289 | 802 | | Forks | 22 | 102 | | Open issues | 14 | 15 | | Language | Python | Python | | 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. | AutoMem leverages both graph and vector database technologies to provide AI assistants with durable relational memory. | | Persona | - | - | | Runtime | - | - | | License | Apache-2.0 | AutoMem is licensed under the MIT License, which means it is free to use, modify, and distribute as long as license terms are met. | | Categories | AI Agents, Vector Databases | AI Agents, Vector Databases | ## Trust and health _Sourced signals - not a safety guarantee. No winner column._ | | [statewave](/tools/smaramwbc-statewave.md) | [automem](/tools/verygoodplugins-automem.md) | | --- | --- | --- | | Maintenance | Very active (96%) | Active (82%) | | Days since push | 1d | 7d | | Open issues (now) | 14 | 15 | | Stars delta | Unknown | +9 (30d) | | Open issues delta | Unknown | +4 (30d) | | Owner type | User | Organization | | Full report | [trust report](/tools/smaramwbc-statewave/trust.md) | [trust report](/tools/verygoodplugins-automem/trust.md) | ## 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. ## Decision facts: automem - **Pricing:** freemium - Free for open-source use, with no explicit commercial licensing information provided. - **Adopt for:** AutoMem leverages both graph and vector database technologies to provide AI assistants with durable relational memory. - **License detail:** AutoMem is licensed under the MIT License, which means it is free to use, modify, and distribute as long as license terms are met. ## Choose when ### 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. ### 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 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 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. ## 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](/tools/smaramwbc-statewave/alternatives) and [automem alternatives](/tools/verygoodplugins-automem/alternatives) ([statewave markdown twin](/tools/smaramwbc-statewave/alternatives.md), [automem markdown twin](/tools/verygoodplugins-automem/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/smaramwbc-statewave-vs-verygoodplugins-automem.md) 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](/tools/smaramwbc-statewave/trust); [automem trust report](/tools/verygoodplugins-automem/trust). --- **Machine-readable endpoints** - JSON: [`/api/graphcanon/graph?tool=smaramwbc-statewave`](/api/graphcanon/graph?tool=smaramwbc-statewave) - 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/_