A · leads
Open WebUI
99.1
158,922 stars · MIT
AI Agents
Open WebUI leads by 24.6 · decisive
A · leads
99.1
158,922 stars · MIT
B
74.5
18,258 stars · Apache-2.0
Open WebUI versus openfang is a AI Agents comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Open WebUI is written mainly in Svelte; openfang is written mainly in Rust. The composite score is 99.1 for Open WebUI and 74.5 for openfang.
Open WebUI has 158,922 GitHub stars to openfang's 18,258, a gap of 140,664 (8.70×). Forks are 23,097 for Open WebUI and 2,283 for openfang. On the log scale used inside this pair, adoption is 100 versus 82, and the fork community is 100 versus 77.
Push history: Open WebUI was last pushed on 17 November 2026 (0 days ago), and openfang was last pushed on 02 July 2026 (138 days ago). Open issues stand at 208 for Open WebUI (0.001 per star) and 136 for openfang (0.007 per star). Issue-health scores are 96 and 84; activity scores are 100 and 36.
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. openfang 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. License scores in this pair are 96 for Open WebUI and 96 for openfang. This is a procurement signal, not legal advice.
In AI Agents, both Open WebUI (158,922 stars) and openfang (18,258 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: Open WebUI is open source, openfang is open source.
Open WebUI is ahead on every scored dimension that is not level. Level dimensions: license flexibility, self-hosting. The widest gap is recent activity at 64 points (100 vs 36), and the tightest is self-hosting at 0 points (100 vs 100).
Open WebUI finishes ahead at 99.1 against openfang at 74.5, a 24.6 point decisive 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 | Open WebUI | openfang |
|---|---|---|
| GitHub stars | 158,922 | 18,258 |
| Forks | 23,097 | 2,283 |
| Open issues | 208 | 136 |
| Adoption | 100 | 82 |
| Activity | 100 | 36 |
| Community | 100 | 77 |
| Issue health | 96 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 99.1 | 74.5 |
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.
Open-source Agent Operating System
Open WebUI has more GitHub stars: 158,922 versus 18,258 for openfang. The gap is 140,664 stars.
Open WebUI was pushed more recently: 17 November 2026 versus 02 July 2026 for openfang. That is 138 days apart.
Yes. This catalog marks both Open WebUI and openfang as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. openfang 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.
Open WebUI scores 99.1 and openfang scores 74.5. This page calls that a decisive lead for Open WebUI.