A
CloakBrowser
90.5
32,949 stars · MIT
AI Agents
Open WebUI leads by 8.6 · clear
A
90.5
32,949 stars · MIT
B · leads
99.1
158,922 stars · MIT
CloakBrowser 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. CloakBrowser is written mainly in Python; Open WebUI is written mainly in Svelte. The composite score is 90.5 for CloakBrowser and 99.1 for Open WebUI.
Open WebUI has 158,922 GitHub stars to CloakBrowser's 32,949, a gap of 125,973 (4.82×). Forks are 2,733 for CloakBrowser and 23,097 for Open WebUI. On the log scale used inside this pair, adoption is 87 versus 100, and the fork community is 79 versus 100.
Push history: CloakBrowser 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 169 for CloakBrowser (0.005 per star) and 208 for Open WebUI (0.001 per star). Issue-health scores are 84 and 96; activity scores are 100 and 100.
Both CloakBrowser and Open WebUI are listed as MIT. 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 CloakBrowser (32,949 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: CloakBrowser is open source, Open WebUI is open source.
Open WebUI is ahead on every scored dimension that is not level. Level dimensions: recent activity, license flexibility, self-hosting. The widest gap is fork community at 21 points (79 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).
Open WebUI finishes ahead at 99.1 against CloakBrowser at 90.5, a 8.6 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 | CloakBrowser | Open WebUI |
|---|---|---|
| GitHub stars | 32,949 | 158,922 |
| Forks | 2,733 | 23,097 |
| Open issues | 169 | 208 |
| Adoption | 87 | 100 |
| Activity | 100 | 100 |
| Community | 79 | 100 |
| Issue health | 84 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 90.5 | 99.1 |
Stealth Chromium that passes every bot detection test. Drop-in Playwright replacement with source-level fingerprint patches. 50+ tests passed.
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 WebUI has more GitHub stars: 158,922 versus 32,949 for CloakBrowser. The gap is 125,973 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both CloakBrowser and Open WebUI as self-hostable. Confirm each project's deploy docs before you plan a migration.
CloakBrowser 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. 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 99.1 and CloakBrowser scores 90.5. This page calls that a clear lead for Open WebUI.