A · leads
Dify
97.9
161,357 stars · Apache-2.0
AI Agents
Dify leads by 6.9 · narrow
A · leads
97.9
161,357 stars · Apache-2.0
B
91.0
25,582 stars · MIT
Dify versus editor 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; editor is written mainly in TypeScript. The composite score is 97.9 for Dify and 91.0 for editor.
Dify has 161,357 GitHub stars to editor's 25,582, a gap of 135,775 (6.31×). Forks are 25,515 for Dify and 3,180 for editor. On the log scale used inside this pair, adoption is 100 versus 85, and the fork community is 100 versus 80.
Push history: Dify was last pushed on 17 November 2026 (0 days ago), and editor was last pushed on 17 November 2026 (0 days ago). Open issues stand at 1,422 for Dify (0.009 per star) and 58 for editor (0.002 per star). Issue-health scores are 84 and 96; 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. editor is listed as MIT, 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 96 for Dify and 96 for editor. This is a procurement signal, not legal advice.
In AI Agents, both Dify (161,357 stars) and editor (25,582 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, editor is open source.
The lead is split. Dify is furthest ahead on fork community (100 to 80), while editor is furthest ahead on issue health (96 to 84). Choose the dimension a rollout cannot compromise on.
Dify finishes ahead at 97.9 against editor at 91.0, a 6.9 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 | Dify | editor |
|---|---|---|
| GitHub stars | 161,357 | 25,582 |
| Forks | 25,515 | 3,180 |
| Open issues | 1,422 | 58 |
| Adoption | 100 | 85 |
| Activity | 100 | 100 |
| Community | 100 | 80 |
| Issue health | 84 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 97.9 | 91.0 |
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.
Open-source 3D architecture software for AECO, scan-to-BIM. Agent-friendly, browser-first, MCP, CLI.
Dify has more GitHub stars: 161,357 versus 25,582 for editor. The gap is 135,775 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both Dify and editor 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. editor is listed as MIT, 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 editor scores 91.0. This page calls that a narrow lead for Dify.