Open WebUI Self-Hosted
Self-hosted AI chat and knowledge interface for local model servers and cloud APIs.
5 sources checked by an editor on · Product website ↗
Read this page as JSON or Markdown.
Deployment terms: BYOC · control plane · data plane · private offer
· Open requirements shortlist · Estimate operating costs
Compare this listing with another →
What lands where
Supplied by
Vendor or project
Official Docker image, Python installation or Kubernetes deployment.
Runs in
Documented customer environment
Customer-operated web application and conversation storage connected to model providers
- AWS: Customer cloud account
- Azure: Customer cloud account
- Google Cloud: Customer cloud account
- AWS
- Azure
- Google Cloud
Servers / containers
Operated by
Your team
Customer runs application storage, authentication, provider configuration, updates and backups.
Deployment boundaries by provider
- AWS: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Open WebUI deployment on AWS ECS / Fargate ↗ · Source checked 2026-11-12
- Azure: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Open WebUI deployment on Azure Container Apps ↗ · Source checked 2026-11-12
- Google Cloud: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Open WebUI deployment on Google Cloud Run ↗ · Source checked 2026-11-12
Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.
| Install method | Official Docker image, Python installation or Kubernetes deployment. |
|---|---|
| Infrastructure | Servers / containers The application runs as a Docker/Python server or Kubernetes workload with persistent conversation/user storage. Local inference is a separate server or accelerator workload, depending on the chosen model. |
| Licensing model | Source Available The current Open WebUI license adds branding restrictions to BSD-style terms, with small-deployment and permission/license exceptions. Classified here as source-available rather than treating the current version as unmodified BSD-3-Clause. |
| License | Open WebUI license based on BSD-style terms with additional branding restrictions and defined exceptions; enterprise terms may be required for rebranding. |
Buyer diligence
Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.
How to read these facts
Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.
5 of 12 fields researched (42%) · 5 documented · 0 unresolved. Evidence coverage is not a feature score.
- Single sign-on
AvailableEvidence and scope for Single sign-on
Upstream documents OAuth/OIDC and trusted-header authentication. Only one generic OIDC provider is configured through OPENID_PROVIDER_URL at a time; trusted-header use requires an isolated trusted proxy.
Upstream authentication configuration; review provider and session settings · Source ↗ · Reviewed 2026-11-14
Documented · Editor reviewed.
- Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC
The upstream Compose example includes Open WebUI and Ollama with persistent volumes. Its defaults use moving image references and an empty application secret; configure production credentials and pin versions.
Upstream example; model resources and service exposure require separate review · Deployment artifact ↗ (main (moving branch)) · Reviewed 2026-11-14
Documented · Editor reviewed.
- Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing
The performance guide shows a container example reserving 2 CPUs/4 GB RAM with limits of 4 CPUs/8 GB. Multi-user deployments need PostgreSQL; scaled replicas also require shared services. Local inference, embeddings, extraction, vector storage and HA are additional. This is an example allocation, not a validated 100-user or 1-TB minimum.
Application-container example; full stack and workload sizing excluded · Source ↗ · Shared infrastructure for scaled deployments ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
- License pricing
DocumentedEvidence and scope for License pricing
Current Open WebUI has custom terms restricting branding changes, with exceptions including deployments of at most 50 end users in a rolling 30-day period, written permission or an enterprise licence. A 100-user deployment cannot assume the small-deployment branding exception. Model and infrastructure costs are separate.
Upstream core licence; commercial features, support and hosting priced separately · Source ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
- Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence
Open WebUI v0.13.4 was published November 17, 2026. Deployments using Terminals server connections require Terminals 0.4.0 or later; upgrading that server from 0.3.x requires manual migration. Open Terminal and Tether terminal connections are unaffected by this migration. The release also replaces Direct Connections and Integrations with Tether and migrates image settings.
Upstream Open WebUI self-hosted release; the Terminals version and migration requirements apply only to deployments using Terminals server connections · Source ↗ · Reviewed 2026-11-18
Documented · Editor reviewed.
Show all fields (7 not researched)
- Marketplace delivery
- Not researched Supply a public source.
- Cloud commitment eligibility
- Not researched Supply a public source.
- SCIM provisioning
- Not researched Supply a public source.
- Compliance attestations
- Not researched Supply a public source.
- Security controls
- Not researched Supply a public source.
- Air-gapped operation
- Not researched Supply a public source.
- Operating cost estimate
- Not researched Supply a public source.
Scope & considerations
The UI sends messages to the model endpoint selected for a conversation. Local Ollama or vLLM endpoints can keep inference on customer infrastructure; cloud APIs, embeddings, tools and plugins have separate data flows. The current license restricts branding removal in larger deployments, with small-deployment, permission and enterprise-license exceptions; review the actual terms. Open WebUI v0.13.4 replaces Direct Connections and Integrations with Tether and migrates image settings. Deployments using Terminals server connections require Terminals 0.4.0 or later; upgrading that server from 0.3.x requires manual migration. Open Terminal and Tether terminal connections are unaffected by this migration. Tether introduces user-device and local-command paths that require explicit trust review.
Category fit
- AI applications & RAG
- Deployable team chat and model-access interface with retrieval features. It is an interface and application layer, not an included license or runtime for every connected model.
- AI tools & infrastructure
- Self-hosted AI chat and knowledge interface for local model servers and cloud APIs.
Compare within AI applications & RAG
- AnythingLLM DockerSelf-hosted application for document-grounded AI chat, retrieval and agents.
- AWS
- Google Cloud
- Railway
- Dify Self-HostedVisual AI application and RAG workflow platform available as a self-hosted container stack.
- Alibaba Cloud
- Langflow Self-HostedVisual AI workflow and agent builder with Docker and persistent PostgreSQL deployment.
- AWS
- Azure
- Google Cloud
- LibreChat Self-HostedSelf-hosted multi-model AI chat, agent and retrieval platform with documented Railway and DigitalOcean deployments.
- DigitalOcean
- Railway
- MaxKB Community EditionOpen-source knowledge-base, RAG and agent-workflow platform deployable into an Alibaba Cloud account.
- Alibaba Cloud
- Onyx Self-HostedSelf-hosted enterprise search and AI assistant platform with connectors and retrieval infrastructure.
- AWS
- Azure
- Google Cloud
- DigitalOcean
- RAGFlowDocument processing and retrieval platform for building RAG and agentic knowledge applications.
- AWS
- Azure
- Google Cloud
- Alibaba Cloud
- Railway
These products address related workflows; read their category-fit notes before comparing scope. See all of AI applications & RAG →
Installation outline
- Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
- Review the vendor's installation documentation, required permissions and outbound data flows.
- Deploy to a non-production environment; configure identity, networking and monitoring.
- Test backup recovery and upgrades before promoting to production.
Evidence trail
Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.
- Deployment sourcesChecked
- Installation options ↗docs.openwebui.com
- Local and cloud model connections ↗docs.openwebui.com
- Current license and branding conditions ↗docs.openwebui.com
- Licensing and edition terms ↗github.com
- Open WebUI v0.13.4 release ↗github.com
- Cloud deployment evidenceChecked
The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.
- Open WebUI deployment on AWS ECS / Fargate ↗ · AWS
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
Project deployment instructions cover the application on AWS ECS / Fargate with external database, Redis and file storage. Model inference is separate; review model endpoints, egress and WebSocket/runtime limits.
- Open WebUI deployment on Azure Container Apps ↗ · Azure
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
Project deployment instructions cover the application on Azure Container Apps with external database, Redis and file storage. Model inference is separate; review model endpoints, egress and WebSocket/runtime limits.
- Open WebUI deployment on Google Cloud Run ↗ · Google Cloud
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
Project deployment instructions cover the application on Google Cloud Run with external database, Redis and file storage. Model inference is separate; review model endpoints, egress and WebSocket/runtime limits.
- Open WebUI deployment on AWS ECS / Fargate ↗ · AWS
- Infrastructure evidenceChecked
- Licensing evidenceChecked