A
dapr
89.4
26,202 stars · Apache-2.0
AI Agents
Dify leads by 8.5 · clear
A
89.4
26,202 stars · Apache-2.0
B · leads
97.9
161,357 stars · Apache-2.0
dapr versus Dify is a AI Agents comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. dapr is written mainly in Go; Dify is written mainly in Python. The composite score is 89.4 for dapr and 97.9 for Dify.
Dify has 161,357 GitHub stars to dapr's 26,202, a gap of 135,155 (6.16×). Forks are 2,184 for dapr and 25,515 for Dify. On the log scale used inside this pair, adoption is 85 versus 100, and the fork community is 76 versus 100.
Push history: dapr was last pushed on 17 November 2026 (0 days ago), and Dify was last pushed on 17 November 2026 (0 days ago). Open issues stand at 473 for dapr (0.018 per star) and 1,422 for Dify (0.009 per star). Issue-health scores are 84 and 84; activity scores are 100 and 100.
Both dapr and Dify 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 dapr (26,202 stars) and Dify (161,357 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: dapr is open source, Dify 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 24 points (76 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).
Dify finishes ahead at 97.9 against dapr at 89.4, a 8.5 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 | dapr | Dify |
|---|---|---|
| GitHub stars | 26,202 | 161,357 |
| Forks | 2,184 | 25,515 |
| Open issues | 473 | 1,422 |
| Adoption | 85 | 100 |
| Activity | 100 | 100 |
| Community | 76 | 100 |
| Issue health | 84 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 89.4 | 97.9 |
Dapr is a portable runtime for building distributed applications across cloud and edge, combining event-driven architecture with workflow orchestration.
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.
Dify has more GitHub stars: 161,357 versus 26,202 for dapr. The gap is 135,155 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both dapr and Dify as self-hostable. Confirm each project's deploy docs before you plan a migration.
dapr 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. 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Dify scores 97.9 and dapr scores 89.4. This page calls that a clear lead for Dify.