A · level
graphify
97.8
149,362 stars · Apache-2.0
AI Agents
Too close to call · 97.8 to 97.5
A · level
97.8
149,362 stars · Apache-2.0
B · level
97.5
156,720 stars · MIT
graphify versus Langflow is a AI Agents comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Both projects are written mainly in Python. The composite score is 97.8 for graphify and 97.5 for Langflow.
Langflow has 156,720 GitHub stars to graphify's 149,362, a gap of 7,358 (1.05×). Forks are 14,362 for graphify and 10,426 for Langflow. On the log scale used inside this pair, adoption is 100 versus 100, and the fork community is 100 versus 97.
Push history: graphify was last pushed on 16 November 2026 (1 day ago), and Langflow was last pushed on 17 November 2026 (0 days ago). Open issues stand at 1,670 for graphify (0.011 per star) and 1,340 for Langflow (0.009 per star). Issue-health scores are 84 and 84; activity scores are 100 and 100.
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. 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. License scores in this pair are 96 for graphify and 96 for Langflow. This is a procurement signal, not legal advice.
In AI Agents, both graphify (149,362 stars) and Langflow (156,720 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: graphify is open source, Langflow is open source.
The lead is split. graphify is furthest ahead on fork community (100 to 97), while Langflow is furthest ahead on adoption (100 to 100). Choose the dimension a rollout cannot compromise on.
Composite score: graphify 97.8, Langflow 97.5. The margin is under one point, so this page calls a tie. Use the dimension breakdown rather than the headline number.
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 | graphify | Langflow |
|---|---|---|
| GitHub stars | 149,362 | 156,720 |
| Forks | 14,362 | 10,426 |
| Open issues | 1,670 | 1,340 |
| Adoption | 100 | 100 |
| Activity | 100 | 100 |
| Community | 100 | 97 |
| Issue health | 84 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 97.8 | 97.5 |
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.
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.
Langflow has more GitHub stars: 156,720 versus 149,362 for graphify. The gap is 7,358 stars.
Langflow was pushed more recently: 17 November 2026 versus 16 November 2026 for graphify. That is 1 days apart.
Yes. This catalog marks both graphify and Langflow as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Neither tool clears a one-point margin. graphify scores 97.8 and Langflow scores 97.5.