Skip to content
DevUtils Online

AI Agents

Open WebUI vs text-to-cad

Open WebUI leads by 8.1 · clear

Open WebUI versus text-to-cad 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; text-to-cad is written mainly in Python. The composite score is 99.1 for Open WebUI and 91.0 for text-to-cad.

Open WebUI has 158,922 GitHub stars to text-to-cad's 26,630, a gap of 132,292 (5.97×). Forks are 23,097 for Open WebUI and 2,537 for text-to-cad. On the log scale used inside this pair, adoption is 100 versus 85, and the fork community is 100 versus 78.

Push history: Open WebUI was last pushed on 17 November 2026 (0 days ago), and text-to-cad was last pushed on 17 November 2026 (0 days ago). Open issues stand at 208 for Open WebUI (0.001 per star) and 46 for text-to-cad (0.002 per star). Issue-health scores are 96 and 96; activity scores are 100 and 100.

Both Open WebUI and text-to-cad 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 Open WebUI (158,922 stars) and text-to-cad (26,630 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, text-to-cad 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 22 points (100 vs 78), and the tightest is self-hosting at 0 points (100 vs 100).

Open WebUI finishes ahead at 99.1 against text-to-cad at 91.0, a 8.1 point clear 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.

Open WebUI versus text-to-cad metrics
Signal Open WebUI text-to-cad
GitHub stars 158,922 26,630
Forks 23,097 2,537
Open issues 208 46
Adoption 100 85
Activity 100 100
Community 100 78
Issue health 96 96
License 96 96
Self-hosting 100 100
Composite 99.1 91.0

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, Open WebUI or text-to-cad?

Open WebUI has more GitHub stars: 158,922 versus 26,630 for text-to-cad. The gap is 132,292 stars.

Which was updated more recently, Open WebUI or text-to-cad?

Both were last pushed on 17 November 2026.

Can I self-host both Open WebUI and text-to-cad?

Yes. This catalog marks both Open WebUI and text-to-cad as self-hostable. Confirm each project's deploy docs before you plan a migration.

Which license is easier to embed in a commercial product, Open WebUI or text-to-cad?

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. text-to-cad 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 Open WebUI vs text-to-cad score?

Open WebUI scores 99.1 and text-to-cad scores 91.0. This page calls that a clear lead for Open WebUI.

Related comparisons