A · leads
Dify
97.9
161,357 stars · Apache-2.0
AI Agents
Dify leads by 4.0 · narrow
A · leads
97.9
161,357 stars · Apache-2.0
B
93.9
69,113 stars · Apache-2.0
Dify versus mem0 is a AI Agents comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Both projects are written mainly in Python. The composite score is 97.9 for Dify and 93.9 for mem0.
Dify has 161,357 GitHub stars to mem0's 69,113, a gap of 92,244 (2.33×). Forks are 25,515 for Dify and 8,226 for mem0. On the log scale used inside this pair, adoption is 100 versus 93, and the fork community is 100 versus 89.
Push history: Dify was last pushed on 17 November 2026 (0 days ago), and mem0 was last pushed on 17 November 2026 (0 days ago). Open issues stand at 1,422 for Dify (0.009 per star) and 963 for mem0 (0.014 per star). Issue-health scores are 84 and 84; activity scores are 100 and 100.
Both Dify and mem0 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 Dify (161,357 stars) and mem0 (69,113 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: Dify is open source, mem0 is open source.
Dify is ahead on every scored dimension that is not level. Level dimensions: recent activity, issue health, license flexibility, self-hosting. The widest gap is fork community at 11 points (100 vs 89), and the tightest is self-hosting at 0 points (100 vs 100).
Dify finishes ahead at 97.9 against mem0 at 93.9, a 4.0 point narrow margin under the published weights.
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 | Dify | mem0 |
|---|---|---|
| GitHub stars | 161,357 | 69,113 |
| Forks | 25,515 | 8,226 |
| Open issues | 1,422 | 963 |
| Adoption | 100 | 93 |
| Activity | 100 | 100 |
| Community | 100 | 89 |
| Issue health | 84 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 97.9 | 93.9 |
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.
The Memory Layer for AI Agents - Drop-in memory infrastructure for AI agents and apps. Context that persists. Built for production.
Dify has more GitHub stars: 161,357 versus 69,113 for mem0. The gap is 92,244 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both Dify and mem0 as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. mem0 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.
Dify scores 97.9 and mem0 scores 93.9. This page calls that a narrow lead for Dify.