Open WebUI

Open WebUI is a self-hosted web interface for running local and cloud LLMs without sending data to third-party servers. Created by Tim Jaeryang Baek in September 2023 as "Ollama WebUI," renamed in January 2024 to reflect broader backend support, the project has grown to 134,000 GitHub stars and a 355,000-member community by April 2026. It runs on Docker or Kubernetes and puts a ChatGPT-style interface in front of Ollama, any OpenAI-compatible API, and dozens of commercial providers simultaneously. Tim Baek incorporated Open WebUI, Inc. in September 2024 after joining Mozilla's inaugural Builders Accelerator cohort.

The current release, v0.9.2 (April 24, 2026), ships with RAG document search across nine vector databases (ChromaDB, Qdrant, Milvus, and others), voice and video calling, a Pipelines framework for Python-based middleware, multi-user role-based access control, LDAP and OIDC SSO, SCIM 2.0 provisioning, OpenTelemetry observability, per-user model quotas, web search via SearxNG, and a tool/function plugin system. For individuals, it is a private ChatGPT replacement. For teams, it is a full internal AI platform that keeps all inference on-premises.

What Open WebUI actually does in April 2026

At its core, Open WebUI is a browser-based admin and chat layer that sits in front of your model backends. You point it at a running Ollama instance or supply any OpenAI-compatible endpoint, and it handles the rest: conversation threading, system prompt management, model switching mid-conversation, file and image uploads, and a shared model library across your organization.

The Pipelines framework is where the platform becomes genuinely extensible. Pipelines are Python scripts that intercept requests and responses: you can attach rate limiters, usage loggers (Langfuse, Datadog), content filters, prompt injection guards, or custom preprocessing chains without modifying the core codebase. As of v0.9.2, Pipelines run as a separate service that Open WebUI routes traffic through.

RAG (Retrieval-Augmented Generation) is built into the upload flow. Drop a PDF or paste a URL and Open WebUI chunks, embeds, and stores it in your configured vector database. Supported embedding models include nomic-embed-text locally or any OpenAI-compatible embeddings API. The knowledge base system lets you build persistent document collections that persist across conversations and can be shared across users.

For team deployments, the admin panel covers user provisioning (local accounts, Google/GitHub SSO, LDAP, Azure AD), group-based model access, per-user token quotas, usage dashboards, and audit logging. SCIM 2.0 support means enterprise identity providers can push user and group changes automatically.

Where Open WebUI sits versus LibreChat and AnythingLLM

These three projects define the current self-hosted LLM UI market. The mechanical differences matter for choosing the right one.

LibreChat (github.com/danny-avila/LibreChat, 33,900 stars) is built for multi-provider chat switching in a single interface. Its architecture is multi-container Docker Compose running the app server, MongoDB for conversation storage, and Meilisearch for full-text RAG indexing alongside vector embeddings. The auth system is the deepest of any alternative: local accounts, LDAP, Google, GitHub, Discord, OpenID, Azure AD, and AWS Cognito with per-user token credit tracking. LibreChat holds a full MIT license with no branding restrictions. Its weakness is setup complexity: you manage three containers versus Open WebUI's single image, and the UI is less polished for pure local LLM use. LibreChat was acquired by ClickHouse in 2025/2026.

AnythingLLM (github.com/Mintplex-Labs/anything-llm, 54,000 stars) treats RAG as its central design principle rather than an add-on. Every workspace is an isolated RAG environment with its own documents, LLM config, and conversation history. The Visual Agent Flows canvas lets non-technical users chain API calls, LLM instructions, and file operations without writing code. AnythingLLM ships a native Electron desktop app with zero-config embedded LanceDB, meaning no Docker required for single-user setups. It supports 50+ document types including GitHub repos, YouTube transcripts, and Confluence pages. AnythingLLM uses MIT license throughout. Its weakness: desktop mode is single-user only; teams need the Docker deployment.

The positioning summary: Open WebUI wins on chat-first UX, fastest Ollama setup, most active development cadence, and multi-user RBAC depth. LibreChat wins on auth system completeness and license purity for commercial compliance. AnythingLLM wins on document-heavy RAG workflows and the no-code agent builder.

"If it's OSI approved it means I don't have to hire a lawyer in order to decide what I can do.", simonw (Simon Willison), Lobsters, 2025

The license change and what it means for your deployment

In late 2024, Open WebUI shipped v0.6.6 with a custom "Open WebUI License" replacing the prior BSD-3-Clause terms. The change added a branding protection clause: any deployment of 51 or more users within a 30-day rolling period must preserve the "Open WebUI" name and branding. Commercial white-labeling, whether building a SaaS product on top of Open WebUI or deploying it under your own brand name, requires a separate enterprise license with pricing that is not publicly listed.

