Comparison
statewave vs memsearch
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 memsearch if memsearch is a hybrid memory management solution for AI agents with Markdown and Milvus backing, ideal for rich semantic search and long-term data storage.
Markdown twin · statewave alternatives · memsearch alternatives
GraphCanon updated 3d
vs
Trust & integrity
| Signal | statewave | memsearch |
|---|---|---|
| Maintenance | Very active (1d since push) As of 3w · github_public_v1 | Very active (0d 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
- memsearch
- A persistent, unified memory layer for all your AI agents backed by Markdown and Milvus.
Stars
- statewave
- 289
- memsearch
- 2.5k
Forks
- statewave
- 22
- memsearch
- 231
Open issues
- statewave
- 14
- memsearch
- 240
Language
- statewave
- Python
- memsearch
- 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.
- memsearch
- memsearch is a hybrid memory management solution for AI agents with Markdown and Milvus backing, ideal for rich semantic search and long-term data storage.
Persona
- statewave
- -
- memsearch
- -
Runtime
- statewave
- -
- memsearch
- -
License
- statewave
- Apache-2.0
- memsearch
- MIT
Last pushed
- statewave
- Jul 30, 2026
- memsearch
- Aug 21, 2026
Categories
- statewave
- AI Agents, Vector Databases
- memsearch
- AI Agents, Data & Retrieval, Vector Databases
Trust and health
Days since push
- statewave
- 1d
- memsearch
- 0d
Open issues (now)
- statewave
- 14
- memsearch
- 240
Stars delta
- statewave
- Unknown
- memsearch
- +155 (30d)
Open issues delta
- statewave
- Unknown
- memsearch
- +9 (30d)
Owner type
- statewave
- User
- memsearch
- Organization
Full report
- statewave
- Trust report
- memsearch
- Trust report
Choose statewave if…
- License: statewave is Apache-2.0, memsearch is MIT.
- Tags unique to statewave: ai-agents, llm, memory, pgvector.
- 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.
Choose memsearch if…
- License: memsearch is MIT, statewave is Apache-2.0.
- Tags unique to memsearch: long-term-memory, milvus, semantic-search.
- Also covers Data & Retrieval.
- When you need robust integration with AI agents like Claude Code or Codex
When NOT to use memsearch
- If your application doesn't require integration with specific AI agents like Claude Code
- In cases where only simple text data storage without semantic search is needed
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 (zilliztech/memsearch) · observed Aug 22, 2026
- GitHub forks (zilliztech/memsearch) · observed Aug 22, 2026
- Last push (zilliztech/memsearch) · observed Aug 21, 2026
- License file (MIT) · observed Aug 22, 2026
- Decision facts (enrichment) · observed Jul 12, 2026
- Trust scan (lockfile / OSV) · observed Jul 11, 2026
GitHub stars on cards: statewave 289 · memsearch 2.5k (synced Aug 1, 2026).
Common questions
- What is the difference between statewave and memsearch?
- statewave: Open-source memory runtime for AI agents. memsearch: A persistent, unified memory layer for all your AI agents backed by Markdown and Milvus.. See the comparison table for live GitHub stats and shared categories.
- When should I choose statewave over memsearch?
- Choose statewave over memsearch when License: statewave is Apache-2.0, memsearch is MIT; Tags unique to statewave: ai-agents, llm, memory, pgvector; 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 choose memsearch over statewave?
- Choose memsearch over statewave when License: memsearch is MIT, statewave is Apache-2.0; Tags unique to memsearch: long-term-memory, milvus, semantic-search; Also covers Data & Retrieval; When you need robust integration with AI agents like Claude Code or Codex.
- 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 memsearch?
- If your application doesn't require integration with specific AI agents like Claude Code In cases where only simple text data storage without semantic search is needed
- Is statewave or memsearch more popular on GitHub?
- memsearch has more GitHub stars (2,491 vs 289). Stars measure visibility, not whether either tool fits your constraints.
- Are statewave and memsearch open source?
- Yes - both are open-source projects on GitHub (statewave: Apache-2.0, memsearch: MIT).
- Where can I find alternatives to statewave or memsearch?
- GraphCanon lists graph-backed alternatives at statewave alternatives and memsearch alternatives (statewave markdown twin, memsearch 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 memsearch?
- statewave: Very active. memsearch: 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 statewave and memsearch?
- GraphCanon publishes per-repo trust reports with dated maintenance, provenance, and scan summaries: statewave trust report; memsearch trust report.