A
archify
95.8
97,376 stars · Apache-2.0
AI Agents
Dify leads by 2.1 · narrow
A
95.8
97,376 stars · Apache-2.0
B · leads
97.9
161,357 stars · Apache-2.0
archify versus Dify 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; Dify is written mainly in Python. The composite score is 95.8 for archify and 97.9 for Dify.
Dify has 161,357 GitHub stars to archify's 97,376, a gap of 63,981 (1.66×). Forks are 6,647 for archify and 25,515 for Dify. On the log scale used inside this pair, adoption is 96 versus 100, and the fork community is 87 versus 100.
Push history: archify was last pushed on 17 November 2026 (0 days ago), and Dify was last pushed on 17 November 2026 (0 days ago). Open issues stand at 368 for archify (0.004 per star) and 1,422 for Dify (0.009 per star). Issue-health scores are 96 and 84; activity scores are 100 and 100.
Both archify and Dify 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 Dify (161,357 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, Dify is open source.
The lead is split. archify is furthest ahead on issue health (96 to 84), while Dify is furthest ahead on fork community (100 to 87). Choose the dimension a rollout cannot compromise on.
Dify finishes ahead at 97.9 against archify at 95.8, a 2.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 | Dify |
|---|---|---|
| GitHub stars | 97,376 | 161,357 |
| Forks | 6,647 | 25,515 |
| Open issues | 368 | 1,422 |
| Adoption | 96 | 100 |
| Activity | 100 | 100 |
| Community | 87 | 100 |
| Issue health | 96 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 95.8 | 97.9 |
Turn any idea, plan, or codebase into a beautiful interactive diagram. An agent skill for Claude Code, Codex, and more.
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.
Dify has more GitHub stars: 161,357 versus 97,376 for archify. The gap is 63,981 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both archify and Dify 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. 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Dify scores 97.9 and archify scores 95.8. This page calls that a narrow lead for Dify.