A · leads
ECC
99.1
305,069 stars · MIT
AI Agents
ECC leads by 15.2 · decisive
A · leads
99.1
305,069 stars · MIT
B
83.9
25,471 stars · Apache-2.0
ECC versus letta 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; letta is written mainly in an unspecified language. The composite score is 99.1 for ECC and 83.9 for letta.
ECC has 305,069 GitHub stars to letta's 25,471, a gap of 279,598 (11.98×). Forks are 44,923 for ECC and 2,677 for letta. On the log scale used inside this pair, adoption is 100 versus 80, and the fork community is 100 versus 74.
Push history: ECC was last pushed on 17 November 2026 (0 days ago), and letta was last pushed on 18 October 2026 (29 days ago). Open issues stand at 149 for ECC (0.000 per star) and 0 for letta (0.000 per star). Issue-health scores are 96 and 96; activity scores are 100 and 78.
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. letta 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 letta. This is a procurement signal, not legal advice.
In AI Agents, both ECC (305,069 stars) and letta (25,471 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, letta is open source.
ECC is ahead on every scored dimension that is not level. Level dimensions: issue health, license flexibility, self-hosting. The widest gap is fork community at 26 points (100 vs 74), and the tightest is self-hosting at 0 points (100 vs 100).
ECC finishes ahead at 99.1 against letta at 83.9, a 15.2 point decisive 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 | letta |
|---|---|---|
| GitHub stars | 305,069 | 25,471 |
| Forks | 44,923 | 2,677 |
| Open issues | 149 | 0 |
| Adoption | 100 | 80 |
| Activity | 100 | 78 |
| Community | 100 | 74 |
| Issue health | 96 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 99.1 | 83.9 |
The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.
Platform for stateful agents: AI with advanced memory that can learn and self-improve over time.
ECC has more GitHub stars: 305,069 versus 25,471 for letta. The gap is 279,598 stars.
ECC was pushed more recently: 17 November 2026 versus 18 October 2026 for letta. That is 29 days apart.
Yes. This catalog marks both ECC and letta 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. letta 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 letta scores 83.9. This page calls that a decisive lead for ECC.