A
cherry-studio
82.0
53,594 stars · AGPL-3.0
AI Agents
hermes-agent leads by 10.9 · clear
A
82.0
53,594 stars · AGPL-3.0
B · leads
92.9
264,096 stars · MIT
cherry-studio versus hermes-agent 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; hermes-agent is written mainly in Python. The composite score is 82.0 for cherry-studio and 92.9 for hermes-agent.
hermes-agent has 264,096 GitHub stars to cherry-studio's 53,594, a gap of 210,502 (4.93×). Forks are 5,231 for cherry-studio and 59,569 for hermes-agent. On the log scale used inside this pair, adoption is 87 versus 100, and the fork community is 78 versus 100.
Push history: cherry-studio was last pushed on 17 November 2026 (0 days ago), and hermes-agent was last pushed on 17 November 2026 (0 days ago). Open issues stand at 2,788 for cherry-studio (0.052 per star) and 53,403 for hermes-agent (0.202 per star). Issue-health scores are 52 and 34; 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. hermes-agent 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 hermes-agent. This is a procurement signal, not legal advice.
In AI Agents, both cherry-studio (53,594 stars) and hermes-agent (264,096 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, hermes-agent is open source.
The lead is split. cherry-studio is furthest ahead on issue health (52 to 34), while hermes-agent is furthest ahead on license flexibility (96 to 52). Choose the dimension a rollout cannot compromise on.
hermes-agent finishes ahead at 92.9 against cherry-studio at 82.0, a 10.9 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 | cherry-studio | hermes-agent |
|---|---|---|
| GitHub stars | 53,594 | 264,096 |
| Forks | 5,231 | 59,569 |
| Open issues | 2,788 | 53,403 |
| Adoption | 87 | 100 |
| Activity | 100 | 100 |
| Community | 78 | 100 |
| Issue health | 52 | 34 |
| License | 52 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 82.0 | 92.9 |
Your AI workspace for models, agents, and productivity.
The agent that grows with you
hermes-agent has more GitHub stars: 264,096 versus 53,594 for cherry-studio. The gap is 210,502 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both cherry-studio and hermes-agent 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. hermes-agent 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.
hermes-agent scores 92.9 and cherry-studio scores 82.0. This page calls that a clear lead for hermes-agent.