A · leads
Dify
97.9
161,357 stars · Apache-2.0
AI Agents
Dify leads by 13.6 · clear
A · leads
97.9
161,357 stars · Apache-2.0
B
84.3
16,362 stars · MIT
Dify versus Paradev 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; Paradev is written mainly in TypeScript. The composite score is 97.9 for Dify and 84.3 for Paradev.
Dify has 161,357 GitHub stars to Paradev's 16,362, a gap of 144,995 (9.86×). Forks are 25,515 for Dify and 1,468 for Paradev. On the log scale used inside this pair, adoption is 100 versus 81, and the fork community is 100 versus 72.
Push history: Dify was last pushed on 17 November 2026 (0 days ago), and Paradev was last pushed on 17 November 2026 (0 days ago). Open issues stand at 1,422 for Dify (0.009 per star) and 1,305 for Paradev (0.080 per star). Issue-health scores are 84 and 52; 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. Paradev 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 Paradev. This is a procurement signal, not legal advice.
In AI Agents, both Dify (161,357 stars) and Paradev (16,362 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, Paradev 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 issue health at 32 points (84 vs 52), and the tightest is self-hosting at 0 points (100 vs 100).
Dify finishes ahead at 97.9 against Paradev at 84.3, a 13.6 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 | Paradev |
|---|---|---|
| GitHub stars | 161,357 | 16,362 |
| Forks | 25,515 | 1,468 |
| Open issues | 1,422 | 1,305 |
| Adoption | 100 | 81 |
| Activity | 100 | 100 |
| Community | 100 | 72 |
| Issue health | 84 | 52 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 97.9 | 84.3 |
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.
Paradev is an open-source Codex App and Conductor alternative. Orchestrate an army coding agents in parallel with your own subscriptions.
Dify has more GitHub stars: 161,357 versus 16,362 for Paradev. The gap is 144,995 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both Dify and Paradev 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. Paradev 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 Paradev scores 84.3. This page calls that a clear lead for Dify.