Skip to main content
Open WebUIProduct page

Open WebUI Signals

What leaders and teams rolling out Open WebUI report, with every finding tied to its evidence.

Read the findings

What the evidence says

Whose sources count

Practitioner sentiment, leaders and teams

−74 Strong negative from 35 sources that take a side

How this figure is made

Strong negative overall signal, net 74 points negative

Each from a different author and a different discussion. Run a pilot on your team's recurring tasks to measure how often answers are used without rework.

Analyzed
83 total sources
Top praise
Search, Tools & MCP (1 of 5 sources) See praise evidence
Top concern
Feature Gaps (14 of 14 sources) See concern evidence

May 2025 to Oct 2026.

78 sources from practitioners, by month and sentiment.

Teams running Open WebUI for an organization mostly report problems: upgrade regressions are raised in 8 sources, feature gaps in 14, and performance at scale in 7, from KION GROUP's 40,000-user deployment to a three-replica rollback from v0.12.0. 2 of the 4 who describe a choice of chat interface kept Open WebUI.

Positive, mixed and negative sources

The score counts each source once, as the split does. See How the numbers work.

See the evidence

Below: 1 praise theme and 4 concerns.

Findings

Counted for Leaders and teams rolling it out, from 35 sources. Change group

What practitioners praise

Every capability practitioners describe positively, ranked by how many sources say so. Open one to read who said it.

  1. Search, Tools & MCP1 of 5 sources on it praise itWeb search, code execution, filter functions, and MCP tool servers extend the chat inside the same interface.

    Counted for Leaders and teams rolling it out.

    Positive, 1

    1. Positive

      alach11, reservoir engineer, data scientist and product manager at a Houston oil and gas company (HN profile), speaking for a company team

      Comment on: A playable DOOM MCP appHacker News comment

      The team stood up Open WebUI for internal chat and agent use and tested filter functions and MCP with games such as Snake and DOOM.

      Published Apr 28, 2026self-described: Open WebUI stood up for internal chat and agent use

    Mixed or negative, 4

    1. Negative

      Miklós Pathy, Puli Space Technologies (GitHub profile)

      issue: MCP tool errors reach the model as a Python list dump instead of the server's error textGitHub issue

      When a tool call fails MCP schema validation, Open WebUI feeds the model a Python list dump that buries the server's error text, so the model repeats the same bad call.

      Published Oct 22, 2026self-described: MCP tools reached through an OpenAI-compatible model with native tool calling

    2. Negative

      Ryota Kameoka, engineer at HERP (GitHub profile)

      issue: Static OAuth 2.1 MCP client uses none auth when server lists ["none", "client_secret_basic"], ignoring the configured client secretGitHub issue

      Open WebUI picked the 'none' token auth method for X Ads' MCP server and dropped the configured client secret, so the connection could not be authorized.

      Published Oct 21, 2026self-described: Connecting an MCP tool server that uses OAuth 2.1 with a client secret

    3. Negative

      viktorashi, Stratec Biomedical (GitHub profile)

      issue: Responses API follow-up after a tool call fails with 400 "Unknown parameter: 'input[n].status'" (stored reasoning items replayed unfiltered)GitHub issue

      With Azure OpenAI's Responses API, every turn where the model reasons and then calls a tool fails on the follow-up with HTTP 400, because stored reasoning items are replayed unfiltered.

      Published Oct 21, 2026self-described: An Azure OpenAI Responses API connection with a reasoning model

    4. Negative

      Taylor Wilsdon, director of engineering at Yelp (GitHub profile)

      issue: New OAuth 2.1 Streamable HTTP MCP server Eetries do not propagate across multi-node setupsGitHub issue

      In a multi-node cluster, a newly added OAuth 2.1 MCP tool server works only on the node it was created on.

      Published Dec 12, 2025self-described: A multi-node cluster with Redis config sync

    GILD's fact checks, which don't count as sources

    Checked Oct 28, 2026.Open WebUI documents its Ollama integration: models served by a connected Ollama instance appear in the model selector automatically. Ollama

    Checked Oct 28, 2026.The enterprise security page lists identity integration through SSO, LDAP, and role-based access control. Enterprise security

    Checked Oct 28, 2026.The v0.12.0 release notes cover integrations with Amazon Bedrock and OpenRouter, including a model ID for GPT-6 Sol on Bedrock and a fix for tool calls on models served through OpenRouter. Open WebUI v0.12.0 release notes

    Open them in the record

