Skip to main content

Research

Open WebUI in Practice: What 42 Public Accounts Report

What 42 public accounts report about running Open WebUI: local models at home, internal chat at companies, the 2025 branding license, and upgrade regressions in v0.12.

Reading time
3 min read
Sources
14 cited

Key findings

  1. Integrations draw praise in 9 sources and local models in 9.
  2. Upgrade regressions are raised in 17 sources and feature gaps in 21, most of them GitHub issues from teams running it for an organization.
  3. 3 of the 6 counted sources that describe a choice of chat interface chose another tool or built their own; the other 3 kept Open WebUI.
  4. A company exposes Open WebUI to its staff on an on-prem server with Gaudi 2 cards for about US$20,000 in total, which it says six months of equivalent Claude usage would exceed.
  5. A three-replica deployment rolled v0.12.0 back to v0.11.4 after containers grew to 8 to 11 GB of memory, and another v0.12.3 user saw 12 to 35 GB during multi-step tool calling.

Of 74 counted public accounts from people running Open WebUI, 15 are positive, 11 mixed, and 48 negative. Individuals use it as the front end for local models and value its search and tool integrations, while companies stand it up for internal chat on their own servers. Critics object to the April 2025 branding license, and October 2026 GitHub issues report regressions in v0.12. GILD read English-language accounts published from May 2025 through October 2026.

Why people run it

Most accounts come from people running local models at home. They put Ollama or llama.cpp behind Open WebUI to get accounts, history, and model switching, and add a self-hosted SearXNG for web search or a Playwright MCP server for browsing.

Companies use it for internal chat. One team stood it up for internal chat and agent use and tested filter functions and MCP early. Another serves its staff from an on-prem server with Gaudi 2 cards, connected to internal resources, for about US$20,000 in total.

Where it breaks

October 2026 GitHub issues concentrate on v0.12: a three-replica deployment rolled back after memory grew to 8 to 11 GB, browser tabs reinitialised in a loop that saturated the server, and memory reached 12 to 35 GB during multi-step tool calling. Chat search on PostgreSQL took 5 to 15 seconds with a few thousand chats.

Feature gaps come up too: no Anthropic prompt caching, weak results from the SearX integration, and tools that run on the same server as the app.

The license

From v0.6.6 in April 2025, the Open WebUI License adds a branding clause to BSD-3: the branding may not be removed or altered on deployments above 50 users in a rolling 30-day period without written permission or an enterprise license. Code contributed up to v0.6.5 stays under BSD-3.

Hacker News commenters call the change no longer open source and compare it to Redis's Commons Clause. Some looked for or built alternatives, and one long-time user is frustrated that the branding cannot simply be bought out.

What to settle before choosing

Decide who hosts and upgrades it, and whether your own branding matters above 50 users. Then turn on SSO, SCIM, and the audit log, which is off by default, and write a retention schedule for the database you own.

Methodology

GILD read English-language public accounts from Hacker News, Reddit's r/selfhosted, GitHub issues on open-webui/open-webui, and a personal blog, published from May 6, 2025 to October 26, 2026 and stored as snapshots on October 28, 2026. Each account is a source in the Hub's Signals with its position on each theme, and every count here comes from those records. Open WebUI's own customer stories and security advisories are kept out of the count, and the license and configuration findings were checked against Open WebUI's documentation and license file on October 28, 2026.

Products in this piece

Sources

Official documentation
5
Public source
9
  1. Open WebUI docs: LicenseOfficial documentationdocs.openwebui.com
  2. open-webui/open-webui LICENSEOfficial documentationgithub.com
  3. Open WebUI docs: Enterprise securityOfficial documentationdocs.openwebui.com
  4. Open WebUI docs: Environment variable configurationOfficial documentationdocs.openwebui.com
  5. Open WebUI v0.12.0 release notes (Oct 10, 2026)Official documentationgithub.com
  6. open-webui/open-webui issue #32267: v0.12.0 multi-instance containers grow to 8-11 GB, v0.11.4 stable (Oct 12, 2026)Public sourcegithub.com
  7. open-webui/open-webui issue #32762: memory growth to 12-35 GB during multi-step tool calling in v0.12.x (Oct 19, 2026)Public sourcegithub.com
  8. open-webui/open-webui issue #32266: chat search on PostgreSQL takes 5-15 s per query (Oct 12, 2026)Public sourcegithub.com
  9. Hacker News: Open WebUI changed license from BSD-3 to Open WebUI license with CLA (May 6, 2025)Public sourcenews.ycombinator.com
  10. Hacker News comment on an Open WebUI front end for staff on a company Gaudi 2 server (Aug 26, 2026)Public sourcenews.ycombinator.com
  11. Hacker News comment on standing up Open WebUI for internal chat and agent use (Apr 28, 2026)Public sourcenews.ycombinator.com
  12. r/selfhosted: Our AI Rollout Started With People, Not Processes (Jun 22, 2026)Public sourcereddit.com
  13. Hacker News comment on missing Anthropic prompt caching in Open WebUI (May 27, 2026)Public sourcenews.ycombinator.com
  14. Steven Marks, totaldebug.uk: Self-hosted LLMs with Ollama and Open WebUI using Docker Compose (Jul 6, 2026)Public sourcetotaldebug.uk