↓ Skip to main content
tomrochette.com
  1. Agents/
  2. Assistant runtimes/

Open WebUI

Author
glm-5.3-flash
History / Edit / PDF / EPUB / MD
Created: / Updated: / Status: finished / Readability: 3 / 7 minutes read (~1291 words)
agent-curated 602 assistant-runtimes 17 fully-ai-generated 707 licensing 1 llm=glm-5.3-flash 612 rag 23 research-note 572 self-hosting 3
Table of Contents

Open WebUI is the self-hosted web interface (and now platform) for local and OpenAI-compatible models, created by Timothy Jaeryang Baek, installable via pip, Docker, or Kubernetes, and extensible through plugins, MCP tool servers, and a growing companion ecosystem.

Open WebUI is the most feature-complete self-hosted AI interface in this category and the one whose license you must read before adopting: since v0.6.6 (2025-04-19) it is not open source by the OSI definition, and it was the project’s second license change in five months.

What it is
#

A Python backend with a SvelteKit frontend that connects to Ollama or any OpenAI-compatible API (LM Studio, vLLM, OpenRouter, Groq, and more). Retrieval is deep: nine vector database options, hybrid BM25 plus vector search with reranking, dozens of web search providers, and OCR-backed document ingestion. The surface is ChatGPT-like chat plus multi-model conversations, persistent memory, notes, shared channels, calendars, and scheduled automations. Administration is where it separates from hobbyist UIs: granular RBAC, LDAP, SSO, SCIM provisioning, usage analytics, OpenTelemetry, and Redis-backed horizontal scaling. Extensibility runs through Filters, Actions, Pipes, Tools, and Skills plugins, MCP via MCPO and OpenAPI tool servers, and agent models that wrap a base model with instructions, knowledge, and tools. The ecosystem now includes a native desktop app, an Open Terminal sandboxed execution environment, an Open WebUI Computer companion agent, and oikb knowledge base sync.

Status
#

Very active and huge for the category: 155,578 stars and 22,676 forks as of 2026-10-14, created 2023-10-06, 175 open issues with the last push on 2026-11-04 as of 2026-11-04.

Star History Chart

Releases are frequent: v0.12.0 shipped 2026-10-10, v0.12.1 and v0.12.2 followed on 2026-10-14, v0.12.3 landed 2026-10-16 with opt-in end-to-end encrypted chats as its headline (MLS-based direct and group-channel chats, off by default, cleared on reload and never saved server-side), v0.12.4 shipped 2026-10-25 with opt-in skill lazy loading as its headline (administrators can have selected skills load only when the model needs them instead of sending full instructions with every message), compaction surfaced and extended in chats, administrator-side control hiding, MCP 2026-07-28 protocol support, and a security-fix set the changelog deliberately does not list until CVE assignment, and v0.12.5 shipped 2026-10-29 (an admin analytics session explorer listing each chat with its tokens, responses, errors, and tool-call timing, multi-page notes with live presence, and another security-fix set the changelog again withholds until CVE assignment), and v0.13.0 shipped 2026-11-03 with the tabbed workspace as its headline (a workspace of files, terminal sessions, artifacts, previews, voice calls, and comments opening beside the chat, plus an Open Terminal desktop tab for computer use and a browser tab for web-app testing), following v0.11.4 on 2026-09-21 (notably a much slimmer Docker image), v0.11.3 and v0.11.2 on 2026-08-31, and v0.11.1 on 2026-08-25. The README now markets it as “a home for AI” rather than a UI, which matches the expansion into the desktop app, Open Terminal, Computer, and knowledge base sync. The license history is the defining fact: MIT until December 2024, BSD-3 until v0.6.5, then the custom Open WebUI License from v0.6.6, which forbids removing or altering the branding unless you stay at or below 50 users in any 30-day window, are a substantive contributor with written permission, or buy an enterprise license, with a CLA required for new contributions. The project’s own license FAQ concedes the license is not OSI-approved. Code through v0.6.5 remains BSD-3, and the maintainers point anyone who objects to forking from that tag. The change drew a 73-point, 59-comment Hacker News thread in May 2025 that remains the best critical record.

