A · leads
Dify
97.9
161,357 stars · Apache-2.0
AI Agents
Dify leads by 14.4 · clear
A · leads
97.9
161,357 stars · Apache-2.0
B
83.5
13,344 stars · Apache-2.0
Dify versus InsForge 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; InsForge is written mainly in TypeScript. The composite score is 97.9 for Dify and 83.5 for InsForge.
Dify has 161,357 GitHub stars to InsForge's 13,344, a gap of 148,013 (12.09×). Forks are 25,515 for Dify and 1,249 for InsForge. On the log scale used inside this pair, adoption is 100 versus 79, and the fork community is 100 versus 70.
Push history: Dify was last pushed on 17 November 2026 (0 days ago), and InsForge was last pushed on 08 November 2026 (9 days ago). Open issues stand at 1,422 for Dify (0.009 per star) and 278 for InsForge (0.021 per star). Issue-health scores are 84 and 70; activity scores are 100 and 92.
Both Dify and InsForge 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 Dify (161,357 stars) and InsForge (13,344 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: Dify is open source, InsForge is open source.
Dify is ahead on every scored dimension that is not level. Level dimensions: license flexibility, self-hosting. The widest gap is fork community at 30 points (100 vs 70), and the tightest is self-hosting at 0 points (100 vs 100).
Dify finishes ahead at 97.9 against InsForge at 83.5, a 14.4 point clear 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 | InsForge |
|---|---|---|
| GitHub stars | 161,357 | 13,344 |
| Forks | 25,515 | 1,249 |
| Open issues | 1,422 | 278 |
| Adoption | 100 | 79 |
| Activity | 100 | 92 |
| Community | 100 | 70 |
| Issue health | 84 | 70 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 97.9 | 83.5 |
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.
The all-in-one, open-source backend platform for agentic coding. InsForge gives your coding agent database, auth, storage, compute, hosting, and AI gateway to ship full-stack apps end-to-end.
Dify has more GitHub stars: 161,357 versus 13,344 for InsForge. The gap is 148,013 stars.
Dify was pushed more recently: 17 November 2026 versus 08 November 2026 for InsForge. That is 9 days apart.
Yes. This catalog marks both Dify and InsForge as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. InsForge 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 InsForge scores 83.5. This page calls that a clear lead for Dify.