A
composio
92.4
31,135 stars · MIT
AI Agents
Open WebUI leads by 6.7 · narrow
A
92.4
31,135 stars · MIT
B · leads
99.1
158,922 stars · MIT
composio 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. composio is written mainly in TypeScript; Open WebUI is written mainly in Svelte. The composite score is 92.4 for composio and 99.1 for Open WebUI.
Open WebUI has 158,922 GitHub stars to composio's 31,135, a gap of 127,787 (5.10×). Forks are 4,956 for composio and 23,097 for Open WebUI. On the log scale used inside this pair, adoption is 86 versus 100, and the fork community is 85 versus 100.
Push history: composio 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 145 for composio (0.005 per star) and 208 for Open WebUI (0.001 per star). Issue-health scores are 96 and 96; activity scores are 100 and 100.
Both composio 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 composio (31,135 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: composio is open source, Open WebUI 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 15 points (85 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).
Open WebUI finishes ahead at 99.1 against composio at 92.4, a 6.7 point narrow 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 | composio | Open WebUI |
|---|---|---|
| GitHub stars | 31,135 | 158,922 |
| Forks | 4,956 | 23,097 |
| Open issues | 145 | 208 |
| Adoption | 86 | 100 |
| Activity | 100 | 100 |
| Community | 85 | 100 |
| Issue health | 96 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 92.4 | 99.1 |
Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
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 31,135 for composio. The gap is 127,787 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both composio and Open WebUI as self-hostable. Confirm each project's deploy docs before you plan a migration.
composio 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 composio scores 92.4. This page calls that a narrow lead for Open WebUI.