A
agent-orchestrator
84.5
14,849 stars · Apache-2.0
AI Agents
Dify leads by 13.4 · clear
A
84.5
14,849 stars · Apache-2.0
B · leads
97.9
161,357 stars · Apache-2.0
agent-orchestrator versus Dify is a AI Agents comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. agent-orchestrator is written mainly in TypeScript; Dify is written mainly in Python. The composite score is 84.5 for agent-orchestrator and 97.9 for Dify.
Dify has 161,357 GitHub stars to agent-orchestrator's 14,849, a gap of 146,508 (10.87×). Forks are 2,042 for agent-orchestrator and 25,515 for Dify. On the log scale used inside this pair, adoption is 80 versus 100, and the fork community is 75 versus 100.
Push history: agent-orchestrator 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 1,028 for agent-orchestrator (0.069 per star) and 1,422 for Dify (0.009 per star). Issue-health scores are 52 and 84; activity scores are 100 and 100.
Both agent-orchestrator 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 agent-orchestrator (14,849 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: agent-orchestrator is open source, Dify 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 (52 vs 84), and the tightest is self-hosting at 0 points (100 vs 100).
Dify finishes ahead at 97.9 against agent-orchestrator at 84.5, a 13.4 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 | agent-orchestrator | Dify |
|---|---|---|
| GitHub stars | 14,849 | 161,357 |
| Forks | 2,042 | 25,515 |
| Open issues | 1,028 | 1,422 |
| Adoption | 80 | 100 |
| Activity | 100 | 100 |
| Community | 75 | 100 |
| Issue health | 52 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 84.5 | 97.9 |
Plan, run and supervise fleets of agents from task to merged PR. Desktop (macOS, Windows, Linux) + iPhone & Android apps. Supports Claude Code, Codex & 35+ coding agents.
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 14,849 for agent-orchestrator. The gap is 146,508 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both agent-orchestrator and Dify as self-hostable. Confirm each project's deploy docs before you plan a migration.
agent-orchestrator 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 agent-orchestrator scores 84.5. This page calls that a clear lead for Dify.