Self-Hosted / Projects / Open-WebUI

Open-WebUI
StableSpecs verified September 23, 2026 · against vv0.11.4
Overview
Self-hosted AI interface for Ollama, OpenAI-compatible APIs, RAG, and team chat.
Open WebUI is a self-hosted AI interface that gives individuals and teams one chat workspace for Ollama, OpenAI-compatible APIs, and other model providers.
Why people choose it
It is a practical choice when you want a browser-based chat experience without tying the interface to one hosted provider. The official docs cover Ollama, OpenAI, Anthropic, vLLM, and other connections, along with model management, conversation history, and user administration.
What is included
The project supports Docker, Python, Kubernetes, and a desktop app. Depending on the image and configuration, it can support document uploads, retrieval-augmented generation (RAG), web search, tool calling, voice features, and Open Terminal. These capabilities can require an embedding provider, external services, or the standard image rather than the slim image.
Deployment requirements
Docker is the recommended path for most deployments. Persist `/app/backend/data` and set a stable `WEBUI_SECRET_KEY`; the official quick start warns that the volume contains chats, users, and settings. The standard image includes more local ML and document-processing dependencies, while `main-slim` is smaller but delegates several features to external providers.
Main tradeoffs
Open WebUI is an interface, not a model by itself. You still need Ollama, another local runtime, or a hosted API provider. RAG, voice, web search, and agent features add configuration and resource requirements, and a public deployment needs normal authentication, updates, backups, and network hardening.
Best fit
Choose it if you want a polished self-hosted ChatGPT-style workspace across local and hosted models, especially when you need more than a single-user command-line runtime. A simpler API-only setup may be better if you only need programmatic inference.
Interface previews
Screenshots of the Open-WebUI interface.
Feature support
| Feature | Support |
|---|---|
| Ollama and local model connectionsOfficial docs provide a dedicated Ollama connection path for local models. | Supported |
| OpenAI-compatible and other provider connectionsOfficial docs list OpenAI, Anthropic, vLLM, and other provider connections. | Supported |
| Docker deployment with persistent application dataThe official quick start recommends Docker and persistent `/app/backend/data` storage. | Supported |
| Document uploads and RAG knowledge basesSupported, but embeddings, vector storage, and document extraction depend on the image and configured providers. | Partial support |
| Multi-user accounts and administrationThe application stores users and settings in its persistent data volume and provides administration features. | Supported |
| Web search, tool calling, and agent workflowsAvailable through configured providers, tools, extensions, or Open Terminal; these are not all zero-dependency features. | Partial support |
| Voice input and spoken repliesSupported through local or external speech services depending on the selected image and configuration. | Partial support |
Community signals
- Stars
- 154k
- Forks
- 22.6k
- Open issues
- 170
- Last commit
- 23h ago
- Latest release
- v0.12.0
- Repo created
- Oct 2023
Includes open pull requests
2d ago
Refreshed nightly from the GitHub API.
Questions
What is Open WebUI used for?
Open WebUI provides a self-hosted browser interface for chatting with Ollama, local models, and OpenAI-compatible or other hosted APIs.
Is Open WebUI a self-hosted ChatGPT alternative?
Yes, at the interface layer. It offers a ChatGPT-style workspace, but you must connect a local model runtime such as Ollama or a hosted API provider.
Does Open WebUI require Ollama?
No. Ollama is a common pairing, but the official docs also support OpenAI, Anthropic, vLLM, and other providers.
Can Open WebUI run with Docker?
Yes. Docker is the recommended deployment path for most users. Persist `/app/backend/data` and set a stable `WEBUI_SECRET_KEY` before exposing the service.
Does Open WebUI support RAG and document uploads?
Yes, but the exact requirements depend on the image. Embeddings, vector storage, and document extraction may need local components or external providers; the slim image omits several bundled ML dependencies.
What is the main Open WebUI tradeoff?
Open WebUI gives you a flexible self-hosted interface, but it is not the model runtime itself. You remain responsible for model hosting or API costs, configuration, updates, backups, and security.
support // the lab
Found this write-up useful?
If it saved you time or a rebuild, you can support more practical homelab guides.