A
cherry-studio
84.3
53,594 stars · AGPL-3.0
AI Agents
Open WebUI leads by 14.8 · clear
A
84.3
53,594 stars · AGPL-3.0
B · leads
99.1
158,922 stars · MIT
cherry-studio versus Open WebUI 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; Open WebUI is written mainly in Svelte. The composite score is 84.3 for cherry-studio and 99.1 for Open WebUI.
Open WebUI has 158,922 GitHub stars to cherry-studio's 53,594, a gap of 105,328 (2.97×). Forks are 5,231 for cherry-studio and 23,097 for Open WebUI. On the log scale used inside this pair, adoption is 91 versus 100, and the fork community is 85 versus 100.
Push history: cherry-studio was last pushed on 17 November 2026 (0 days ago), and Open WebUI was last pushed on 17 November 2026 (0 days ago). Open issues stand at 2,788 for cherry-studio (0.052 per star) and 208 for Open WebUI (0.001 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. Open WebUI 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 Open WebUI. This is a procurement signal, not legal advice.
In AI Agents, both cherry-studio (53,594 stars) and Open WebUI (158,922 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, Open WebUI is open source.
Open WebUI 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).
Open WebUI finishes ahead at 99.1 against cherry-studio at 84.3, a 14.8 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 | Open WebUI |
|---|---|---|
| GitHub stars | 53,594 | 158,922 |
| Forks | 5,231 | 23,097 |
| Open issues | 2,788 | 208 |
| Adoption | 91 | 100 |
| Activity | 100 | 100 |
| Community | 85 | 100 |
| Issue health | 52 | 96 |
| License | 52 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 84.3 | 99.1 |
Your AI workspace for models, agents, and productivity.
Open WebUI is a self-hosted chat interface for local and remote language models, including Ollama. It adds users, documents, and tools around the model endpoint.
Open WebUI has more GitHub stars: 158,922 versus 53,594 for cherry-studio. The gap is 105,328 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both cherry-studio and Open WebUI 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. Open WebUI 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.
Open WebUI scores 99.1 and cherry-studio scores 84.3. This page calls that a clear lead for Open WebUI.