A
agents-towards-production
77.3
21,914 stars · license n/a
AI Agents
Dify leads by 20.6 · decisive
A
77.3
21,914 stars · license n/a
B · leads
97.9
161,357 stars · Apache-2.0
agents-towards-production versus Dify is a AI Agents comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. agents-towards-production is written mainly in Jupyter Notebook; Dify is written mainly in Python. The composite score is 77.3 for agents-towards-production and 97.9 for Dify.
Dify has 161,357 GitHub stars to agents-towards-production's 21,914, a gap of 139,443 (7.36×). Forks are 2,893 for agents-towards-production and 25,515 for Dify. On the log scale used inside this pair, adoption is 83 versus 100, and the fork community is 78 versus 100.
Push history: agents-towards-production was last pushed on 15 November 2026 (2 days ago), and Dify was last pushed on 17 November 2026 (0 days ago). Open issues stand at 5 for agents-towards-production (0.000 per star) and 1,422 for Dify (0.009 per star). Issue-health scores are 96 and 84; activity scores are 100 and 100.
agents-towards-production is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. 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. License scores in this pair are 30 for agents-towards-production and 96 for Dify. This is a procurement signal, not legal advice.
Only Dify is marked self-hostable here (161,357 stars, deploy score 100). agents-towards-production is not (21,914 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: agents-towards-production is unpriced in this catalog, Dify is open source.
The lead is split. agents-towards-production is furthest ahead on issue health (96 to 84), while Dify is furthest ahead on license flexibility (96 to 30). Choose the dimension a rollout cannot compromise on.
Dify finishes ahead at 97.9 against agents-towards-production at 77.3, a 20.6 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 | agents-towards-production | Dify |
|---|---|---|
| GitHub stars | 21,914 | 161,357 |
| Forks | 2,893 | 25,515 |
| Open issues | 5 | 1,422 |
| Adoption | 83 | 100 |
| Activity | 100 | 100 |
| Community | 78 | 100 |
| Issue health | 96 | 84 |
| License | 30 | 96 |
| Self-hosting | 35 | 100 |
| Composite | 77.3 | 97.9 |
End-to-end, code-first tutorials for building production-grade GenAI agents. From prototype to enterprise deployment.
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 21,914 for agents-towards-production. The gap is 139,443 stars.
Dify was pushed more recently: 17 November 2026 versus 15 November 2026 for agents-towards-production. That is 2 days apart.
Only Dify is marked self-hostable. agents-towards-production is not.
agents-towards-production is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. 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 agents-towards-production scores 77.3. This page calls that a decisive lead for Dify.