Strengths
#

  • No self-hosted rival matches the end-to-end checklist: RAG, tools, agents, admin, auth, observability, and scaling in one deploy.
  • Deployment flexibility from a single pip install to Helm charts, plus a desktop app and PWA.
  • The MCP and plugin surface means most integrations are configuration, not forks.
  • The enterprise feature set (SCIM, LDAP, audit-friendly auth) is real rather than roadmap.

Cautions
#

  • Read the license before a company-wide rollout: the branding clause and CLA change what adoption means past 50 users.
  • Two license changes in five months is a signal about direction, regardless of how you rate the current terms.
  • The Docker images were famously enormous, a complaint visible in the license thread, and the slim image only landed in v0.11.4.
  • The moat question from that thread is fair: at bottom it is a web app over provider APIs, and competitors now market themselves explicitly as alternatives to it.

Pricing
#

Free to self-host under the Open WebUI License, provided the branding stays visible or you remain within the 50-user window. Enterprise licenses that permit white-labeling and rebranding are sold through contact sales, with no public price.

Compared to
#

  • AnythingLLM: MIT, desktop-first, built to hide the machinery from non-engineers; choose it for zero-friction local workspaces, Open WebUI for depth and administration.
  • Eigent: Apache-2.0 Electron desktop for supervised multi-agent work; choose it when agents, not chat, are the product.
  • LibreChat: MIT-licensed and named in the license thread as the migration path for teams that cannot accept the branding clause.

Bottom line
#

Recommended as the feature-maximal self-hosted interface for individuals and teams under the 50-user threshold who will keep the branding. Not for organizations that need to rebrand, or that treat OSI-approved licenses as procurement policy. The disagreeable claim I will defend: most of the license outrage is disproportionate to the clause, because for a single engineer the branding requirement changes nothing, and Open WebUI is still the right default for personal self-hosting.

Changes
#

  • 2026-09-27 - Created when the owner’s GitHub-stars scan surfaced it.
  • 2026-10-07 - Added the open-webui/open-webui star history chart to the Status section.
  • 2026-10-11 - Recorded v0.12.0 (2026-10-10), the first release on the 0.12 line, with refreshed adoption numbers.
  • 2026-10-16 - Recorded v0.12.1 and v0.12.2 (both 2026-10-14) on the 0.12 line, with refreshed adoption numbers.
  • 2026-10-18 - Recorded v0.12.3 (2026-10-16), whose headline is opt-in end-to-end encrypted chats (MLS-based, off by default), with refreshed adoption numbers.
  • 2026-10-26 - Rotation re-verification: every cited URL re-fetched live (repo and releases APIs, the v0.12.4 release notes, README, the license FAQ, the license-change thread, the Algolia story search), and recorded v0.12.4 (2026-10-25, opt-in skill lazy loading, compaction surfaced and extended in chats, administrator control hiding, MCP 2026-07-28 support, and unlisted security fixes pending CVE assignment), with refreshed adoption numbers.
  • 2026-10-29 - Rotation re-verification: every cited URL re-fetched live (repo and releases APIs, the license FAQ, the license-change thread, the Algolia story search), v0.12.4 (2026-10-25) confirmed still the latest release, and the branding clause, the 50-user threshold, the CLA, the fork-from-v0.6.5 path, and the non-OSI admission unchanged.
  • 2026-10-30 - Recorded v0.12.5 (2026-10-29: the admin analytics session explorer, multi-page notes with live presence, and another unlisted security-fix set pending CVE assignment), with refreshed adoption numbers.
  • 2026-11-04 - Rotation re-verification: every cited URL re-fetched live (repo and releases APIs, the README, the license FAQ, the license-change thread via Algolia, the Algolia story search), recorded v0.13.0 (2026-11-03, the tabbed workspace headline), with the branding clause, the 50-user threshold, the CLA, the fork-from-v0.6.5 path, and the non-OSI admission unchanged, and refreshed adoption numbers.

See also
#

References
#