
# Open WebUI Self-Hosted

Self-hosted AI chat and knowledge interface for local model servers and cloud APIs.

Canonical page: https://launchinyourcloud.com/directory/open-webui/
Catalog revision: 170de95bb7d832897d269051ad4500713acf96a62f3d01bc1d4e649679a56fde




Named clouds have provider-specific evidence. Missing clouds do not establish incompatibility. Preserve edition, account boundary, operating responsibilities and publisher disclosures. Source review dates record human checks, not rebuilds.


1 listing.


## Open WebUI Self-Hosted

Self-hosted AI chat and knowledge interface for local model servers and cloud APIs.

- Listing: https://launchinyourcloud.com/directory/open-webui/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Open WebUI license based on BSD-style terms with additional branding restrictions and defined exceptions; enterprise terms may be required for rebranding.
- Licensing model: source-available
- Installation: Official Docker image, Python installation or Kubernetes deployment.
- Architecture: Customer-operated web application and conversation storage connected to model providers
- Operations: Customer runs application storage, authentication, provider configuration, updates and backups.
- Product website: https://openwebui.com/
- Source review: 2026-11-18; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

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.

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.

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.


### 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: Self-hosted AI chat and knowledge interface for local model servers and cloud APIs.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.openwebui.com/deployment/aws-ecs/ (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.openwebui.com/deployment/azure-container-apps/ (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.openwebui.com/deployment/google-cloud-run/ (checked 2026-11-12). 


### Cloud deployment evidence

- Open WebUI deployment on AWS ECS / Fargate (aws): https://docs.openwebui.com/deployment/aws-ecs/
  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.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Open WebUI deployment on Azure Container Apps (azure): https://docs.openwebui.com/deployment/azure-container-apps/
  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.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Open WebUI deployment on Google Cloud Run (gcp): https://docs.openwebui.com/deployment/google-cloud-run/
  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.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Installation options: https://docs.openwebui.com/getting-started/quick-start/

- Local and cloud model connections: https://docs.openwebui.com/getting-started/quick-start/connect-a-provider/

- Current license and branding conditions: https://docs.openwebui.com/license/

- Licensing and edition terms: https://github.com/open-webui/open-webui/blob/main/LICENSE

- Open WebUI v0.13.4 release: https://github.com/open-webui/open-webui/releases/tag/v0.13.4

### Licensing sources

- https://github.com/open-webui/open-webui/blob/main/LICENSE

- https://docs.openwebui.com/license/

### Infrastructure sources

- https://docs.openwebui.com/getting-started/quick-start/


### Buyer diligence


Research coverage: 5/12 fields (42%); 5 documented, 0 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. 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. Scope: Upstream authentication configuration; review provider and session settings. Source: https://docs.openwebui.com/features/authentication-access/auth/sso/ (reviewed 2026-11-14).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. 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. Scope: Upstream example; model resources and service exposure require separate review. Source: https://github.com/open-webui/open-webui/blob/main/docker-compose.yaml (reviewed 2026-11-14). Deployment artifact: https://github.com/open-webui/open-webui/blob/main/docker-compose.yaml. Artifact reference: main (moving branch).

- Minimum footprint / sizing: Documented. 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. Scope: Application-container example; full stack and workload sizing excluded. Source: https://docs.openwebui.com/troubleshooting/performance/ (reviewed 2026-11-20). Supporting source: Shared infrastructure for scaled deployments — https://docs.openwebui.com/enterprise/deployment/.

- License pricing: Documented. 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. Scope: Upstream core licence; commercial features, support and hosting priced separately. Source: https://raw.githubusercontent.com/open-webui/open-webui/main/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. 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. Scope: Upstream Open WebUI self-hosted release; the Terminals version and migration requirements apply only to deployments using Terminals server connections. Source: https://github.com/open-webui/open-webui/releases/tag/v0.13.4 (reviewed 2026-11-18).






