A · leads
ECC
99.1
305,069 stars · MIT
AI Agents
ECC leads by 7.4 · clear
A · leads
99.1
305,069 stars · MIT
B
91.7
69,113 stars · Apache-2.0
ECC versus mem0 is a AI Agents comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. ECC is written mainly in JavaScript; mem0 is written mainly in Python. The composite score is 99.1 for ECC and 91.7 for mem0.
ECC has 305,069 GitHub stars to mem0's 69,113, a gap of 235,956 (4.41×). Forks are 44,923 for ECC and 8,226 for mem0. On the log scale used inside this pair, adoption is 100 versus 88, and the fork community is 100 versus 84.
Push history: ECC 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 149 for ECC (0.000 per star) and 963 for mem0 (0.014 per star). Issue-health scores are 96 and 84; activity scores are 100 and 100.
ECC 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 ECC and 96 for mem0. This is a procurement signal, not legal advice.
In AI Agents, both ECC (305,069 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: ECC is open source, mem0 is open source.
ECC is ahead on every scored dimension that is not level. Level dimensions: recent activity, license flexibility, self-hosting. The widest gap is fork community at 16 points (100 vs 84), and the tightest is self-hosting at 0 points (100 vs 100).
ECC finishes ahead at 99.1 against mem0 at 91.7, a 7.4 point clear 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 | ECC | mem0 |
|---|---|---|
| GitHub stars | 305,069 | 69,113 |
| Forks | 44,923 | 8,226 |
| Open issues | 149 | 963 |
| Adoption | 100 | 88 |
| Activity | 100 | 100 |
| Community | 100 | 84 |
| Issue health | 96 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 99.1 | 91.7 |
The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.
The Memory Layer for AI Agents - Drop-in memory infrastructure for AI agents and apps. Context that persists. Built for production.
ECC has more GitHub stars: 305,069 versus 69,113 for mem0. The gap is 235,956 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both ECC and mem0 as self-hostable. Confirm each project's deploy docs before you plan a migration.
ECC 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.
ECC scores 99.1 and mem0 scores 91.7. This page calls that a clear lead for ECC.