A · level
deer-flow
97.6
85,441 stars · MIT
AI Agents
Too close to call · 97.6 to 97.8
A · level
97.6
85,441 stars · MIT
B · level
97.8
94,309 stars · Apache-2.0
deer-flow versus ragflow is a AI Agents comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. deer-flow is written mainly in Python; ragflow is written mainly in Go. The composite score is 97.6 for deer-flow and 97.8 for ragflow.
ragflow has 94,309 GitHub stars to deer-flow's 85,441, a gap of 8,868 (1.10×). Forks are 12,046 for deer-flow and 11,335 for ragflow. On the log scale used inside this pair, adoption is 99 versus 100, and the fork community is 100 versus 99.
Push history: deer-flow 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 1,117 for deer-flow (0.013 per star) and 1,317 for ragflow (0.014 per star). Issue-health scores are 84 and 84; activity scores are 100 and 100.
deer-flow 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. 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. License scores in this pair are 96 for deer-flow and 96 for ragflow. This is a procurement signal, not legal advice.
In AI Agents, both deer-flow (85,441 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: deer-flow is open source, ragflow is open source.
The lead is split. deer-flow is furthest ahead on fork community (100 to 99), while ragflow is furthest ahead on adoption (100 to 99). Choose the dimension a rollout cannot compromise on.
Composite score: deer-flow 97.6, ragflow 97.8. 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 | deer-flow | ragflow |
|---|---|---|
| GitHub stars | 85,441 | 94,309 |
| Forks | 12,046 | 11,335 |
| Open issues | 1,117 | 1,317 |
| Adoption | 99 | 100 |
| Activity | 100 | 100 |
| Community | 100 | 99 |
| Issue health | 84 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 97.6 | 97.8 |
An open-source long-horizon SuperAgent harness that researches, codes, and creates. With the help of sandboxes, memories, tools, skill, subagents and message gateway, it handles different levels of tasks that could take minutes to hours.
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,441 for deer-flow. The gap is 8,868 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both deer-flow and ragflow as self-hostable. Confirm each project's deploy docs before you plan a migration.
deer-flow 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. 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. deer-flow scores 97.6 and ragflow scores 97.8.