What concerns them

Every concern practitioners raise, most raised first.

  1. Feature GapsAll 14 sources on it raise it as a concernMissing or weak features such as Anthropic prompt caching, image generation, mobile apps, and agent-era workflows.

    Counted for Leaders and teams rolling it out.

    1. Negative

      Miklós Pathy, Puli Space Technologies (GitHub profile)

      issue: MCP tool errors reach the model as a Python list dump instead of the server's error textGitHub issue

      When a tool call fails MCP schema validation, Open WebUI feeds the model a Python list dump that buries the server's error text, so the model repeats the same bad call.

      Published Oct 22, 2026self-described: MCP tools reached through an OpenAI-compatible model with native tool calling

    2. Negative

      yGuy (Sebastian Müller), CTO at yWorks (GitHub profile)

      Feat: Make knowledge base retrieval opt-in; no selection should mean no accessGitHub issue comment

      A colleague's programming question in a blank new chat made the model query a team knowledge base, and details about the team were sent to the cloud provider. The team wants some knowledge bases usable only with local models, which Open WebUI cannot be configured to do.

      Published Oct 22, 2026self-described: A team instance that mixes commercial cloud models and local models, with a knowledge base shared across the team

    3. Negative

      Ryota Kameoka, engineer at HERP (GitHub profile)

      issue: Static OAuth 2.1 MCP client uses none auth when server lists ["none", "client_secret_basic"], ignoring the configured client secretGitHub issue

      Open WebUI picked the 'none' token auth method for X Ads' MCP server and dropped the configured client secret, so the connection could not be authorized.

      Published Oct 21, 2026self-described: Connecting an MCP tool server that uses OAuth 2.1 with a client secret

    4. Negative

      Christoph Lauper, Digitec Galaxus AG (GitHub profile)

      issue: streamed usage is summed per chunk, inflating input_tokens ~30x for providers that send cumulative usage on every chunk (Google OpenAI-compatible endpoint)GitHub issue

      Over 30 days on the author's production instance, Open WebUI stored 31.8× the real input tokens for 3598 gemini-flash-latest messages through an OpenAI connection, which skews the usage tooltip, context compaction and any per-token pricing. Claude Sonnet 5 and Claude Opus 5, which send usage only in the final chunk, were unaffected. A maintainer's one-word reply called it intended, and the issue was closed as completed.

      Published Oct 8, 2026self-described: A production instance with Gemini, Claude Sonnet 5 and Claude Opus 5 on OpenAI-compatible connections

    5. Negative

      Roman (moltar), ScaleLeap (GitHub profile)

      bug: pgvector client ignores DATABASE_ENABLE_IAM_TOKEN_AUTH, so RDS IAM auth and VECTOR_DB=pgvector cannot be used togetherGitHub issue

      With RDS IAM token auth the main database connects, but the pgvector client still asks for a password, so the container exits and the deployment never becomes healthy.

      Published Jul 30, 2026self-described: Open WebUI on Amazon RDS for PostgreSQL with IAM token auth and pgvector

    6. Negative

      Marco A. Rueda, Senior AI Engineer at Volkswagen Digital Solutions (GitHub profile)

      issue: Task Management builtin tools (create_tasks/update_task) fail in Temporary Chat mode: "Task with id not found"GitHub issue

      In Temporary Chat mode the model creates tasks, then every update fails with task not found, because the task tools are offered where they cannot persist.

      Published Jul 24, 2026self-described: Built-in task tools in Temporary Chat mode

    7. Negative

      E. Dalton, research analyst at Moodle (GitHub profile)

      issue: max_tokens rejection by upstream provider returns bare 400 to user with no log entry and no actionable messageGitHub issue

      When a model API rejects a request for max_tokens, users see a bare 400 and the provider's error never reaches the logs, so admins cannot diagnose it.

      Published Jul 20, 2026self-described: Open WebUI in front of an upstream model API

    8. Negative

      Arkadi Yaroslavtsev, Engineering Manager for Metabase Cloud (Metabase author page)

      How we picked LibreChat, and ended up with a Slack agentEngineering blog post, metabase.com

      Metabase's Cloud team gave Open WebUI a genuine deployment and found it polished, with all the enterprise admin controls you would want, yet first-class support was effectively OpenAI-only. Anthropic needed a community-written Python function and MCP support was second-class at the time, and LibreChat won on operability.

      Published Jul 20, 2026self-described: Metabase's Cloud team choosing one self-hosted chat front end to standardize the whole company on

    9. Negative

      stavros, founder of Stochastic Technologies (self-described on the site linked from the HN profile)

      Hacker News comment on deploying Open WebUI with the Claude APIHacker News comment

      One employee's ten messages of everyday work through Open WebUI cost US$200: Claude reported 44M input tokens with no cache hits, while Open WebUI reported 3M. In a reply the author names Anthropic caching, which the author had not known needed enabling, as the likely culprit.

      Published May 26, 2026self-described: Open WebUI deployed with the Claude API for employees, on a new API key

    10. Negative

      Tim Champ, UMBC (GitHub profile)

      Bug: Task endpoints (title/tags/follow-up generation) return 404 when chat model is from a direct connectionGitHub issue

      At UMBC, title, tag and follow-up generation return 404 whenever the chat model comes from a user's direct connection, even with a server task model configured.

      Published Apr 24, 2026self-described: A university deployment on ECS Fargate with direct user connections

    11. Negative

      Jason Culligan, Intel (GitHub profile)

      issue: Data truncated when uploaded as a file, no issues when the file text is pasted into the promptGitHub issue

      Models could not see content past roughly the middle of an uploaded HTML file, while pasting the same text into the prompt worked, so the upload path truncates documents.

      Published Apr 15, 2026self-described: Uploading HTML documents for the model to read

    12. Negative

      Florian, Lead Software Engineer at TKWW (The Knot Worldwide) (GitHub profile)

      issue: Import of ChatGPT export file is brokenGitHub issue

      Importing an unmodified ChatGPT export reported success while importing 0 chats from a file holding dozens.

      Published Apr 8, 2026self-described: Importing a ChatGPT conversations export

    13. Mixed

      Vladimir Levin, Woven by Toyota (GitHub profile)

      issue: Broken markdown checklistGitHub issue

      A markdown checklist inside a fenced block renders outside the block in the chat view.

      Published Dec 28, 2025self-described: Rendering model answers that contain markdown

    14. Mixed

      ojosilva, B2B founder (HN profile)

      Hacker News comment on chat clients tried for a teamHacker News comment

      Deployed Open WebUI for the team to chat through many APIs and finds it works well as a multi-user web deployment, though image generation has not been working. As a personal client it is sometimes buggy, with frequent fixes.

      Published Jul 31, 2025self-described: Open WebUI deployed for a team to chat through many model APIs

    Open them in the record
  2. Upgrade RegressionsAll 8 sources on it raise it as a concernNew releases that break search, networking, memory, or sessions on an existing deployment.

    Counted for Leaders and teams rolling it out.

    1. Negative

      viktorashi, Stratec Biomedical (GitHub profile)

      issue: Responses API follow-up after a tool call fails with 400 "Unknown parameter: 'input[n].status'" (stored reasoning items replayed unfiltered)GitHub issue

      With Azure OpenAI's Responses API, every turn where the model reasons and then calls a tool fails on the follow-up with HTTP 400, because stored reasoning items are replayed unfiltered.

      Published Oct 21, 2026self-described: An Azure OpenAI Responses API connection with a reasoning model

    2. Negative

      clg-e2e-tester-lang, GitHub user running a multi-instance deployment

      issue: 0.12.0 multi-instance Redis setup: containers grow to 8-11 GB RAM under chat load (0.11.4 stable)GitHub issue

      After upgrading a three-replica deployment to v0.12.0, containers grew from about 2 GB to 8 to 11 GB of RAM under chat load, and rolling back to v0.11.4 restored stability.

      Published Oct 12, 2026self-described: Three replicas per host sharing one Redis, with several users and tabs active

    3. Negative

      Damien S, Cloud Engineer at the Luxembourg Institute of Science and Technology (GitHub profile)

      issue: builtin retrieval tools build an incomplete user object, breaking knowledge search and group-shared file accessGitHub issue

      On v0.11.0 the built-in knowledge search fails while generating the query embedding and group-shared files become unreachable, because the tools build an incomplete user object.

      Published Jul 28, 2026self-described: An institute deployment with knowledge bases and an external embedding endpoint

    4. Negative

      cono, Chartbeat (GitHub profile)

      issue: runAsNonRoot: true breaks on v0.11.0GitHub issue

      A Kubernetes deployment on the latest tag started failing with runAsNonRoot because a cached model file in the image belongs to root with 0600 permissions.

      Published Jul 28, 2026self-described: A Kubernetes deployment that followed the latest tag

    5. Negative

      Dāvis Pazars, AI Engineer at Mikrotik (GitHub profile)

      issue: admin panel OAuth config is saved but never applied; SSO never activates without env varsGitHub issue

      While setting up Keycloak SSO in production, OAuth settings saved in the admin panel were never applied, so SSO did not activate without environment variables.

      Published Jul 9, 2026self-described: A production instance being set up with Keycloak SSO

    6. Negative

      Mark Nguyen, Retool (GitHub profile)

      issue: open-webui stopped streaming reasoning tokens, and often does not display the thought block before or after toolcallsGitHub issue

      Open WebUI stopped showing streamed thinking for GLM-5.2, Kimi-K2.6 and gpt-oss-120b, and thought blocks vanish during streaming until a refresh.

      Published Jul 4, 2026self-described: Chats with reasoning models such as GLM-5.2 and gpt-oss-120b

    7. Negative

      Christian Otto Stelter, Senior DevOps Engineer at PlusServer (GitHub profile)

      issue: delete_knowledge_by_id failsGitHub issue

      Knowledge bases created on 0.6.28 throw a validation error when deleted on 0.8.12.

      Published Apr 16, 2026self-described: Knowledge bases created on 0.6.x and deleted on 0.8.x

    8. Negative

      Aslan Vatsaev, Lead GenAI software engineer at Edenred (GitHub profile)

      issue: Microsoft SSO signup doesn't work after 0.6.41 updateGitHub issue

      After the 0.6.41 update new users could no longer sign up through Microsoft SSO.

      Published Dec 16, 2025self-described: Microsoft SSO sign-up for new users

    Open them in the record
  3. Performance at ScaleAll 7 sources on it raise it as a concernMemory growth, slow search, and CPU starvation as users, chats, and uploads grow.

    Counted for Leaders and teams rolling it out.

    1. Negative

      clg-e2e-tester-lang, GitHub user running a multi-instance deployment

      issue: 0.12.0 multi-instance Redis setup: containers grow to 8-11 GB RAM under chat load (0.11.4 stable)GitHub issue

      After upgrading a three-replica deployment to v0.12.0, containers grew from about 2 GB to 8 to 11 GB of RAM under chat load, and rolling back to v0.11.4 restored stability.

      Published Oct 12, 2026self-described: Three replicas per host sharing one Redis, with several users and tabs active

    2. Negative

      Erik, Tech Lead AI and Senior Solution Architect at HUK Coburg (GitHub profile)

      issue: Analytics Daily Endpoint fails when to many dataGitHub issue

      The analytics daily endpoint returns HTTP 500 once there are many requests and messages, so the team built its own workaround that queries it in 30-day slices.

      Published Jul 22, 2026self-described: An Open WebUI deployment on Kubernetes with heavy usage

    3. Negative

      Jian Guo, KION GROUP IT (GitHub profile)

      bug: SentinelRedisProxy re-resolves Sentinel master on every op (new pool per call) → Redis connection churn + event-loop stalls/liveness kills under load (v0.10.2)GitHub issue

      In production with about 40,000 users on Redis Sentinel, Open WebUI resolves the master and opens a new connection pool on every Redis operation, which caused about 6.9 new connections a second, event-loop stalls and liveness kills.

      Published Jul 20, 2026self-described: A Kubernetes deployment with Redis Sentinel

    4. Negative

      Jan Kessler, Johannes Gutenberg-Universität Mainz (GitHub profile)

      issue: YDocManager's remove_user_from_all_documents throws on websocket disconnect (with Redis Sentinel)GitHub issue

      With Redis Sentinel, closing a browser tab throws errors on websocket disconnect and the session likely stays in the session pool.

      Published Dec 23, 2025self-described: A university instance on Redis Sentinel

    5. Negative

      Michael, MLOps Engineer at MagnitTech (GitHub profile)

      issue: Severe TTFT increase when accessing vLLM through Open WebUIGitHub issue

      Through Open WebUI's API, time to first token from vLLM rises to about 5 to 6 seconds, against about 600 ms calling vLLM directly with the same model and hardware.

      Published Dec 17, 2025self-described: Open WebUI's API in front of a vLLM backend

    6. Negative

      Taylor Wilsdon, director of engineering at Yelp (GitHub profile)

      issue: New OAuth 2.1 Streamable HTTP MCP server Eetries do not propagate across multi-node setupsGitHub issue

      In a multi-node cluster, a newly added OAuth 2.1 MCP tool server works only on the node it was created on.

      Published Dec 12, 2025self-described: A multi-node cluster with Redis config sync

    7. Negative

      Boris Bakchiev, Morris Technology (GitHub profile)

      issue: PostgreSQL search crashes on invalid Unicode surrogate pairs in chat dataGitHub issue

      Chat search on PostgreSQL crashes with a 500 when stored chats contain invalid Unicode surrogate pairs.

      Published Nov 27, 2025self-described: Chat search on a PostgreSQL-backed instance

    Open them in the record
  4. Setup & Operations7 of 8 sources on it raise it as a concernThe work of hosting, updating, securing, and tuning Open WebUI on your own infrastructure.

    Counted for Leaders and teams rolling it out.

    Raised as a concern, 7

    1. Negative

      Roman (moltar), ScaleLeap (GitHub profile)

      bug: pgvector client ignores DATABASE_ENABLE_IAM_TOKEN_AUTH, so RDS IAM auth and VECTOR_DB=pgvector cannot be used togetherGitHub issue

      With RDS IAM token auth the main database connects, but the pgvector client still asks for a password, so the container exits and the deployment never becomes healthy.

      Published Jul 30, 2026self-described: Open WebUI on Amazon RDS for PostgreSQL with IAM token auth and pgvector

    2. Negative

      cono, Chartbeat (GitHub profile)

      issue: runAsNonRoot: true breaks on v0.11.0GitHub issue

      A Kubernetes deployment on the latest tag started failing with runAsNonRoot because a cached model file in the image belongs to root with 0600 permissions.

      Published Jul 28, 2026self-described: A Kubernetes deployment that followed the latest tag

    3. Negative

      Dāvis Pazars, AI Engineer at Mikrotik (GitHub profile)

      issue: admin panel OAuth config is saved but never applied; SSO never activates without env varsGitHub issue

      While setting up Keycloak SSO in production, OAuth settings saved in the admin panel were never applied, so SSO did not activate without environment variables.

      Published Jul 9, 2026self-described: A production instance being set up with Keycloak SSO

    4. Mixed

      pablooliva, led a company-wide self-hosted AI rollout

      Our AI Rollout Started With People, Not ProcessesReddit post

      Chose LibreChat over Open WebUI for a company-wide rollout, mostly because it was lighter to run for their needs.

      Published Jun 22, 2026self-described: A company-wide self-hosted AI rollout

    5. Negative

      Aslan Vatsaev, Lead GenAI software engineer at Edenred (GitHub profile)

      issue: Microsoft SSO signup doesn't work after 0.6.41 updateGitHub issue

      After the 0.6.41 update new users could no longer sign up through Microsoft SSO.

      Published Dec 16, 2025self-described: Microsoft SSO sign-up for new users

    6. Negative

      Matthias Weise, intercorp (GitHub profile)

      issue: Groups not imported from MS Entra IDGitHub issue

      Users from Azure security groups can sign in through Entra ID, but their groups are never imported into Open WebUI.

      Published Dec 16, 2025self-described: An internal instance signing in through Microsoft Entra ID

    7. Negative

      Tobias Genannt, q.beyond (GitHub profile)

      issue: A users groups aren't always updated on OAuh loginGitHub issue

      With OAuth group management on, a user's groups update only on the second login after a role change in the identity provider.

      Published Nov 25, 2025self-described: OAuth group management

    Discussed without concern, 1

    1. Mixed

      FamDev, r/selfhosted member evaluating for a production deployment

      LibreChat vs Open WebUI for secure cloud deployment (multi-tenant, sensitive data)Reddit post

      Weighs LibreChat against Open WebUI for a multi-tenant production deployment holding legal and healthcare data, with Keycloak OIDC and one VM per tenant.

      Published Oct 10, 2025self-described: A planned deployment in a national public cloud for legal and healthcare data with Keycloak OIDC

    Open them in the record

