A · leads
Dify
97.9
161,357 stars · Apache-2.0
AI Agents
Dify leads by 2.6 · narrow
A · leads
97.9
161,357 stars · Apache-2.0
B
95.3
94,309 stars · Apache-2.0
Dify versus ragflow is a AI Agents comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Dify is written mainly in Python; ragflow is written mainly in Go. The composite score is 97.9 for Dify and 95.3 for ragflow.
Dify has 161,357 GitHub stars to ragflow's 94,309, a gap of 67,048 (1.71×). Forks are 25,515 for Dify and 11,335 for ragflow. On the log scale used inside this pair, adoption is 100 versus 96, and the fork community is 100 versus 92.
Push history: Dify 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,422 for Dify (0.009 per star) and 1,317 for ragflow (0.014 per star). Issue-health scores are 84 and 84; activity scores are 100 and 100.
Both Dify 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 Dify (161,357 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: Dify is open source, ragflow is open source.
Dify is ahead on every scored dimension that is not level. Level dimensions: recent activity, issue health, license flexibility, self-hosting. The widest gap is fork community at 8 points (100 vs 92), and the tightest is self-hosting at 0 points (100 vs 100).
Dify finishes ahead at 97.9 against ragflow at 95.3, a 2.6 point narrow 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 | Dify | ragflow |
|---|---|---|
| GitHub stars | 161,357 | 94,309 |
| Forks | 25,515 | 11,335 |
| Open issues | 1,422 | 1,317 |
| Adoption | 100 | 96 |
| Activity | 100 | 100 |
| Community | 100 | 92 |
| Issue health | 84 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 97.9 | 95.3 |
Dify is a platform for building LLM apps: prompts, RAG pipelines, agents, and observability. It is aimed at teams that want that stack on their own machines.
RAGFlow is an agent-native database: a Retrieval-Augmented Generation (RAG) engine that grew into context infrastructure.
Dify has more GitHub stars: 161,357 versus 94,309 for ragflow. The gap is 67,048 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both Dify and ragflow as self-hostable. Confirm each project's deploy docs before you plan a migration.
Dify 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.
Dify scores 97.9 and ragflow scores 95.3. This page calls that a narrow lead for Dify.