A · leads
deer-flow
97.9
85,441 stars · MIT
AI Agents
deer-flow leads by 1.2 · narrow
A · leads
97.9
85,441 stars · MIT
B
96.7
69,113 stars · Apache-2.0
deer-flow 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 deer-flow and 96.7 for mem0.
deer-flow has 85,441 GitHub stars to mem0's 69,113, a gap of 16,328 (1.24×). Forks are 12,046 for deer-flow and 8,226 for mem0. On the log scale used inside this pair, adoption is 100 versus 98, and the fork community is 100 versus 96.
Push history: deer-flow 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,117 for deer-flow (0.013 per star) and 963 for mem0 (0.014 per star). Issue-health scores are 84 and 84; activity scores are 100 and 100.
deer-flow is listed as MIT, 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. License scores in this pair are 96 for deer-flow and 96 for mem0. This is a procurement signal, not legal advice.
In AI Agents, both deer-flow (85,441 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: deer-flow is open source, mem0 is open source.
deer-flow 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 4 points (100 vs 96), and the tightest is self-hosting at 0 points (100 vs 100).
deer-flow finishes ahead at 97.9 against mem0 at 96.7, a 1.2 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 | deer-flow | mem0 |
|---|---|---|
| GitHub stars | 85,441 | 69,113 |
| Forks | 12,046 | 8,226 |
| Open issues | 1,117 | 963 |
| Adoption | 100 | 98 |
| Activity | 100 | 100 |
| Community | 100 | 96 |
| Issue health | 84 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 97.9 | 96.7 |
An open-source long-horizon SuperAgent harness that researches, codes, and creates. With the help of sandboxes, memories, tools, skill, subagents and message gateway, it handles different levels of tasks that could take minutes to hours.
The Memory Layer for AI Agents - Drop-in memory infrastructure for AI agents and apps. Context that persists. Built for production.
deer-flow has more GitHub stars: 85,441 versus 69,113 for mem0. The gap is 16,328 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both deer-flow and mem0 as self-hostable. Confirm each project's deploy docs before you plan a migration.
deer-flow is listed as MIT, 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.
deer-flow scores 97.9 and mem0 scores 96.7. This page calls that a narrow lead for deer-flow.