A · leads
Dify
97.9
161,357 stars · Apache-2.0
AI Agents
Dify leads by 10.1 · clear
A · leads
97.9
161,357 stars · Apache-2.0
B
87.8
24,678 stars · MIT
Dify versus happy 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; happy is written mainly in Swift. The composite score is 97.9 for Dify and 87.8 for happy.
Dify has 161,357 GitHub stars to happy's 24,678, a gap of 136,679 (6.54×). Forks are 25,515 for Dify and 2,123 for happy. On the log scale used inside this pair, adoption is 100 versus 84, and the fork community is 100 versus 76.
Push history: Dify was last pushed on 17 November 2026 (0 days ago), and happy was last pushed on 17 November 2026 (0 days ago). Open issues stand at 1,422 for Dify (0.009 per star) and 1,111 for happy (0.045 per star). Issue-health scores are 84 and 70; 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. happy 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 happy. This is a procurement signal, not legal advice.
In AI Agents, both Dify (161,357 stars) and happy (24,678 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, happy is open source.
Dify is ahead on every scored dimension that is not level. Level dimensions: recent activity, license flexibility, self-hosting. The widest gap is fork community at 24 points (100 vs 76), and the tightest is self-hosting at 0 points (100 vs 100).
Dify finishes ahead at 97.9 against happy at 87.8, a 10.1 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 | happy |
|---|---|---|
| GitHub stars | 161,357 | 24,678 |
| Forks | 25,515 | 2,123 |
| Open issues | 1,422 | 1,111 |
| Adoption | 100 | 84 |
| Activity | 100 | 100 |
| Community | 100 | 76 |
| Issue health | 84 | 70 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 97.9 | 87.8 |
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.
Orchestrate Claude, Codex and Grok in one app. Open-source (MIT), reuses the subscriptions you already pay for.
Dify has more GitHub stars: 161,357 versus 24,678 for happy. The gap is 136,679 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both Dify and happy 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. happy 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 happy scores 87.8. This page calls that a clear lead for Dify.