Where the evidence agrees

Statements this group's sources agree on, then the ones close to agreement.

For leaders and teams rolling it out, no statement reaches 5 sources from 3 authors.

Where it disagrees

Questions the sources split on, with the count on each side.

For leaders and teams rolling it out, no question reaches 5 sources from 3 authors, with 2 on each side.

    The evidence

    Whose experience this is

    The three groups, then every practitioner by the context they work in, and how emphasis changes with scale.

    Three groups drawn from the same sources. Choose a group to select whose experience counts. Within that group, each author counts once in the practitioner sentiment, with their latest view. Signals open on Leaders and teams rolling it out.

    • Leaders and teams rolling it out

      35 sources. This group counts teams and departments using the tool together, and the leaders deciding its rollout.

    • Individual users

      43 sources. This group counts people using the tool for their own work.

    • All users

      78 sources. This gives the broadest read, but combines individual use with team and company rollouts that can reach different conclusions.

    78 sources from practitioners, by the context they work in. Filled rows count for this group.

    1. Individual userOne person using it for their own work43 sources

      Emphasizes Local models at home, integrations, and the branding license

    2. Small team2 to 10 people sharing it5 sources, counted here

      Emphasizes Internal chat for staff on company hardware, and upgrade rollbacks

    3. DepartmentA department, or a named company's team25 sources, counted here

      Emphasizes No named team account in GILD's October 2026 search of GitHub, Hacker News, and Reddit beyond the small-team ones; ask Open WebUI for a reference customer of your size

    4. IT & leadershipIT and business leaders deciding the rolloutNo sources from this setting yet
    5. Organization-wideCompany-wide rollout5 sources, counted here

      Emphasizes A company-wide rollout that chose LibreChat because it was lighter to run

    What changes with scale. Individual users run Open WebUI at home in front of local models and value its search and tool integrations, and object to the branding license. Teams that serve staff from it report upgrade regressions under load, and one company-wide rollout chose a lighter interface.

    Where the sources come from

    Where this group's sources were published.

    Counted for Leaders and teams rolling it out, from 35 sources. Change group

    40 sources for this group, 5 of them documentation

    • Practitioner Communities34, 85% of 40 sources
    • Product Documentation5, 13% of 40 sources
    • Blogs & Reviews1, 3% of 40 sources

    Earlier evidence remains when it still applies. Records tied to a release that later patches may fix carry Current until a fix ships.

    See sources by origin

    The record

    Who each source is, how it knows, whether it still applies and what it counts toward.

    Newest first, on its own page. Every count above opens its sources there.

    Read all 83 sources

    About this read

    What changed, and how we count

    What changed

    • Nov 1, 2026: six practitioner accounts were added, each with its author's role or company from the author's own profile. Leaders and teams read −74, individual users −18 and all users −45.
    • Nov 1, 2026: since Oct 30 the page prints one vote per author, and a figure given on the weighted reading is the second view. Leaders and teams read −73, individual users −21 and all users −44.
    • Oct 30, 2026: a second-model check removed a Reddit post that names Open WebUI as an option with no reason given. A GitHub report of a desktop app that could not reach an internal server now reads as a fresh install, so it no longer counts as an upgrade regression and counts toward no figure. FORTH-IESL's card dates its repository to June 25, 2025. All practitioners now count 68 sources: 14 positive, 10 mixed and 44 negative.
    • Oct 28, 2026: first edition, built from the Hacker News, Reddit, GitHub, and blog accounts GILD's research missions stored on October 28, 2026, favoring sources that name their author's role, company, or project.
    • Every account links to its public source and names its author and publication date.
    • A finding shows only when at least 5 sources from 3 different authors discuss it. A disagreement also requires at least 2 sources on each side.
    • Counts people who describe their own use or evaluation of Open WebUI; security advisories and vendor case studies are excluded.
    • Checks the license, audit log, sign-in, and retention findings against Open WebUI's documentation and license file on the review date.
    • Oct 28, 2026: adds 9 Hacker News, Reddit and GitHub sources from GILD's research ledger, 5 with the passage they quote, on the license change, local models and a networking regression. On the weighted reading, individual users move from Mixed at -19 to Negative at -23 and all practitioners from -48 to -47; leaders and teams stay at -76. A competing project's author is listed without counting.

    Method

    A running review of what people using Open WebUI at work report, from individual users to company-wide rollouts. Each finding links to its sources, and each conflict shows both sides.

    Counts cover only the sources GILD reviewed.

    Who counts

    Leaders and teams rolling it out
    Small team, Department, IT & leadership, Organization-wide
    Individual users
    Individual user
    All users
    Everyone in the leaders and teams and individual users groups

    Choose a group to select whose experience counts. Within that group, each author counts once in the practitioner sentiment, with their latest view. GILD files each source in a group from how the account describes its author. A role or employer marked self-described is what the source states about themselves. Documentation checks facts for every group and never counts toward sentiment.

    How the numbers work

    • Overall signal. Positive votes minus negative ones, per 100 votes from the sources that take a side. Each author counts once, with their latest view, whoever they are and wherever they posted. The older weighted reading, where accounts GILD matched to a named person count three times when GILD lists the author among IT and business leaders and twice otherwise, is shown beside it as a second view. Where an author wrote more than one source, the line beside the split gives the votes, one per author, so the score follows from it. When one author's sources from the same day disagree, that author counts as mixed, and a half point rounds away from zero. Sources with no opinion are listed and not counted. Strong positive is +50 or higher, positive +20 to +49, mixed −19 to +19, negative −20 to −49, strong negative −50 or lower.
    • Weighted reading, second view. Counted the older way, where an account GILD matched to a named person counts two or three times, leaders and teams read −76 strong negative (method sentiment/S1). GILD printed that number as "GILD score" until October 29, 2026; most of those matches rest on a name or a self-described role.
    • Method change, Oct 30, 2026. GILD changed how practitioner sentiment counts, to one vote per author. Weighted, it read −76 Strong negative; with one vote per author it reads −73 Strong negative. No evidence changed.
    • Unscored. A group gets a score only with 20 sources from 15 authors. Below that, one source moves the score about 5 points, so the read says "Unscored until 20 sources from 15 authors" and shows its counts.
    • Independence. A source whose author works for the vendor, for one of its partners or programs, or for a competitor, and a page the vendor published or ran, is listed with that tie and counts toward nothing. One author counts on at most two records per product. The line under the score says how many authors and how many separate discussions the counted sources come from: comments in one thread are one discussion.
    • Praise and concerns. How many of the sources that discuss a theme praise it or raise it.
    • Consensus. A statement joins when 20% of the group's sources support it and fewer contradict it. Contradicting sources are counted separately. Below that line a statement shows as building. At 40% or more it reads Strong agreement; below, Recurring point.
    • Disagreements. The count on each side. GILD names no winner and gives no share of all users.
    • Minimum evidence. A finding needs 5 sources from 3 authors; a disagreement also needs 2 on each side. Smaller counts stay in the table below, marked under the minimum.

    Labels on a source

    A source's date and whether it still applies are separate: a recent post can describe an old version, and an old one can still hold.

    Documented
    Stated in official documentation.
    Reported
    A practitioner's account of their own use.
    Measured
    Backed by the source's own measurements, such as a comparative test or tracked team metrics.
    GILD analysis
    GILD's check of a claim against official documentation.
    Current
    Describes the product as it is now.
    Still applicable
    Older, and the behavior or lesson still holds.
    Needs a recheck
    May depend on a plan, version or setting that changed since it was written. It keeps counting until GILD rechecks it, since the rest of the account usually holds, and its card says so.
    Out of date
    No longer accurate. Kept in the record; counts toward nothing current.

    Flagged for a recheck, of the sources that take a side: leaders and teams 0 of 35, individual users 0 of 39, all users 0 of 74.

    Limits

    • These figures describe reviewed sources; they do not represent all Open WebUI users. GitHub issues supply 37 of the 78 sources and are bug reports, which tilt toward problems; many come from teams running Open WebUI for an organization, so the leaders view reads more negative than the builders view. Hacker News supplies 27, and its threads about competing chat interfaces draw critics of the license. Open WebUI's own customer stories are kept out of the count.
    • Sources cover Open WebUI from the April 2025 license change (v0.6.6) to v0.12.x in October 2026. Several October 2026 GitHub issues concern v0.12.0, released October 10, 2026, and may be fixed in later patches.

    Every count, and the sources behind it

    12 findings for 3 groups

    Each row opens its sources for the group you are reading.

    FindingLeaders and teams rolling it outIndividual usersAll usersSources
    Current readCurrent sentiment2 positive, 5 mixed, 28 negative13 positive, 6 mixed, 20 negative15 positive, 11 mixed, 48 negativeSources
    PraiseSelf-Hosted Control1 of 1 positive (under the minimum)6 of 6 positive7 of 7 positiveSources
    PraiseFront End for Local Models1 of 1 positive (under the minimum)8 of 9 positive9 of 10 positiveSources
    PraiseSearch, Tools & MCP1 of 5 positive8 of 8 positive9 of 13 positiveSources
    PraiseAny Model Behind One Interface1 of 1 positive (under the minimum)3 of 3 positive (under the minimum)4 of 4 positive (under the minimum)Sources
    ConcernLicense & Branding Terms0 of 0 raise it (under the minimum)6 of 6 raise it6 of 6 raise itSources
    ConcernUpgrade Regressions8 of 8 raise it9 of 9 raise it17 of 17 raise itSources
    ConcernPerformance at Scale7 of 7 raise it5 of 5 raise it12 of 12 raise itSources
    ConcernFeature Gaps14 of 14 raise it7 of 7 raise it21 of 21 raise itSources
    ConcernSetup & Operations7 of 8 raise it3 of 5 raise it10 of 13 raise itSources
    DisagreementWhen people compare Open WebUI with other chat interfaces, which do they keep?Kept Open WebUI 2, Chose another tool 2 (under the minimum)Kept Open WebUI 1, Chose another tool 1 (under the minimum)Kept Open WebUI 3, Chose another tool 3Sources
    Current readEvidence mix40 sources48 sources83 sourcesSources

    Fact checks

    GILD's checks of claims against official documentation, kept apart from the source counts.

    • Self-Hosted Control. Open WebUI's security page states that data stays within your infrastructure by default unless you configure external model providers, and that you own the database and its retention policies. Enterprise security, checked Oct 28, 2026
    • Search, Tools & MCP. Open WebUI documents its Ollama integration: models served by a connected Ollama instance appear in the model selector automatically. Ollama, checked Oct 28, 2026
    • Search, Tools & MCP. The enterprise security page lists identity integration through SSO, LDAP, and role-based access control. Enterprise security, checked Oct 28, 2026
    • Search, Tools & MCP. The v0.12.0 release notes cover integrations with Amazon Bedrock and OpenRouter, including a model ID for GPT-6 Sol on Bedrock and a fix for tool calls on models served through OpenRouter. Open WebUI v0.12.0 release notes, checked Oct 28, 2026
    • Any Model Behind One Interface. DEFAULT_MODELS sets the model or models preselected on a new chat, and Ollama models appear in the model selector with no configuration. Environment configuration, checked Oct 28, 2026
    • License & Branding Terms. The license lets a deployment remove or alter the branding only with 50 or fewer end users in a rolling 30-day period, with written permission, or under an enterprise license; code contributed up to v0.6.5 stays under BSD-3. License, checked Oct 28, 2026