A
cherry-studio
86.6
53,594 stars · AGPL-3.0
AI Agents
ragflow leads by 11.3 · clear
A
86.6
53,594 stars · AGPL-3.0
B · leads
97.9
94,309 stars · Apache-2.0
cherry-studio versus ragflow 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; ragflow is written mainly in Go. The composite score is 86.6 for cherry-studio and 97.9 for ragflow.
ragflow has 94,309 GitHub stars to cherry-studio's 53,594, a gap of 40,715 (1.76×). Forks are 5,231 for cherry-studio and 11,335 for ragflow. On the log scale used inside this pair, adoption is 95 versus 100, and the fork community is 92 versus 100.
Push history: cherry-studio was last pushed on 17 November 2026 (0 days ago), and ragflow was last pushed on 17 November 2026 (0 days ago). Open issues stand at 2,788 for cherry-studio (0.052 per star) and 1,317 for ragflow (0.014 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. ragflow 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 52 for cherry-studio and 96 for ragflow. This is a procurement signal, not legal advice.
In AI Agents, both cherry-studio (53,594 stars) and ragflow (94,309 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, ragflow is open source.
ragflow 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).
ragflow finishes ahead at 97.9 against cherry-studio at 86.6, a 11.3 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 | ragflow |
|---|---|---|
| GitHub stars | 53,594 | 94,309 |
| Forks | 5,231 | 11,335 |
| Open issues | 2,788 | 1,317 |
| Adoption | 95 | 100 |
| Activity | 100 | 100 |
| Community | 92 | 100 |
| Issue health | 52 | 84 |
| License | 52 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 86.6 | 97.9 |
Your AI workspace for models, agents, and productivity.
RAGFlow is an agent-native database: a Retrieval-Augmented Generation (RAG) engine that grew into context infrastructure.
ragflow has more GitHub stars: 94,309 versus 53,594 for cherry-studio. The gap is 40,715 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both cherry-studio and ragflow 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. ragflow 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.
ragflow scores 97.9 and cherry-studio scores 86.6. This page calls that a clear lead for ragflow.