A · leads
Open WebUI
99.1
158,922 stars · MIT
AI Agents
Open WebUI leads by 11.3 · clear
A · leads
99.1
158,922 stars · MIT
B
87.8
13,578 stars · Apache-2.0
Open WebUI versus txtai 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; txtai is written mainly in Python. The composite score is 99.1 for Open WebUI and 87.8 for txtai.
Open WebUI has 158,922 GitHub stars to txtai's 13,578, a gap of 145,344 (11.70×). Forks are 23,097 for Open WebUI and 1,040 for txtai. On the log scale used inside this pair, adoption is 100 versus 80, and the fork community is 100 versus 69.
Push history: Open WebUI was last pushed on 17 November 2026 (0 days ago), and txtai was last pushed on 17 November 2026 (0 days ago). Open issues stand at 208 for Open WebUI (0.001 per star) and 38 for txtai (0.003 per star). Issue-health scores are 96 and 96; activity scores are 100 and 100.
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. txtai 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 txtai. This is a procurement signal, not legal advice.
In AI Agents, both Open WebUI (158,922 stars) and txtai (13,578 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, txtai is open source.
Open WebUI is ahead on every scored dimension that is not level. Level dimensions: recent activity, issue health, license flexibility, self-hosting. The widest gap is fork community at 31 points (100 vs 69), and the tightest is self-hosting at 0 points (100 vs 100).
Open WebUI finishes ahead at 99.1 against txtai at 87.8, a 11.3 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 | txtai |
|---|---|---|
| GitHub stars | 158,922 | 13,578 |
| Forks | 23,097 | 1,040 |
| Open issues | 208 | 38 |
| Adoption | 100 | 80 |
| Activity | 100 | 100 |
| Community | 100 | 69 |
| Issue health | 96 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 99.1 | 87.8 |
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.
💡 All-in-one AI framework for semantic search, LLM orchestration and language model workflows
Open WebUI has more GitHub stars: 158,922 versus 13,578 for txtai. The gap is 145,344 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both Open WebUI and txtai 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. txtai 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 txtai scores 87.8. This page calls that a clear lead for Open WebUI.