A · leads
Open WebUI
99.1
158,922 stars · MIT
AI Agents
Open WebUI leads by 10.4 · clear
A · leads
99.1
158,922 stars · MIT
B
88.7
31,141 stars · Apache-2.0
Open WebUI versus OpenCLI 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; OpenCLI is written mainly in JavaScript. The composite score is 99.1 for Open WebUI and 88.7 for OpenCLI.
Open WebUI has 158,922 GitHub stars to OpenCLI's 31,141, a gap of 127,781 (5.10×). Forks are 23,097 for Open WebUI and 3,047 for OpenCLI. On the log scale used inside this pair, adoption is 100 versus 86, and the fork community is 100 versus 80.
Push history: Open WebUI was last pushed on 17 November 2026 (0 days ago), and OpenCLI was last pushed on 07 November 2026 (10 days ago). Open issues stand at 208 for Open WebUI (0.001 per star) and 318 for OpenCLI (0.010 per star). Issue-health scores are 96 and 84; activity scores are 100 and 92.
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. OpenCLI 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 OpenCLI. This is a procurement signal, not legal advice.
In AI Agents, both Open WebUI (158,922 stars) and OpenCLI (31,141 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, OpenCLI 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 fork community at 20 points (100 vs 80), and the tightest is self-hosting at 0 points (100 vs 100).
Open WebUI finishes ahead at 99.1 against OpenCLI at 88.7, a 10.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 | Open WebUI | OpenCLI |
|---|---|---|
| GitHub stars | 158,922 | 31,141 |
| Forks | 23,097 | 3,047 |
| Open issues | 208 | 318 |
| Adoption | 100 | 86 |
| Activity | 100 | 92 |
| Community | 100 | 80 |
| Issue health | 96 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 99.1 | 88.7 |
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.
Make Any Website into CLI & Use your logged-in browser by AI agent.
Open WebUI has more GitHub stars: 158,922 versus 31,141 for OpenCLI. The gap is 127,781 stars.
Open WebUI was pushed more recently: 17 November 2026 versus 07 November 2026 for OpenCLI. That is 10 days apart.
Yes. This catalog marks both Open WebUI and OpenCLI 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. OpenCLI 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 OpenCLI scores 88.7. This page calls that a clear lead for Open WebUI.