A · leads
graphify
97.9
149,362 stars · Apache-2.0
AI Agents
graphify leads by 1.7 · narrow
A · leads
97.9
149,362 stars · Apache-2.0
B
96.2
94,309 stars · Apache-2.0
graphify versus ragflow is a AI Agents comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. graphify is written mainly in Python; ragflow is written mainly in Go. The composite score is 97.9 for graphify and 96.2 for ragflow.
graphify has 149,362 GitHub stars to ragflow's 94,309, a gap of 55,053 (1.58×). Forks are 14,362 for graphify and 11,335 for ragflow. On the log scale used inside this pair, adoption is 100 versus 96, and the fork community is 100 versus 98.
Push history: graphify was last pushed on 16 November 2026 (1 day ago), and ragflow was last pushed on 17 November 2026 (0 days ago). Open issues stand at 1,670 for graphify (0.011 per star) and 1,317 for ragflow (0.014 per star). Issue-health scores are 84 and 84; activity scores are 100 and 100.
Both graphify 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 graphify (149,362 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: graphify is open source, ragflow is open source.
graphify is ahead on every scored dimension that is not level. Level dimensions: recent activity, issue health, license flexibility, self-hosting. The widest gap is adoption at 4 points (100 vs 96), and the tightest is self-hosting at 0 points (100 vs 100).
graphify finishes ahead at 97.9 against ragflow at 96.2, a 1.7 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 | graphify | ragflow |
|---|---|---|
| GitHub stars | 149,362 | 94,309 |
| Forks | 14,362 | 11,335 |
| Open issues | 1,670 | 1,317 |
| Adoption | 100 | 96 |
| Activity | 100 | 100 |
| Community | 100 | 98 |
| Issue health | 84 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 97.9 | 96.2 |
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.
RAGFlow is an agent-native database: a Retrieval-Augmented Generation (RAG) engine that grew into context infrastructure.
graphify has more GitHub stars: 149,362 versus 94,309 for ragflow. The gap is 55,053 stars.
ragflow 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 ragflow 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. 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.
graphify scores 97.9 and ragflow scores 96.2. This page calls that a narrow lead for graphify.