A
mem0
96.5
69,113 stars · Apache-2.0
AI Agents
ragflow leads by 1.4 · narrow
A
96.5
69,113 stars · Apache-2.0
B · leads
97.9
94,309 stars · Apache-2.0
mem0 versus ragflow is a AI Agents comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. mem0 is written mainly in Python; ragflow is written mainly in Go. The composite score is 96.5 for mem0 and 97.9 for ragflow.
ragflow has 94,309 GitHub stars to mem0's 69,113, a gap of 25,196 (1.36×). Forks are 8,226 for mem0 and 11,335 for ragflow. On the log scale used inside this pair, adoption is 97 versus 100, and the fork community is 97 versus 100.
Push history: mem0 was last pushed on 17 November 2026 (0 days ago), and ragflow was last pushed on 17 November 2026 (0 days ago). Open issues stand at 963 for mem0 (0.014 per star) and 1,317 for ragflow (0.014 per star). Issue-health scores are 84 and 84; activity scores are 100 and 100.
Both mem0 and ragflow 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 mem0 (69,113 stars) and ragflow (94,309 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: mem0 is open source, ragflow is open source.
ragflow 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 3 points (97 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).
ragflow finishes ahead at 97.9 against mem0 at 96.5, a 1.4 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 | mem0 | ragflow |
|---|---|---|
| GitHub stars | 69,113 | 94,309 |
| Forks | 8,226 | 11,335 |
| Open issues | 963 | 1,317 |
| Adoption | 97 | 100 |
| Activity | 100 | 100 |
| Community | 97 | 100 |
| Issue health | 84 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 96.5 | 97.9 |
The Memory Layer for AI Agents - Drop-in memory infrastructure for AI agents and apps. Context that persists. Built for production.
RAGFlow is an agent-native database: a Retrieval-Augmented Generation (RAG) engine that grew into context infrastructure.
ragflow has more GitHub stars: 94,309 versus 69,113 for mem0. The gap is 25,196 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both mem0 and ragflow as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. ragflow 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.
ragflow scores 97.9 and mem0 scores 96.5. This page calls that a narrow lead for ragflow.