A
cherry-studio
87.2
53,594 stars · AGPL-3.0
AI Agents
ruflo leads by 10.7 · clear
A
87.2
53,594 stars · AGPL-3.0
B · leads
97.9
81,931 stars · MIT
cherry-studio versus ruflo is a AI Agents comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Both projects are written mainly in TypeScript. The composite score is 87.2 for cherry-studio and 97.9 for ruflo.
ruflo has 81,931 GitHub stars to cherry-studio's 53,594, a gap of 28,337 (1.53×). Forks are 5,231 for cherry-studio and 9,668 for ruflo. On the log scale used inside this pair, adoption is 96 versus 100, and the fork community is 93 versus 100.
Push history: cherry-studio was last pushed on 17 November 2026 (0 days ago), and ruflo was last pushed on 17 November 2026 (0 days ago). Open issues stand at 2,788 for cherry-studio (0.052 per star) and 614 for ruflo (0.007 per star). Issue-health scores are 52 and 84; 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. ruflo 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 ruflo. This is a procurement signal, not legal advice.
In AI Agents, both cherry-studio (53,594 stars) and ruflo (81,931 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, ruflo is open source.
ruflo is ahead on every scored dimension that is not level. Level dimensions: recent activity, self-hosting. The widest gap is license flexibility at 44 points (52 vs 96), and the tightest is self-hosting at 0 points (100 vs 100).
ruflo finishes ahead at 97.9 against cherry-studio at 87.2, a 10.7 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 | ruflo |
|---|---|---|
| GitHub stars | 53,594 | 81,931 |
| Forks | 5,231 | 9,668 |
| Open issues | 2,788 | 614 |
| Adoption | 96 | 100 |
| Activity | 100 | 100 |
| Community | 93 | 100 |
| Issue health | 52 | 84 |
| License | 52 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 87.2 | 97.9 |
Your AI workspace for models, agents, and productivity.
🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, federation, vector RAG integration, and native Claude Code / Codex / Hermes and many more Integrated
ruflo has more GitHub stars: 81,931 versus 53,594 for cherry-studio. The gap is 28,337 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both cherry-studio and ruflo 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. ruflo 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.
ruflo scores 97.9 and cherry-studio scores 87.2. This page calls that a clear lead for ruflo.