The timing was notable. Open WebUI had already changed from MIT to BSD-3 just five months earlier, also without announcement. The v0.6.6 change generated a long Hacker News thread (id=43901575) and a parallel Lobsters thread with several hundred comments between them. The reaction was not fringe: it included well-known developers and open-source advocates.

"This 'little addition' will likely make it non-Open Source according to standard definition.". PeterZaitsev, Hacker News, April/May 2025

"The whole point of open-source software is that it can be used for any purpose, including reselling it.. If you don't want that, you are against open source. Which is fine, but then I don't think you should be calling your program 'Open' WebUI. It is deceptive and dishonest to claim your license is something it simply is not.", r/LocalLLaMA community member, Reddit, 2025

The practical impact: personal use, home labs, and teams under 50 active users per month are completely unaffected and remain free. The restriction bites commercial operators: anyone building a paid product, managed service, or white-labeled enterprise deployment faces legal ambiguity without paying for an enterprise license at an undisclosed price. Developers who need OSI-certified open-source for internal compliance policies cannot use v0.6.6+ at all. The last fully permissive release, v0.6.5, is available on GitHub for those who want to fork from a clean baseline.

What the deployment and upgrade reality looks like

For a new install, Open WebUI is genuinely fast to get running. A single Docker command pulls the image and binds to port 3000; if Ollama is already running locally, the UI connects automatically. The v0.9.2 image is larger than early releases but still manageable on a standard VPS.

Production operation is harder. Open WebUI's rapid development cadence, roughly weekly releases through much of 2025 and 2026, has meant that upgrades sometimes break configurations in place. Documented incidents include v0.8.0 causing startup failures on existing deployments, v0.7.2 breaking API access tokens, and v0.6.3x requiring container restart times of several hours for some users. The project's GitHub issue tracker reflects these patterns clearly across multiple versions.

Browser resource usage is another operational consideration. Generating responses from a remote Ollama instance can push one CPU core to 100% utilization in Chrome. RAM consumption grows incrementally over extended sessions. Large knowledge base deployments, those with 60,000 or more files, experience the /api/models endpoint returning 43-50MB responses that include all file UUIDs, causing perceptible slowdowns particularly on mobile browsers.

For home lab and small team use where downtime tolerance is reasonable, these friction points are manageable. For production deployments where reliability SLAs matter, the upgrade cadence requires a more conservative pinning strategy and a staging environment before applying updates.

Who Open WebUI is built for

Open WebUI is the right choice for local LLM enthusiasts who want a polished, actively maintained interface without building one themselves. It is also a strong choice for small-to-medium teams deploying internal AI access: the RBAC, SSO, and quota systems cover most enterprise requirements without requiring commercial AI vendor relationships. Privacy-first organizations where data residency is non-negotiable will find it provides the infrastructure they need on standard server hardware. IT administrators comfortable with Docker who want a managed, extensible platform rather than a raw API benefit from the admin panel depth.

Skip Open WebUI if your primary use case is document-heavy RAG where retrieval quality is the core requirement: AnythingLLM's workspace model and visual agent builder are better suited. Skip it if you need a truly lightweight UI without operational overhead: the project has grown into a platform, and first-time setup now involves meaningful configuration decisions. Skip it if you need OSI-certified open-source for legal or compliance reasons: the v0.6.6+ license does not qualify, and forking from v0.6.5 means missing 18-plus months of active development. Skip it if you plan to build a commercial white-labeled product: the enterprise license path has no published pricing, and assuming it is free is a legal risk.

Getting started with Open WebUI

The fastest path is a single Docker command if Ollama is already running locally:

docker run -d -p 3000:80 --add-host=host.docker.internal:host-gateway \
  -v open-webui:/app/backend/data --name open-webui \
  --restart always ghcr.io/open-webui/open-webui:main

Navigate to http://localhost:3000 and create the first admin account. The first user to register becomes the admin automatically. From the admin panel, configure additional model backends under Settings > Connections, set up SSO under Settings > Auth, and configure RAG vector database preferences under Settings > Documents.

For team deployments, the recommended path is Docker Compose with an external PostgreSQL or SQLite database, an Nginx reverse proxy for HTTPS, and Ollama either co-located or on a separate inference server. The official documentation at docs.openwebui.com covers Kubernetes Helm charts for larger deployments. Pin to a specific release tag rather than the main or latest tag if production stability matters: the frequent release cadence means latest can carry breaking changes.