Comparison
OpenMemory vs TencentDB-Agent-Memory
Verdict
Pick OpenMemory when license: OpenMemory is Apache-2.0, TencentDB-Agent-Memory is Other; pick TencentDB-Agent-Memory when license: TencentDB-Agent-Memory is Other, OpenMemory is Apache-2.0.
Markdown twin · OpenMemory alternatives · TencentDB-Agent-Memory alternatives
GraphCanon updated today
vs
Trust & integrity
| Signal | OpenMemory | TencentDB-Agent-Memory |
|---|---|---|
| Maintenance | Active (14d since push) As of today · github_public_v1 | Active (15d since push) As of today · github_public_v1 |
| Provenance | Not a fork · Organization account As of today · github_public_v1 | Not a fork · Organization account As of today · github_public_v1 |
| Security (OSV) | No lockfile As of today · none | No lockfile As of today · none |
Tagline
- OpenMemory
- Local persistent memory store for LLM applications including claude desktop, github copilot, codex, antigravity, etc.
- TencentDB-Agent-Memory
- TencentDB Agent Memory delivers fully local long-term memory for AI Agents via a 4-tier progressive pipeline, with zero external API dependencies.
Stars
- OpenMemory
- 4.3k
- TencentDB-Agent-Memory
- 8.4k
Forks
- OpenMemory
- 490
- TencentDB-Agent-Memory
- 772
Open issues
- OpenMemory
- 13
- TencentDB-Agent-Memory
- 257
Language
- OpenMemory
- TypeScript
- TencentDB-Agent-Memory
- TypeScript
Adopt for
- OpenMemory
- Decision-critical facts about OpenMemory
- TencentDB-Agent-Memory
- -
Persona
- OpenMemory
- -
- TencentDB-Agent-Memory
- -
Runtime
- OpenMemory
- -
- TencentDB-Agent-Memory
- -
License
- OpenMemory
- Apache-2.0
- TencentDB-Agent-Memory
- Other
Last pushed
- OpenMemory
- Jun 27, 2026
- TencentDB-Agent-Memory
- Jun 26, 2026
Categories
- OpenMemory
- AI Agents, Vector Databases, LLM Frameworks
- TencentDB-Agent-Memory
- LLM Frameworks, AI Agents, Vector Databases
Trust and health
Days since push
- OpenMemory
- 14d
- TencentDB-Agent-Memory
- 15d
Open issues (now)
- OpenMemory
- 13
- TencentDB-Agent-Memory
- 257
Full report
- OpenMemory
- Trust report
- TencentDB-Agent-Memory
- Trust report
Choose OpenMemory if…
- License: OpenMemory is Apache-2.0, TencentDB-Agent-Memory is Other.
- Requirements: Install using the npm commands provided in the README to add `opm` to your PATH..
- Tags unique to OpenMemory: embeddings, cognitive-architecture, ai, artificial-intelligence.
- When you need a local, persistent memory store specifically tailored for applications like claude desktop and GitHub Copilot, where maintaining context over time is essential.
When NOT to use OpenMemory
- Avoid OpenMemory if your project needs seamless integration with cloud-based infrastructure or services that require networked persistence beyond the local scope.
- Do not use this tool if you seek a highly scalable solution for distributed systems where memory stores must be shared across multiple nodes without performance degradation.
Choose TencentDB-Agent-Memory if…
- License: TencentDB-Agent-Memory is Other, OpenMemory is Apache-2.0.
- Tags unique to TencentDB-Agent-Memory: memory, llm, local-first, openclaw-plugin.
- More GitHub stars (8.4k vs 4.3k) - visibility, not fit.
When NOT to use TencentDB-Agent-Memory
- LLM Frameworks: Avoid a framework for a single prompt-and-retrieve call; the abstraction can cost more than it saves.
- AI Agents: Don't use an agent loop when a deterministic workflow would do; agents add latency, cost, and non-determinism.
- Vector Databases: Don't reach for a dedicated vector DB under ~100k vectors; pgvector on your existing Postgres is simpler to operate.
Explore
Sources
Every stat on this page traces to a dated GitHub sync, license file, enrichment field, or trust scan.
- GitHub stars (CaviraOSS/OpenMemory) · observed Jul 11, 2026
- GitHub forks (CaviraOSS/OpenMemory) · observed Jul 11, 2026
- Last push (CaviraOSS/OpenMemory) · observed Jun 27, 2026
- License file (Apache-2.0) · observed Jul 11, 2026
- Decision facts (enrichment) · observed Jul 11, 2026
- Trust scan (lockfile / OSV) · observed Jul 11, 2026
- GitHub stars (TencentCloud/TencentDB-Agent-Memory) · observed Jul 11, 2026
- GitHub forks (TencentCloud/TencentDB-Agent-Memory) · observed Jul 11, 2026
- Last push (TencentCloud/TencentDB-Agent-Memory) · observed Jun 26, 2026
- License file (Other) · observed Jul 11, 2026
- Trust scan (lockfile / OSV) · observed Jul 11, 2026
GitHub stars on cards: OpenMemory 4.3k · TencentDB-Agent-Memory 8.4k (synced Jul 11, 2026).
Common questions
- What is the difference between OpenMemory and TencentDB-Agent-Memory?
- OpenMemory: Local persistent memory store for LLM applications including claude desktop, github copilot, codex, antigravity, etc.. TencentDB-Agent-Memory: TencentDB Agent Memory delivers fully local long-term memory for AI Agents via a 4-tier progressive pipeline, with zero external API dependencies.. See the comparison table for live GitHub stats and shared categories.
- When should I choose OpenMemory over TencentDB-Agent-Memory?
- Choose OpenMemory over TencentDB-Agent-Memory when License: OpenMemory is Apache-2.0, TencentDB-Agent-Memory is Other; Requirements: Install using the npm commands provided in the README to add
opmto your PATH.; Tags unique to OpenMemory: embeddings, cognitive-architecture, ai, artificial-intelligence; When you need a local, persistent memory store specifically tailored for applications like claude desktop and GitHub Copilot, where maintaining context over time is essential. - When should I choose TencentDB-Agent-Memory over OpenMemory?
- Choose TencentDB-Agent-Memory over OpenMemory when License: TencentDB-Agent-Memory is Other, OpenMemory is Apache-2.0; Tags unique to TencentDB-Agent-Memory: memory, llm, local-first, openclaw-plugin; More GitHub stars (8.4k vs 4.3k) - visibility, not fit.
- When should I avoid OpenMemory?
- Avoid OpenMemory if your project needs seamless integration with cloud-based infrastructure or services that require networked persistence beyond the local scope. Do not use this tool if you seek a highly scalable solution for distributed systems where memory stores must be shared across multiple nodes without performance degradation.
- When should I avoid TencentDB-Agent-Memory?
- LLM Frameworks: Avoid a framework for a single prompt-and-retrieve call; the abstraction can cost more than it saves. AI Agents: Don't use an agent loop when a deterministic workflow would do; agents add latency, cost, and non-determinism. Vector Databases: Don't reach for a dedicated vector DB under ~100k vectors; pgvector on your existing Postgres is simpler to operate.
- Is OpenMemory or TencentDB-Agent-Memory more popular on GitHub?
- TencentDB-Agent-Memory has more GitHub stars (8,404 vs 4,323). Stars measure visibility, not whether either tool fits your constraints.
- Are OpenMemory and TencentDB-Agent-Memory open source?
- Yes - both are open-source projects on GitHub (OpenMemory: Apache-2.0, TencentDB-Agent-Memory: Other).
- Where can I find alternatives to OpenMemory or TencentDB-Agent-Memory?
- GraphCanon lists graph-backed alternatives at OpenMemory alternatives and TencentDB-Agent-Memory alternatives (OpenMemory markdown twin, TencentDB-Agent-Memory 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, OpenMemory or TencentDB-Agent-Memory?
- OpenMemory: Active. TencentDB-Agent-Memory: 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 OpenMemory and TencentDB-Agent-Memory?
- GraphCanon publishes per-repo trust reports with dated maintenance, provenance, and scan summaries: OpenMemory trust report; TencentDB-Agent-Memory trust report.