A · leads
cherry-studio
87.2
53,594 stars · AGPL-3.0
AI Agents
cherry-studio leads by 7.3 · clear
A · leads
87.2
53,594 stars · AGPL-3.0
B
79.9
55,573 stars · Apache-2.0
cherry-studio versus Flowise 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 79.9 for Flowise.
Flowise has 55,573 GitHub stars to cherry-studio's 53,594, a gap of 1,979 (1.04×). Forks are 5,231 for cherry-studio and 25,096 for Flowise. On the log scale used inside this pair, adoption is 100 versus 100, and the fork community is 84 versus 100.
Push history: cherry-studio was last pushed on 17 November 2026 (0 days ago), and Flowise was last pushed on 13 August 2026 (96 days ago). Open issues stand at 2,788 for cherry-studio (0.052 per star) and 1,033 for Flowise (0.019 per star). Issue-health scores are 52 and 84; activity scores are 100 and 18. Flowise is archived on GitHub, so its activity score is capped.
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. Flowise 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 Flowise. This is a procurement signal, not legal advice.
In AI Agents, both cherry-studio (53,594 stars) and Flowise (55,573 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, Flowise is open source.
The lead is split. cherry-studio is furthest ahead on recent activity (100 to 18), while Flowise is furthest ahead on license flexibility (96 to 52). Choose the dimension a rollout cannot compromise on.
cherry-studio finishes ahead at 87.2 against Flowise at 79.9, a 7.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 | Flowise |
|---|---|---|
| GitHub stars | 53,594 | 55,573 |
| Forks | 5,231 | 25,096 |
| Open issues | 2,788 | 1,033 |
| Adoption | 100 | 100 |
| Activity | 100 | 18 |
| Community | 84 | 100 |
| Issue health | 52 | 84 |
| License | 52 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 87.2 | 79.9 |
Your AI workspace for models, agents, and productivity.
Flowise is a visual builder for LLM chains and agents on top of libraries such as LangChain. You design a flow in the browser and run it from a self-hosted Node service.
Flowise has more GitHub stars: 55,573 versus 53,594 for cherry-studio. The gap is 1,979 stars.
cherry-studio was pushed more recently: 17 November 2026 versus 13 August 2026 for Flowise. That is 96 days apart.
Yes. This catalog marks both cherry-studio and Flowise 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. Flowise 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.
cherry-studio scores 87.2 and Flowise scores 79.9. This page calls that a clear lead for cherry-studio.