A · leads
Dify
97.9
161,357 stars · Apache-2.0
AI Agents
Dify leads by 9.3 · clear
A · leads
97.9
161,357 stars · Apache-2.0
B
88.6
21,509 stars · Apache-2.0
Dify versus img2threejs 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 88.6 for img2threejs.
Dify has 161,357 GitHub stars to img2threejs's 21,509, a gap of 139,848 (7.50×). Forks are 25,515 for Dify and 1,839 for img2threejs. On the log scale used inside this pair, adoption is 100 versus 83, and the fork community is 100 versus 74.
Push history: Dify was last pushed on 17 November 2026 (0 days ago), and img2threejs was last pushed on 16 November 2026 (1 day ago). Open issues stand at 1,422 for Dify (0.009 per star) and 123 for img2threejs (0.006 per star). Issue-health scores are 84 and 84; activity scores are 100 and 100.
Both Dify and img2threejs 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 img2threejs (21,509 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, img2threejs 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 26 points (100 vs 74), and the tightest is self-hosting at 0 points (100 vs 100).
Dify finishes ahead at 97.9 against img2threejs at 88.6, a 9.3 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 | img2threejs |
|---|---|---|
| GitHub stars | 161,357 | 21,509 |
| Forks | 25,515 | 1,839 |
| Open issues | 1,422 | 123 |
| Adoption | 100 | 83 |
| Activity | 100 | 100 |
| Community | 100 | 74 |
| Issue health | 84 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 97.9 | 88.6 |
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.
Rebuild the object in a reference image as a code-only, procedural, quality-gated, animation-ready Three.js model. Token-efficient image-to-3D.
Dify has more GitHub stars: 161,357 versus 21,509 for img2threejs. The gap is 139,848 stars.
Dify was pushed more recently: 17 November 2026 versus 16 November 2026 for img2threejs. That is 1 days apart.
Yes. This catalog marks both Dify and img2threejs 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. img2threejs 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 img2threejs scores 88.6. This page calls that a clear lead for Dify.