A
deer-flow
92.8
85,441 stars · MIT
AI Agents
ECC leads by 6.3 · narrow
A
92.8
85,441 stars · MIT
B · leads
99.1
305,069 stars · MIT
deer-flow versus ECC is a AI Agents comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. deer-flow is written mainly in Python; ECC is written mainly in JavaScript. The composite score is 92.8 for deer-flow and 99.1 for ECC.
ECC has 305,069 GitHub stars to deer-flow's 85,441, a gap of 219,628 (3.57×). Forks are 12,046 for deer-flow and 44,923 for ECC. On the log scale used inside this pair, adoption is 90 versus 100, and the fork community is 88 versus 100.
Push history: deer-flow was last pushed on 17 November 2026 (0 days ago), and ECC was last pushed on 17 November 2026 (0 days ago). Open issues stand at 1,117 for deer-flow (0.013 per star) and 149 for ECC (0.000 per star). Issue-health scores are 84 and 96; activity scores are 100 and 100.
Both deer-flow and ECC are listed as MIT. 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 deer-flow (85,441 stars) and ECC (305,069 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, ECC 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 12 points (88 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).
ECC finishes ahead at 99.1 against deer-flow at 92.8, a 6.3 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 | ECC |
|---|---|---|
| GitHub stars | 85,441 | 305,069 |
| Forks | 12,046 | 44,923 |
| Open issues | 1,117 | 149 |
| Adoption | 90 | 100 |
| Activity | 100 | 100 |
| Community | 88 | 100 |
| Issue health | 84 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 92.8 | 99.1 |
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 agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.
ECC has more GitHub stars: 305,069 versus 85,441 for deer-flow. The gap is 219,628 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both deer-flow and ECC 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. 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
ECC scores 99.1 and deer-flow scores 92.8. This page calls that a narrow lead for ECC.