A · leads
ECC
99.1
305,069 stars · MIT
AI Agents
ECC leads by 14.1 · clear
A · leads
99.1
305,069 stars · MIT
B
85.0
12,716 stars · MIT
ECC versus OpenBot 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; OpenBot is written mainly in TypeScript. The composite score is 99.1 for ECC and 85.0 for OpenBot.
ECC has 305,069 GitHub stars to OpenBot's 12,716, a gap of 292,353 (23.99×). Forks are 44,923 for ECC and 1,578 for OpenBot. On the log scale used inside this pair, adoption is 100 versus 75, and the fork community is 100 versus 69.
Push history: ECC was last pushed on 17 November 2026 (0 days ago), and OpenBot was last pushed on 17 November 2026 (0 days ago). Open issues stand at 149 for ECC (0.000 per star) and 121 for OpenBot (0.010 per star). Issue-health scores are 96 and 84; activity scores are 100 and 100.
Both ECC and OpenBot 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 ECC (305,069 stars) and OpenBot (12,716 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, OpenBot 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 31 points (100 vs 69), and the tightest is self-hosting at 0 points (100 vs 100).
ECC finishes ahead at 99.1 against OpenBot at 85.0, a 14.1 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 | OpenBot |
|---|---|---|
| GitHub stars | 305,069 | 12,716 |
| Forks | 44,923 | 1,578 |
| Open issues | 149 | 121 |
| Adoption | 100 | 75 |
| Activity | 100 | 100 |
| Community | 100 | 69 |
| Issue health | 96 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 99.1 | 85.0 |
The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.
The open, self-hostable alternative to closed AI bots. Production-ready, fully customizable, and plugs into every stack: any agent, any model, any tool.
ECC has more GitHub stars: 305,069 versus 12,716 for OpenBot. The gap is 292,353 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both ECC and OpenBot 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. OpenBot 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 OpenBot scores 85.0. This page calls that a clear lead for ECC.