A · level
mem0
97.2
69,113 stars · Apache-2.0
AI Agents
Too close to call · 97.2 to 97.9
A · level
97.2
69,113 stars · Apache-2.0
B · level
97.9
81,931 stars · MIT
mem0 versus ruflo 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; ruflo is written mainly in TypeScript. The composite score is 97.2 for mem0 and 97.9 for ruflo.
ruflo has 81,931 GitHub stars to mem0's 69,113, a gap of 12,818 (1.19×). Forks are 8,226 for mem0 and 9,668 for ruflo. On the log scale used inside this pair, adoption is 98 versus 100, and the fork community is 98 versus 100.
Push history: mem0 was last pushed on 17 November 2026 (0 days ago), and ruflo was last pushed on 17 November 2026 (0 days ago). Open issues stand at 963 for mem0 (0.014 per star) and 614 for ruflo (0.007 per star). Issue-health scores are 84 and 84; activity scores are 100 and 100.
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. ruflo 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. License scores in this pair are 96 for mem0 and 96 for ruflo. This is a procurement signal, not legal advice.
In AI Agents, both mem0 (69,113 stars) and ruflo (81,931 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, ruflo is open source.
ruflo 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 2 points (98 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).
Composite score: mem0 97.2, ruflo 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 | mem0 | ruflo |
|---|---|---|
| GitHub stars | 69,113 | 81,931 |
| Forks | 8,226 | 9,668 |
| Open issues | 963 | 614 |
| Adoption | 98 | 100 |
| Activity | 100 | 100 |
| Community | 98 | 100 |
| Issue health | 84 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 97.2 | 97.9 |
The Memory Layer for AI Agents - Drop-in memory infrastructure for AI agents and apps. Context that persists. Built for production.
🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, federation, vector RAG integration, and native Claude Code / Codex / Hermes and many more Integrated
ruflo has more GitHub stars: 81,931 versus 69,113 for mem0. The gap is 12,818 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both mem0 and ruflo 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. ruflo 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Neither tool clears a one-point margin. mem0 scores 97.2 and ruflo scores 97.9.