A · leads
ECC
99.1
305,069 stars · MIT
AI Agents
ECC leads by 13.0 · clear
A · leads
99.1
305,069 stars · MIT
B
86.1
23,048 stars · Apache-2.0
ECC versus NemoClaw 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; NemoClaw is written mainly in TypeScript. The composite score is 99.1 for ECC and 86.1 for NemoClaw.
ECC has 305,069 GitHub stars to NemoClaw's 23,048, a gap of 282,021 (13.24×). Forks are 44,923 for ECC and 3,218 for NemoClaw. On the log scale used inside this pair, adoption is 100 versus 80, and the fork community is 100 versus 75.
Push history: ECC was last pushed on 17 November 2026 (0 days ago), and NemoClaw was last pushed on 17 November 2026 (0 days ago). Open issues stand at 149 for ECC (0.000 per star) and 552 for NemoClaw (0.024 per star). Issue-health scores are 96 and 70; 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. NemoClaw 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 NemoClaw. This is a procurement signal, not legal advice.
In AI Agents, both ECC (305,069 stars) and NemoClaw (23,048 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, NemoClaw 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 issue health at 26 points (96 vs 70), and the tightest is self-hosting at 0 points (100 vs 100).
ECC finishes ahead at 99.1 against NemoClaw at 86.1, a 13.0 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 | NemoClaw |
|---|---|---|
| GitHub stars | 305,069 | 23,048 |
| Forks | 44,923 | 3,218 |
| Open issues | 149 | 552 |
| Adoption | 100 | 80 |
| Activity | 100 | 100 |
| Community | 100 | 75 |
| Issue health | 96 | 70 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 99.1 | 86.1 |
The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.
Run agents like Hermes, LangChain Deep Agents, and OpenClaw more securely inside NVIDIA OpenShell with managed inference
ECC has more GitHub stars: 305,069 versus 23,048 for NemoClaw. The gap is 282,021 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both ECC and NemoClaw 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. NemoClaw 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 NemoClaw scores 86.1. This page calls that a clear lead for ECC.