Skip to content
DevUtils Online

AI Agents

corsair vs Open WebUI

Open WebUI leads by 27.1 · decisive

A

corsair

72.0

15,648 stars · license n/a

corsair 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. corsair is written mainly in TypeScript; Open WebUI is written mainly in Svelte. The composite score is 72.0 for corsair and 99.1 for Open WebUI.

Open WebUI has 158,922 GitHub stars to corsair's 15,648, a gap of 143,274 (10.16×). Forks are 724 for corsair and 23,097 for Open WebUI. On the log scale used inside this pair, adoption is 81 versus 100, and the fork community is 66 versus 100.

Push history: corsair 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 320 for corsair (0.020 per star) and 208 for Open WebUI (0.001 per star). Issue-health scores are 70 and 96; activity scores are 100 and 100.

corsair is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. 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 30 for corsair and 96 for Open WebUI. This is a procurement signal, not legal advice.

Only Open WebUI is marked self-hostable here (158,922 stars, deploy score 100). corsair is not (15,648 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: corsair is unpriced in this catalog, Open WebUI is open source.

Open WebUI is ahead on every scored dimension that is not level. Level dimensions: recent activity. The widest gap is license flexibility at 66 points (30 vs 96), and the tightest is recent activity at 0 points (100 vs 100).

Open WebUI finishes ahead at 99.1 against corsair at 72.0, a 27.1 point decisive margin under the published weights.

Scores are computed inside this pair only. Method and weights.

Where they separate

The numbers

Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.

corsair versus Open WebUI metrics
Signal corsair Open WebUI
GitHub stars 15,648 158,922
Forks 724 23,097
Open issues 320 208
Adoption 81 100
Activity 100 100
Community 66 100
Issue health 70 96
License 30 96
Self-hosting 35 100
Composite 72.0 99.1

Open WebUI

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.

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, corsair or Open WebUI?

Open WebUI has more GitHub stars: 158,922 versus 15,648 for corsair. The gap is 143,274 stars.

Which was updated more recently, corsair or Open WebUI?

Both were last pushed on 17 November 2026.

Can I self-host both corsair and Open WebUI?

Only Open WebUI is marked self-hostable. corsair is not.

Which license is easier to embed in a commercial product, corsair or Open WebUI?

corsair is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. 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.

Who wins the corsair vs Open WebUI score?

Open WebUI scores 99.1 and corsair scores 72.0. This page calls that a decisive lead for Open WebUI.

Related comparisons