A
archify
96.8
97,376 stars · Apache-2.0
AI Agents
graphify leads by 1.1 · narrow
A
96.8
97,376 stars · Apache-2.0
B · leads
97.9
149,362 stars · Apache-2.0
archify versus graphify is a AI Agents comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. archify is written mainly in JavaScript; graphify is written mainly in Python. The composite score is 96.8 for archify and 97.9 for graphify.
graphify has 149,362 GitHub stars to archify's 97,376, a gap of 51,986 (1.53×). Forks are 6,647 for archify and 14,362 for graphify. On the log scale used inside this pair, adoption is 96 versus 100, and the fork community is 92 versus 100.
Push history: archify was last pushed on 17 November 2026 (0 days ago), and graphify was last pushed on 16 November 2026 (1 day ago). Open issues stand at 368 for archify (0.004 per star) and 1,670 for graphify (0.011 per star). Issue-health scores are 96 and 84; activity scores are 100 and 100.
Both archify 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 archify (97,376 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: archify is open source, graphify is open source.
The lead is split. archify is furthest ahead on issue health (96 to 84), while graphify is furthest ahead on fork community (100 to 92). Choose the dimension a rollout cannot compromise on.
graphify finishes ahead at 97.9 against archify at 96.8, a 1.1 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 | archify | graphify |
|---|---|---|
| GitHub stars | 97,376 | 149,362 |
| Forks | 6,647 | 14,362 |
| Open issues | 368 | 1,670 |
| Adoption | 96 | 100 |
| Activity | 100 | 100 |
| Community | 92 | 100 |
| Issue health | 96 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 96.8 | 97.9 |
Turn any idea, plan, or codebase into a beautiful interactive diagram. An agent skill for Claude Code, Codex, and more.
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 97,376 for archify. The gap is 51,986 stars.
archify was pushed more recently: 17 November 2026 versus 16 November 2026 for graphify. That is 1 days apart.
Yes. This catalog marks both archify and graphify as self-hostable. Confirm each project's deploy docs before you plan a migration.
archify 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.9 and archify scores 96.8. This page calls that a narrow lead for graphify.