A · level
claude-mem
97.0
117,865 stars · Apache-2.0
AI Agents
Too close to call · 97.0 to 97.9
A · level
97.0
117,865 stars · Apache-2.0
B · level
97.9
161,357 stars · Apache-2.0
claude-mem versus Dify is a AI Agents comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. claude-mem is written mainly in TypeScript; Dify is written mainly in Python. The composite score is 97.0 for claude-mem and 97.9 for Dify.
Dify has 161,357 GitHub stars to claude-mem's 117,865, a gap of 43,492 (1.37×). Forks are 10,242 for claude-mem and 25,515 for Dify. On the log scale used inside this pair, adoption is 97 versus 100, and the fork community is 91 versus 100.
Push history: claude-mem was last pushed on 17 November 2026 (0 days ago), and Dify was last pushed on 17 November 2026 (0 days ago). Open issues stand at 159 for claude-mem (0.001 per star) and 1,422 for Dify (0.009 per star). Issue-health scores are 96 and 84; activity scores are 100 and 100.
Both claude-mem and Dify are listed as Apache-2.0. A permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. The license score is therefore level at 96 versus 96, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.
In AI Agents, both claude-mem (117,865 stars) and Dify (161,357 stars) are marked self-hostable. Deploy scores are 100 and 100. Running either one means you own upgrades, backups, and the license duties that follow a modified copy. Pricing labels on file: claude-mem is open source, Dify is open source.
The lead is split. claude-mem is furthest ahead on issue health (96 to 84), while Dify is furthest ahead on fork community (100 to 91). Choose the dimension a rollout cannot compromise on.
Composite score: claude-mem 97.0, Dify 97.9. The margin is under one point, so this page calls a tie. Use the dimension breakdown rather than the headline number.
Scores are computed inside this pair only. Method and weights.
Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.
| Signal | claude-mem | Dify |
|---|---|---|
| GitHub stars | 117,865 | 161,357 |
| Forks | 10,242 | 25,515 |
| Open issues | 159 | 1,422 |
| Adoption | 97 | 100 |
| Activity | 100 | 100 |
| Community | 91 | 100 |
| Issue health | 96 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 97.0 | 97.9 |
Persistent Context Across Sessions for Every Agent – Captures everything your agent does during sessions, compresses it with AI, and injects relevant context back into future sessions. Works with Claude Code, OpenClaw, Codex, Gemini, Hermes, Copilot, OpenCode + More
Dify is a platform for building LLM apps: prompts, RAG pipelines, agents, and observability. It is aimed at teams that want that stack on their own machines.
Dify has more GitHub stars: 161,357 versus 117,865 for claude-mem. The gap is 43,492 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both claude-mem and Dify as self-hostable. Confirm each project's deploy docs before you plan a migration.
claude-mem is listed as Apache-2.0, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. Dify is listed as Apache-2.0, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Neither tool clears a one-point margin. claude-mem scores 97.0 and Dify scores 97.9.