A
Flowise
77.1
55,573 stars · Apache-2.0
AI Agents
graphify leads by 20.1 · decisive
A
77.1
55,573 stars · Apache-2.0
B · leads
97.2
149,362 stars · Apache-2.0
Flowise versus graphify 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; graphify is written mainly in Python. The composite score is 77.1 for Flowise and 97.2 for graphify.
graphify has 149,362 GitHub stars to Flowise's 55,573, a gap of 93,789 (2.69×). Forks are 25,096 for Flowise and 14,362 for graphify. On the log scale used inside this pair, adoption is 92 versus 100, and the fork community is 100 versus 94.
Push history: Flowise was last pushed on 13 August 2026 (96 days ago), and graphify was last pushed on 16 November 2026 (1 day ago). Open issues stand at 1,033 for Flowise (0.019 per star) and 1,670 for graphify (0.011 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 graphify 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 graphify (149,362 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, graphify is open source.
The lead is split. Flowise is furthest ahead on fork community (100 to 94), while graphify is furthest ahead on recent activity (100 to 18). Choose the dimension a rollout cannot compromise on.
graphify finishes ahead at 97.2 against Flowise at 77.1, a 20.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 | Flowise | graphify |
|---|---|---|
| GitHub stars | 55,573 | 149,362 |
| Forks | 25,096 | 14,362 |
| Open issues | 1,033 | 1,670 |
| Adoption | 92 | 100 |
| Activity | 18 | 100 |
| Community | 100 | 94 |
| Issue health | 84 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 77.1 | 97.2 |
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.
Turn any codebase, with its docs, SQL schemas, configs, and PDFs, into a queryable knowledge graph. A /graphify skill for Claude Code, Cursor, Codex, and Gemini CLI: local deterministic AST parsing, every edge explained, no vector store.
graphify has more GitHub stars: 149,362 versus 55,573 for Flowise. The gap is 93,789 stars.
graphify was pushed more recently: 16 November 2026 versus 13 August 2026 for Flowise. That is 95 days apart.
Yes. This catalog marks both Flowise and graphify 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. graphify 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.
graphify scores 97.2 and Flowise scores 77.1. This page calls that a decisive lead for graphify.