A
Flowise
78.3
55,573 stars · Apache-2.0
AI Agents
ragflow leads by 18.5 · decisive
A
78.3
55,573 stars · Apache-2.0
B · leads
96.8
94,309 stars · Apache-2.0
Flowise versus ragflow is a AI Agents comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Flowise is written mainly in TypeScript; ragflow is written mainly in Go. The composite score is 78.3 for Flowise and 96.8 for ragflow.
ragflow has 94,309 GitHub stars to Flowise's 55,573, a gap of 38,736 (1.70×). Forks are 25,096 for Flowise and 11,335 for ragflow. On the log scale used inside this pair, adoption is 95 versus 100, and the fork community is 100 versus 92.
Push history: Flowise was last pushed on 13 August 2026 (96 days ago), and ragflow was last pushed on 17 November 2026 (0 days ago). Open issues stand at 1,033 for Flowise (0.019 per star) and 1,317 for ragflow (0.014 per star). Issue-health scores are 84 and 84; activity scores are 18 and 100. Flowise is archived on GitHub, so its activity score is capped.
Both Flowise 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 Flowise (55,573 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: Flowise is open source, ragflow is open source.
The lead is split. Flowise is furthest ahead on fork community (100 to 92), while ragflow is furthest ahead on recent activity (100 to 18). Choose the dimension a rollout cannot compromise on.
ragflow finishes ahead at 96.8 against Flowise at 78.3, a 18.5 point decisive 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 | Flowise | ragflow |
|---|---|---|
| GitHub stars | 55,573 | 94,309 |
| Forks | 25,096 | 11,335 |
| Open issues | 1,033 | 1,317 |
| Adoption | 95 | 100 |
| Activity | 18 | 100 |
| Community | 100 | 92 |
| Issue health | 84 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 78.3 | 96.8 |
Flowise is a visual builder for LLM chains and agents on top of libraries such as LangChain. You design a flow in the browser and run it from a self-hosted Node service.
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 55,573 for Flowise. The gap is 38,736 stars.
ragflow was pushed more recently: 17 November 2026 versus 13 August 2026 for Flowise. That is 96 days apart.
Yes. This catalog marks both Flowise and ragflow as self-hostable. Confirm each project's deploy docs before you plan a migration.
Flowise 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.
ragflow scores 96.8 and Flowise scores 78.3. This page calls that a decisive lead for ragflow.