A · leads
Dify
97.9
161,357 stars · Apache-2.0
AI Agents
Dify leads by 22.5 · decisive
A · leads
97.9
161,357 stars · Apache-2.0
B
75.4
30,565 stars · license n/a
Dify versus infisical is a AI Agents comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Dify is written mainly in Python; infisical is written mainly in TypeScript. The composite score is 97.9 for Dify and 75.4 for infisical.
Dify has 161,357 GitHub stars to infisical's 30,565, a gap of 130,792 (5.28×). Forks are 25,515 for Dify and 2,434 for infisical. On the log scale used inside this pair, adoption is 100 versus 86, and the fork community is 100 versus 77.
Push history: Dify was last pushed on 17 November 2026 (0 days ago), and infisical was last pushed on 17 November 2026 (0 days ago). Open issues stand at 1,422 for Dify (0.009 per star) and 925 for infisical (0.030 per star). Issue-health scores are 84 and 70; activity scores are 100 and 100.
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. infisical 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. License scores in this pair are 96 for Dify and 30 for infisical. This is a procurement signal, not legal advice.
Only Dify is marked self-hostable here (161,357 stars, deploy score 100). infisical is not (30,565 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: Dify is open source, infisical is unpriced in this catalog.
Dify is ahead on every scored dimension that is not level. Level dimensions: recent activity. The widest gap is license flexibility at 66 points (96 vs 30), and the tightest is recent activity at 0 points (100 vs 100).
Dify finishes ahead at 97.9 against infisical at 75.4, a 22.5 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 | Dify | infisical |
|---|---|---|
| GitHub stars | 161,357 | 30,565 |
| Forks | 25,515 | 2,434 |
| Open issues | 1,422 | 925 |
| Adoption | 100 | 86 |
| Activity | 100 | 100 |
| Community | 100 | 77 |
| Issue health | 84 | 70 |
| License | 96 | 30 |
| Self-hosting | 100 | 35 |
| Composite | 97.9 | 75.4 |
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.
Infisical is the open-source platform for securing secrets, certificates, access, and AI Agents.
Dify has more GitHub stars: 161,357 versus 30,565 for infisical. The gap is 130,792 stars.
Both were last pushed on 17 November 2026.
Only Dify is marked self-hostable. infisical is not.
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. infisical 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Dify scores 97.9 and infisical scores 75.4. This page calls that a decisive lead for Dify.