A · leads
Langflow
97.8
156,720 stars · MIT
AI Agents
Langflow leads by 1.3 · narrow
A · leads
97.8
156,720 stars · MIT
B
96.5
94,309 stars · Apache-2.0
Langflow versus ragflow is a AI Agents comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Langflow is written mainly in Python; ragflow is written mainly in Go. The composite score is 97.8 for Langflow and 96.5 for ragflow.
Langflow has 156,720 GitHub stars to ragflow's 94,309, a gap of 62,411 (1.66×). Forks are 10,426 for Langflow and 11,335 for ragflow. On the log scale used inside this pair, adoption is 100 versus 96, and the fork community is 99 versus 100.
Push history: Langflow 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,340 for Langflow (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.
Langflow 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 Langflow and 96 for ragflow. This is a procurement signal, not legal advice.
In AI Agents, both Langflow (156,720 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: Langflow is open source, ragflow is open source.
The lead is split. Langflow is furthest ahead on adoption (100 to 96), while ragflow is furthest ahead on fork community (100 to 99). Choose the dimension a rollout cannot compromise on.
Langflow finishes ahead at 97.8 against ragflow at 96.5, a 1.3 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 | Langflow | ragflow |
|---|---|---|
| GitHub stars | 156,720 | 94,309 |
| Forks | 10,426 | 11,335 |
| Open issues | 1,340 | 1,317 |
| Adoption | 100 | 96 |
| Activity | 100 | 100 |
| Community | 99 | 100 |
| Issue health | 84 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 97.8 | 96.5 |
Langflow is a visual environment for composing language-model flows and agents. It exports the graph as code and is used to prototype retrieval and tool-using apps.
RAGFlow is an agent-native database: a Retrieval-Augmented Generation (RAG) engine that grew into context infrastructure.
Langflow has more GitHub stars: 156,720 versus 94,309 for ragflow. The gap is 62,411 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both Langflow and ragflow as self-hostable. Confirm each project's deploy docs before you plan a migration.
Langflow 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.
Langflow scores 97.8 and ragflow scores 96.5. This page calls that a narrow lead for Langflow.