A · leads
Dify
97.9
161,357 stars · Apache-2.0
AI Agents
Dify leads by 11.0 · clear
A · leads
97.9
161,357 stars · Apache-2.0
B
86.9
14,910 stars · Apache-2.0
Dify versus E2B is a AI Agents comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Both projects are written mainly in Python. The composite score is 97.9 for Dify and 86.9 for E2B.
Dify has 161,357 GitHub stars to E2B's 14,910, a gap of 146,447 (10.82×). Forks are 25,515 for Dify and 1,171 for E2B. On the log scale used inside this pair, adoption is 100 versus 80, and the fork community is 100 versus 70.
Push history: Dify was last pushed on 17 November 2026 (0 days ago), and E2B was last pushed on 17 November 2026 (0 days ago). Open issues stand at 1,422 for Dify (0.009 per star) and 130 for E2B (0.009 per star). Issue-health scores are 84 and 84; activity scores are 100 and 100.
Both Dify and E2B 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 E2B (14,910 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, E2B is open source.
Dify is ahead on every scored dimension that is not level. Level dimensions: recent activity, issue health, 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 E2B at 86.9, a 11.0 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 | E2B |
|---|---|---|
| GitHub stars | 161,357 | 14,910 |
| Forks | 25,515 | 1,171 |
| Open issues | 1,422 | 130 |
| Adoption | 100 | 80 |
| Activity | 100 | 100 |
| Community | 100 | 70 |
| Issue health | 84 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 97.9 | 86.9 |
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, secure environment with real-world tools for enterprise-grade agents.
Dify has more GitHub stars: 161,357 versus 14,910 for E2B. The gap is 146,447 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both Dify and E2B 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. E2B 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 E2B scores 86.9. This page calls that a clear lead for Dify.