A
cherry-studio
86.5
53,594 stars · AGPL-3.0
AI Agents
OmniRoute leads by 11.4 · clear
A
86.5
53,594 stars · AGPL-3.0
B · leads
97.9
88,282 stars · MIT
cherry-studio versus OmniRoute 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 86.5 for cherry-studio and 97.9 for OmniRoute.
OmniRoute has 88,282 GitHub stars to cherry-studio's 53,594, a gap of 34,688 (1.65×). Forks are 5,231 for cherry-studio and 13,565 for OmniRoute. On the log scale used inside this pair, adoption is 96 versus 100, and the fork community is 90 versus 100.
Push history: cherry-studio was last pushed on 17 November 2026 (0 days ago), and OmniRoute was last pushed on 17 November 2026 (0 days ago). Open issues stand at 2,788 for cherry-studio (0.052 per star) and 673 for OmniRoute (0.008 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. OmniRoute 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 OmniRoute. This is a procurement signal, not legal advice.
In AI Agents, both cherry-studio (53,594 stars) and OmniRoute (88,282 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, OmniRoute is open source.
OmniRoute 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).
OmniRoute finishes ahead at 97.9 against cherry-studio at 86.5, a 11.4 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 | OmniRoute |
|---|---|---|
| GitHub stars | 53,594 | 88,282 |
| Forks | 5,231 | 13,565 |
| Open issues | 2,788 | 673 |
| Adoption | 96 | 100 |
| Activity | 100 | 100 |
| Community | 90 | 100 |
| Issue health | 52 | 84 |
| License | 52 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 86.5 | 97.9 |
Your AI workspace for models, agents, and productivity.
Never stop coding. Free MIT AI gateway: one endpoint, 375 providers (150+ free), 1,400+ models Kimi, Claude, GPT, Gemini, GLM, DeepSeek, MiniMax. Works with Claude Code, Codex, Cursor, OpenCode, Cline & Copilot. Quota-aware auto-fallback, RTK+Caveman compression saves 15-95% tokens, MCP/A2A, Desktop/PWA. Built by 900+ contributors
OmniRoute has more GitHub stars: 88,282 versus 53,594 for cherry-studio. The gap is 34,688 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both cherry-studio and OmniRoute 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. OmniRoute 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.
OmniRoute scores 97.9 and cherry-studio scores 86.5. This page calls that a clear lead for OmniRoute.