A · leads
Dify
97.9
161,357 stars · Apache-2.0
AI Agents
Dify leads by 1.8 · narrow
A · leads
97.9
161,357 stars · Apache-2.0
B
96.1
108,897 stars · Apache-2.0
Dify versus gemini-cli 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; gemini-cli is written mainly in TypeScript. The composite score is 97.9 for Dify and 96.1 for gemini-cli.
Dify has 161,357 GitHub stars to gemini-cli's 108,897, a gap of 52,460 (1.48×). Forks are 25,515 for Dify and 14,956 for gemini-cli. On the log scale used inside this pair, adoption is 100 versus 97, and the fork community is 100 versus 95.
Push history: Dify was last pushed on 17 November 2026 (0 days ago), and gemini-cli was last pushed on 17 November 2026 (0 days ago). Open issues stand at 1,422 for Dify (0.009 per star) and 739 for gemini-cli (0.007 per star). Issue-health scores are 84 and 84; activity scores are 100 and 100.
Both Dify and gemini-cli 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 gemini-cli (108,897 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, gemini-cli 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 5 points (100 vs 95), and the tightest is self-hosting at 0 points (100 vs 100).
Dify finishes ahead at 97.9 against gemini-cli at 96.1, a 1.8 point narrow 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 | gemini-cli |
|---|---|---|
| GitHub stars | 161,357 | 108,897 |
| Forks | 25,515 | 14,956 |
| Open issues | 1,422 | 739 |
| Adoption | 100 | 97 |
| Activity | 100 | 100 |
| Community | 100 | 95 |
| Issue health | 84 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 97.9 | 96.1 |
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.
An open-source AI agent that brings the power of Gemini directly into your terminal.
Dify has more GitHub stars: 161,357 versus 108,897 for gemini-cli. The gap is 52,460 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both Dify and gemini-cli 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. gemini-cli 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 gemini-cli scores 96.1. This page calls that a narrow lead for Dify.