A
cherry-studio
81.9
53,594 stars · AGPL-3.0
AI Agents
ECC leads by 17.2 · decisive
A
81.9
53,594 stars · AGPL-3.0
B · leads
99.1
305,069 stars · MIT
cherry-studio versus ECC is a AI Agents comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. cherry-studio is written mainly in TypeScript; ECC is written mainly in JavaScript. The composite score is 81.9 for cherry-studio and 99.1 for ECC.
ECC has 305,069 GitHub stars to cherry-studio's 53,594, a gap of 251,475 (5.69×). Forks are 5,231 for cherry-studio and 44,923 for ECC. On the log scale used inside this pair, adoption is 86 versus 100, and the fork community is 80 versus 100.
Push history: cherry-studio 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 2,788 for cherry-studio (0.052 per star) and 149 for ECC (0.000 per star). Issue-health scores are 52 and 96; activity scores are 100 and 100.
cherry-studio is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. 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. License scores in this pair are 52 for cherry-studio and 96 for ECC. This is a procurement signal, not legal advice.
In AI Agents, both cherry-studio (53,594 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: cherry-studio is open source, ECC is open source.
ECC is ahead on every scored dimension that is not level. Level dimensions: recent activity, self-hosting. The widest gap is issue health at 44 points (52 vs 96), and the tightest is self-hosting at 0 points (100 vs 100).
ECC finishes ahead at 99.1 against cherry-studio at 81.9, a 17.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 | cherry-studio | ECC |
|---|---|---|
| GitHub stars | 53,594 | 305,069 |
| Forks | 5,231 | 44,923 |
| Open issues | 2,788 | 149 |
| Adoption | 86 | 100 |
| Activity | 100 | 100 |
| Community | 80 | 100 |
| Issue health | 52 | 96 |
| License | 52 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 81.9 | 99.1 |
Your AI workspace for models, agents, and productivity.
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 53,594 for cherry-studio. The gap is 251,475 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both cherry-studio and ECC as self-hostable. Confirm each project's deploy docs before you plan a migration.
cherry-studio is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. 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 cherry-studio scores 81.9. This page calls that a decisive lead for ECC.