A
Dify
97.9
161,357 stars · Apache-2.0
AI Agents
Open WebUI leads by 1.0 · narrow
A
97.9
161,357 stars · Apache-2.0
B · leads
98.9
158,922 stars · MIT
Dify versus Open WebUI 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; Open WebUI is written mainly in Svelte. The composite score is 97.9 for Dify and 98.9 for Open WebUI.
Dify has 161,357 GitHub stars to Open WebUI's 158,922, a gap of 2,435 (1.02×). Forks are 25,515 for Dify and 23,097 for Open WebUI. On the log scale used inside this pair, adoption is 100 versus 100, and the fork community is 100 versus 99.
Push history: Dify was last pushed on 17 November 2026 (0 days ago), and Open WebUI was last pushed on 17 November 2026 (0 days ago). Open issues stand at 1,422 for Dify (0.009 per star) and 208 for Open WebUI (0.001 per star). Issue-health scores are 84 and 96; 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. Open WebUI 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 Open WebUI. This is a procurement signal, not legal advice.
In AI Agents, both Dify (161,357 stars) and Open WebUI (158,922 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, Open WebUI is open source.
The lead is split. Dify is furthest ahead on fork community (100 to 99), while Open WebUI is furthest ahead on issue health (96 to 84). Choose the dimension a rollout cannot compromise on.
Open WebUI finishes ahead at 98.9 against Dify at 97.9, a 1.0 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 | Open WebUI |
|---|---|---|
| GitHub stars | 161,357 | 158,922 |
| Forks | 25,515 | 23,097 |
| Open issues | 1,422 | 208 |
| Adoption | 100 | 100 |
| Activity | 100 | 100 |
| Community | 100 | 99 |
| Issue health | 84 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 97.9 | 98.9 |
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.
Open WebUI is a self-hosted chat interface for local and remote language models, including Ollama. It adds users, documents, and tools around the model endpoint.
Dify has more GitHub stars: 161,357 versus 158,922 for Open WebUI. The gap is 2,435 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both Dify and Open WebUI 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. Open WebUI 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.
Open WebUI scores 98.9 and Dify scores 97.9. This page calls that a narrow lead for Open WebUI.