Skip to content
DevUtils Online

AI Agents

cherry-studio vs hyperframes

hyperframes leads by 11.7 · clear

B · leads

hyperframes

99.1

85,709 stars · Apache-2.0

cherry-studio versus hyperframes 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.4 for cherry-studio and 99.1 for hyperframes.

hyperframes has 85,709 GitHub stars to cherry-studio's 53,594, a gap of 32,115 (1.60×). Forks are 5,231 for cherry-studio and 7,946 for hyperframes. On the log scale used inside this pair, adoption is 96 versus 100, and the fork community is 95 versus 100.

Push history: cherry-studio was last pushed on 17 November 2026 (0 days ago), and hyperframes was last pushed on 17 November 2026 (0 days ago). Open issues stand at 2,788 for cherry-studio (0.052 per star) and 293 for hyperframes (0.003 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. hyperframes 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 hyperframes. This is a procurement signal, not legal advice.

In AI Agents, both cherry-studio (53,594 stars) and hyperframes (85,709 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, hyperframes is open source.

hyperframes 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).

hyperframes finishes ahead at 99.1 against cherry-studio at 87.4, a 11.7 point clear margin under the published weights.

Scores are computed inside this pair only. Method and weights.

Where they separate

The numbers

Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.

cherry-studio versus hyperframes metrics
Signal cherry-studio hyperframes
GitHub stars 53,594 85,709
Forks 5,231 7,946
Open issues 2,788 293
Adoption 96 100
Activity 100 100
Community 95 100
Issue health 52 96
License 52 96
Self-hosting 100 100
Composite 87.4 99.1

Questions this page answers

Which has more GitHub stars, cherry-studio or hyperframes?

hyperframes has more GitHub stars: 85,709 versus 53,594 for cherry-studio. The gap is 32,115 stars.

Which was updated more recently, cherry-studio or hyperframes?

Both were last pushed on 17 November 2026.

Can I self-host both cherry-studio and hyperframes?

Yes. This catalog marks both cherry-studio and hyperframes as self-hostable. Confirm each project's deploy docs before you plan a migration.

Which license is easier to embed in a commercial product, cherry-studio or hyperframes?

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. hyperframes 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.

Who wins the cherry-studio vs hyperframes score?

hyperframes scores 99.1 and cherry-studio scores 87.4. This page calls that a clear lead for hyperframes.

Related comparisons