A · level
hyperframes
98.3
85,709 stars · Apache-2.0
AI Agents
Too close to call · 98.3 to 97.9
A · level
98.3
85,709 stars · Apache-2.0
B · level
97.9
94,309 stars · Apache-2.0
hyperframes versus ragflow is a AI Agents comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. hyperframes is written mainly in TypeScript; ragflow is written mainly in Go. The composite score is 98.3 for hyperframes and 97.9 for ragflow.
ragflow has 94,309 GitHub stars to hyperframes's 85,709, a gap of 8,600 (1.10×). Forks are 7,946 for hyperframes and 11,335 for ragflow. On the log scale used inside this pair, adoption is 99 versus 100, and the fork community is 96 versus 100.
Push history: hyperframes 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 293 for hyperframes (0.003 per star) and 1,317 for ragflow (0.014 per star). Issue-health scores are 96 and 84; activity scores are 100 and 100.
Both hyperframes and ragflow are listed as Apache-2.0. 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. The license score is therefore level at 96 versus 96, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.
In AI Agents, both hyperframes (85,709 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: hyperframes is open source, ragflow is open source.
The lead is split. hyperframes is furthest ahead on issue health (96 to 84), while ragflow is furthest ahead on fork community (100 to 96). Choose the dimension a rollout cannot compromise on.
Composite score: hyperframes 98.3, ragflow 97.9. The margin is under one point, so this page calls a tie. Use the dimension breakdown rather than the headline number.
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 | hyperframes | ragflow |
|---|---|---|
| GitHub stars | 85,709 | 94,309 |
| Forks | 7,946 | 11,335 |
| Open issues | 293 | 1,317 |
| Adoption | 99 | 100 |
| Activity | 100 | 100 |
| Community | 96 | 100 |
| Issue health | 96 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 98.3 | 97.9 |
Write HTML. Render video. Built for agents.
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 85,709 for hyperframes. The gap is 8,600 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both hyperframes and ragflow as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. 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.
Neither tool clears a one-point margin. hyperframes scores 98.3 and ragflow scores 97.9.