Skip to content
DevUtils Online

AI Agents

Flowise vs Open WebUI

Open WebUI leads by 22.1 · decisive

A

Flowise

76.9

55,573 stars · Apache-2.0

Flowise 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. Flowise is written mainly in TypeScript; Open WebUI is written mainly in Svelte. The composite score is 76.9 for Flowise and 99.0 for Open WebUI.

Open WebUI has 158,922 GitHub stars to Flowise's 55,573, a gap of 103,349 (2.86×). Forks are 25,096 for Flowise and 23,097 for Open WebUI. On the log scale used inside this pair, adoption is 91 versus 100, and the fork community is 100 versus 99.

Push history: Flowise was last pushed on 13 August 2026 (96 days ago), and Open WebUI was last pushed on 17 November 2026 (0 days ago). Open issues stand at 1,033 for Flowise (0.019 per star) and 208 for Open WebUI (0.001 per star). Issue-health scores are 84 and 96; activity scores are 18 and 100. Flowise is archived on GitHub, so its activity score is capped.

Flowise 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. 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 96 for Flowise and 96 for Open WebUI. This is a procurement signal, not legal advice.

In AI Agents, both Flowise (55,573 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: Flowise is open source, Open WebUI is open source.

The lead is split. Flowise is furthest ahead on fork community (100 to 99), while Open WebUI is furthest ahead on recent activity (100 to 18). Choose the dimension a rollout cannot compromise on.

Open WebUI finishes ahead at 99.0 against Flowise at 76.9, a 22.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.

Flowise versus Open WebUI metrics
Signal Flowise Open WebUI
GitHub stars 55,573 158,922
Forks 25,096 23,097
Open issues 1,033 208
Adoption 91 100
Activity 18 100
Community 100 99
Issue health 84 96
License 96 96
Self-hosting 100 100
Composite 76.9 99.0

Flowise

Flowise is a visual builder for LLM chains and agents on top of libraries such as LangChain. You design a flow in the browser and run it from a self-hosted Node service.

Project site · GitHub · Full profile

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, Flowise or Open WebUI?

Open WebUI has more GitHub stars: 158,922 versus 55,573 for Flowise. The gap is 103,349 stars.

Which was updated more recently, Flowise or Open WebUI?

Open WebUI was pushed more recently: 17 November 2026 versus 13 August 2026 for Flowise. That is 96 days apart.

Can I self-host both Flowise and Open WebUI?

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

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

Flowise 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. 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 Flowise vs Open WebUI score?

Open WebUI scores 99.0 and Flowise scores 76.9. This page calls that a decisive lead for Open WebUI.

Related comparisons