A · leads
Dify
97.9
161,357 stars · Apache-2.0
AI Agents
Dify leads by 21.1 · decisive
A · leads
97.9
161,357 stars · Apache-2.0
B
76.8
55,573 stars · Apache-2.0
Dify versus Flowise 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; Flowise is written mainly in TypeScript. The composite score is 97.9 for Dify and 76.8 for Flowise.
Dify has 161,357 GitHub stars to Flowise's 55,573, a gap of 105,784 (2.90×). Forks are 25,515 for Dify and 25,096 for Flowise. On the log scale used inside this pair, adoption is 100 versus 91, and the fork community is 100 versus 100.
Push history: Dify was last pushed on 17 November 2026 (0 days ago), and Flowise was last pushed on 13 August 2026 (96 days ago). Open issues stand at 1,422 for Dify (0.009 per star) and 1,033 for Flowise (0.019 per star). Issue-health scores are 84 and 84; activity scores are 100 and 18. Flowise is archived on GitHub, so its activity score is capped.
Both Dify and Flowise 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 Flowise (55,573 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, Flowise is open source.
Dify is ahead on every scored dimension that is not level. Level dimensions: issue health, license flexibility, self-hosting. The widest gap is recent activity at 82 points (100 vs 18), and the tightest is self-hosting at 0 points (100 vs 100).
Dify finishes ahead at 97.9 against Flowise at 76.8, a 21.1 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 | Dify | Flowise |
|---|---|---|
| GitHub stars | 161,357 | 55,573 |
| Forks | 25,515 | 25,096 |
| Open issues | 1,422 | 1,033 |
| Adoption | 100 | 91 |
| Activity | 100 | 18 |
| Community | 100 | 100 |
| Issue health | 84 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 97.9 | 76.8 |
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.
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.
Dify has more GitHub stars: 161,357 versus 55,573 for Flowise. The gap is 105,784 stars.
Dify was pushed more recently: 17 November 2026 versus 13 August 2026 for Flowise. That is 96 days apart.
Yes. This catalog marks both Dify and Flowise 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. 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Dify scores 97.9 and Flowise scores 76.8. This page calls that a decisive lead for Dify.