open-webui · Classic298 · Jun 6, 2026 · Jun 6, 2026 · Jun 6, 2026 · Jun 6, 2026
diff --git a/.gitignore b/.gitignore
@@ -8,6 +8,9 @@
 .docusaurus
 .cache-loader
 
+# Local banner render scratch (not for commit)
+.scratch_banner
+
 # Misc
 .DS_Store
 .env.local

diff --git a/docs/enterprise/customers/astellas-pharma.mdx b/docs/enterprise/customers/astellas-pharma.mdx
@@ -22,8 +22,8 @@ How Astellas Pharma Inc. built a secure, flexible internal AI platform with **Op
 - **Industry**: Pharmaceutical
 - **Deployment**: Azure AKS (private endpoints)
 - **Models**: Azure OpenAI, Gemini, DeepSeek, Perplexity
-- **Time-to-deploy**: ~1 month (April–May 2025)
-- **Adoption**: 30–40% weekly active users sustained over five months
+- **Time-to-deploy**: ~1 month (April to May 2025)
+- **Adoption**: 30 to 40% weekly active users sustained over five months
 - **Key Results**: 420+ custom models created, 68% of users report significant efficacy gains, +43 NPS
 
 
@@ -60,7 +60,7 @@ Open WebUI was selected for its **flexibility, fine-grained permission controls,
 - **Security Controls**: MFA via IdP, RBAC by group, data residency enforced
 
 
-> “Open WebUI allowed us to create and share custom AI models securely across the entire company, while giving us the flexibility to leverage the full potential of any cutting-edge model available.” - Generative AI Team Manager, Astellas
+> “Open WebUI allowed us to create and share custom AI models securely across the entire company, while giving us the flexibility to leverage the full potential of any cutting-edge model available.” Generative AI Team Manager, Astellas
 
 ## Models & Data Handling
 
@@ -84,12 +84,12 @@ Training included:
 
 Over the following months:
 
-- **Weekly active users stabilized at 30–40%** over five months
+- **Weekly active users stabilized at 30 to 40%** over five months
 - Users organically created **hundreds of custom models**, sharing them across departments
 - **All departments** adopted the platform, including Research, Clinical Development, Medical, Sales, Marketing, Legal, Compliance, Pharmacovigilance, Administration, Communications, and Corporate Strategy
 
 
-> “Our efficiency in gathering external scientific information has improved dramatically. Being able to select and switch models depending on the use case makes our research far more effective.” - Research Department User, Astellas 
+> “Our efficiency in gathering external scientific information has improved dramatically. Being able to select and switch models depending on the use case makes our research far more effective.” Research Department User, Astellas 
 
 ## Results: Democratization, Productivity, and Satisfaction
 
@@ -114,7 +114,7 @@ The platform grew to **3,200+ total users** organically, with an advanced user b
 R&D and research teams reported dramatic improvements in gathering and synthesizing scientific information, clinical trial summaries, and multilingual medical documents.
 
 
-> “For coding tasks, efficiency has increased more than ten-fold, I can’t imagine working without this tool now.” - Advanced User, Astellas
+> “For coding tasks, efficiency has increased more than ten-fold, I can’t imagine working without this tool now.” Advanced User, Astellas
 
 ## Top Use Cases
 
@@ -146,7 +146,7 @@ R&D and research teams reported dramatic improvements in gathering and synthesiz
 
 :::tip
 
-**Looking for an [Enterprise Plan](https://docs.openwebui.com/enterprise)?** — **[Speak with Our Sales Team Today!](https://docs.openwebui.com/enterprise)**
+**Looking for an [Enterprise Plan](https://docs.openwebui.com/enterprise)?** **[Speak with Our Sales Team Today!](https://docs.openwebui.com/enterprise)**
 
 Get **enhanced capabilities**, including **custom theming and branding**, **Service Level Agreement (SLA) support**, **Long-Term Support (LTS) versions**, and **more!**
 

diff --git a/docs/enterprise/customers/public-storage.mdx b/docs/enterprise/customers/public-storage.mdx
@@ -17,7 +17,7 @@ How Public Storage used a **champion-driven rollout** to deploy a secure, privat
 
 ### At a Glance
 
-- **Users**: 5,000–10,000 employees
+- **Users**: 5,000 to 10,000 employees
 - **Region**: United States (data residency enforced)
 - **Industry**: Real Estate
 - **Deployment**: GCP (containerized, private networking)
@@ -60,7 +60,7 @@ Open WebUI was selected for its **extensible foundation**: an open architecture
 - **Security Controls**: MFA via IdP, RBAC by group, data residency enforced, PII redaction with user-facing interruption, moderation guardrails, audit exports to SIEM, DLP policies, egress restrictions
 
 
-> “Our goal wasn’t just to deploy AI, but to scale it responsibly. Open WebUI allows us to crowdsource high-value use cases from the business while maintaining the governance we need.” — CTO, Public Storage
+> “Our goal wasn’t just to deploy AI, but to scale it responsibly. Open WebUI allows us to crowdsource high-value use cases from the business while maintaining the governance we need.” CTO, Public Storage
 
 ## Models & Data Handling
 
@@ -84,7 +84,7 @@ Within the first month:
 - Usage continued to grow as teams **shared successful workflows** with peers
 - **All corporate functions** were represented, including HR, Marketing, Finance, Legal, Call Center, Operations, Sales/Acquisitions, IT, and Risk Management
 
-> “We’re seeing real operational time savings from use cases built by the business, not just IT, which has accelerated adoption and delivered practical results.” — VP, Digital Technology, Public Storage
+> “We’re seeing real operational time savings from use cases built by the business, not just IT, which has accelerated adoption and delivered practical results.” VP, Digital Technology, Public Storage
 
 ## Results: Productivity, Adoption, and Governance
 
@@ -132,7 +132,7 @@ The platform empowered every corporate function to discover and share AI-driven
 
 :::tip
 
-**Looking for an [Enterprise Plan](https://docs.openwebui.com/enterprise)?** — **[Speak with Our Sales Team Today!](https://docs.openwebui.com/enterprise)**
+**Looking for an [Enterprise Plan](https://docs.openwebui.com/enterprise)?** **[Speak with Our Sales Team Today!](https://docs.openwebui.com/enterprise)**
 
 Get **enhanced capabilities**, including **custom theming and branding**, **Service Level Agreement (SLA) support**, **Long-Term Support (LTS) versions**, and **more!**
 

diff --git a/docs/enterprise/customers/samsung-semiconductor.mdx b/docs/enterprise/customers/samsung-semiconductor.mdx
@@ -17,7 +17,7 @@ How Samsung Semiconductor built a secure, self-hosted AI platform with **Open We
 
 ### At a Glance
 
-- **Users**: 1,000 - 4,999 employees
+- **Users**: 1,000 to 4,999 employees
 - **Region**: United States (data residency enforced)
 - **Industry**: Semiconductor
 - **Deployment**: On-prem Kubernetes cluster
@@ -58,7 +58,7 @@ Open WebUI was selected for its **open architecture, flexibility, and rapid proo
 - **Security Controls**: Data residency enforced; internal user access controls
 
 
-> “Open WebUI gave us control across security, models, and UX, without vendor lock-in.” — Software Engineering, Samsung Semiconductor, Inc.
+> “Open WebUI gave us control across security, models, and UX, without vendor lock-in.” Software Engineering, Samsung Semiconductor, Inc.
 
 ## Adoption & Enablement
 
@@ -69,7 +69,7 @@ Within 30 days:
 - Daily active users stabilized at 5-10% of total employees
 - R&D teams reported **significant productivity improvements**
 
-> “Open WebUI provides users with an environment similar to commercial tools, giving them a sense of familiarity, and at the same time, it has the advantage of improving usability with its simple and intuitive design.” — AI/ML Engineering, Samsung Semiconductor, Inc.
+> “Open WebUI provides users with an environment similar to commercial tools, giving them a sense of familiarity, and at the same time, it has the advantage of improving usability with its simple and intuitive design.” AI/ML Engineering, Samsung Semiconductor, Inc.
 
 ## Results: Speed, Adoption, and Control
 
@@ -109,7 +109,7 @@ Samsung Semiconductor plans to continue expanding its AI infrastructure with Ope
 
 :::tip
 
-**Looking for an [Enterprise Plan](https://docs.openwebui.com/enterprise)?** — **[Speak with Our Sales Team Today!](https://docs.openwebui.com/enterprise)**
+**Looking for an [Enterprise Plan](https://docs.openwebui.com/enterprise)?** **[Speak with Our Sales Team Today!](https://docs.openwebui.com/enterprise)**
 
 Get **enhanced capabilities**, including **custom theming and branding**, **Service Level Agreement (SLA) support**, **Long-Term Support (LTS) versions**, and **more!**
 

diff --git a/docs/enterprise/deployment/container-service.md b/docs/enterprise/deployment/container-service.md
@@ -8,7 +8,7 @@ title: "Container Service"
 Run the official `ghcr.io/open-webui/open-webui` image on a managed container platform such as AWS ECS/Fargate, Azure Container Apps, or Google Cloud Run.
 
 :::info Prerequisites
-Before proceeding, ensure you have configured the [shared infrastructure requirements](/enterprise/deployment#shared-infrastructure-requirements) — PostgreSQL, Redis, a vector database, shared storage, and content extraction.
+Before proceeding, ensure you have configured the [shared infrastructure requirements](/enterprise/deployment#shared-infrastructure-requirements): PostgreSQL, Redis, a vector database, shared storage, and content extraction.
 :::
 
 ## When to Choose This Pattern
@@ -49,7 +49,7 @@ Use **versioned tags** for production stability:
 ghcr.io/open-webui/open-webui:v0.x.x
 ```
 
-Avoid the `:main` tag in production — it tracks the latest development build and can introduce breaking changes without warning. Check the [Open WebUI releases](https://github.com/open-webui/open-webui/releases) for the latest stable version.
+Avoid the `:main` tag in production. It tracks the latest development build and can introduce breaking changes without warning. Check the [Open WebUI releases](https://github.com/open-webui/open-webui/releases) for the latest stable version.
 
 ## Scaling Strategy
 
@@ -65,7 +65,7 @@ Avoid the `:main` tag in production — it tracks the latest development build a
 | **Storage** | Use object storage (S3, GCS, Azure Blob) or a shared filesystem (such as EFS). Container-local storage is ephemeral and not shared across tasks. |
 | **Tika sidecar** | Run Tika as a sidecar container in the same task definition, or as a separate service. Sidecar pattern keeps extraction traffic local. |
 | **Secrets management** | Use your platform's secrets manager (AWS Secrets Manager, Azure Key Vault, GCP Secret Manager) for `DATABASE_URL`, `REDIS_URL`, and `WEBUI_SECRET_KEY`. |
-| **Updates** | Perform a rolling deployment with a single task first — this task runs migrations (`ENABLE_DB_MIGRATIONS=true`). Once healthy, scale the remaining tasks with `ENABLE_DB_MIGRATIONS=false`. |
+| **Updates** | Perform a rolling deployment with a single task first. This task runs migrations (`ENABLE_DB_MIGRATIONS=true`). Once healthy, scale the remaining tasks with `ENABLE_DB_MIGRATIONS=false`. |
 
 ## Anti-Patterns to Avoid
 

diff --git a/docs/enterprise/deployment/index.md b/docs/enterprise/deployment/index.md
@@ -5,7 +5,7 @@ title: "Deployment Options"
 
 # Scalable Enterprise Deployment Options
 
-Open WebUI's **stateless, container-first architecture** means the same application runs identically whether you deploy it as a Python process on a VM, a container in a managed service, or a pod in a Kubernetes cluster. The difference between deployment patterns is how you **orchestrate, scale, and operate** the application — not how the application itself behaves.
+Open WebUI's **stateless, container-first architecture** means the same application runs identically whether you deploy it as a Python process on a VM, a container in a managed service, or a pod in a Kubernetes cluster. The difference between deployment patterns is how you **orchestrate, scale, and operate** the application, not how the application itself behaves.
 
 :::tip Model Inference Is Independent
 How you serve LLM models is separate from how you deploy Open WebUI. You can use **managed APIs** (OpenAI, Anthropic, Azure OpenAI, Google Gemini) or **self-hosted inference** (Ollama, vLLM) with any deployment pattern. See [Integration](/enterprise/integration) for details on connecting models.
@@ -83,7 +83,7 @@ Deploy `open-webui serve` as a systemd-managed process on virtual machines in a
 
 ### [Container Service](./container-service)
 
-Run the official Open WebUI container image on a managed platform such as AWS ECS/Fargate, Azure Container Apps, or Google Cloud Run. Best for teams wanting container benefits — immutable images, versioned deployments, no OS management — without Kubernetes complexity.
+Run the official Open WebUI container image on a managed platform such as AWS ECS/Fargate, Azure Container Apps, or Google Cloud Run. Best for teams wanting container benefits (immutable images, versioned deployments, no OS management) without Kubernetes complexity.
 
 ### [Kubernetes with Helm](./kubernetes-helm)
 
@@ -95,9 +95,9 @@ Deploy using the official Open WebUI Helm chart on any Kubernetes distribution (
 
 | | **Python / Pip (VMs)** | **Container Service** | **Kubernetes (Helm)** |
 | :--- | :--- | :--- | :--- |
-| **Operational complexity** | Moderate — OS patching, Python management | Low — platform-managed containers | Higher — requires K8s expertise |
+| **Operational complexity** | Moderate (OS patching, Python management) | Low (platform-managed containers) | Higher (requires K8s expertise) |
 | **Auto-scaling** | Cloud ASG/VMSS with health checks | Platform-native, minimal configuration | HPA with fine-grained control |
-| **Container isolation** | None — process runs directly on OS | Full container isolation | Full container + namespace isolation |
+| **Container isolation** | None (process runs directly on OS) | Full container isolation | Full container + namespace isolation |
 | **Rolling updates** | Manual (scale down, update, scale up) | Platform-managed rolling deployments | Declarative rolling updates with rollback |
 | **Infrastructure-as-code** | Terraform/Pulumi for VMs + config mgmt | Task/service definitions (CloudFormation, Bicep, Terraform) | Helm charts + GitOps (Argo CD, Flux) |
 | **Best suited for** | Teams with VM-centric operations, regulatory constraints | Teams wanting container benefits without K8s complexity | Large-scale, mission-critical deployments |
@@ -111,8 +111,8 @@ Production deployments should include monitoring and observability regardless of
 
 ### Health Checks
 
-- **`/health`** — Basic liveness check. Returns HTTP 200 when the application is running. Use this for load balancer and auto-scaler health checks.
-- **`/api/models`** — Verifies the application can connect to configured model backends. Requires an API key.
+- **`/health`**: Basic liveness check. Returns HTTP 200 when the application is running. Use this for load balancer and auto-scaler health checks.
+- **`/api/models`**: Verifies the application can connect to configured model backends. Requires an API key.
 
 ### OpenTelemetry
 
@@ -124,7 +124,7 @@ OTEL_EXPORTER_OTLP_ENDPOINT=http://your-collector:4318
 OTEL_SERVICE_NAME=open-webui
 ```
 
-This auto-instruments FastAPI, SQLAlchemy, Redis, and HTTP clients — giving visibility into request latency, database query performance, and cross-service traces.
+This auto-instruments FastAPI, SQLAlchemy, Redis, and HTTP clients, giving visibility into request latency, database query performance, and cross-service traces.
 
 ### Structured Logging
 
@@ -141,11 +141,11 @@ For full monitoring setup details, see [Monitoring](/reference/monitoring) and [
 
 ## Next Steps
 
-- **[Architecture & High Availability](/enterprise/architecture)** — Deeper dive into Open WebUI's stateless design and HA capabilities.
-- **[Security](/enterprise/security)** — Compliance frameworks, SSO/LDAP integration, RBAC, and audit logging.
-- **[Integration](/enterprise/integration)** — Connecting AI models, pipelines, and extending functionality.
-- **[Scaling Open WebUI](/getting-started/advanced-topics/scaling)** — The complete step-by-step technical scaling guide.
-- **[Multi-Replica Troubleshooting](/troubleshooting/multi-replica)** — Solutions for common issues in scaled deployments.
+- **[Architecture & High Availability](/enterprise/architecture)**: Deeper dive into Open WebUI's stateless design and HA capabilities.
+- **[Security](/enterprise/security)**: Compliance frameworks, SSO/LDAP integration, RBAC, and audit logging.
+- **[Integration](/enterprise/integration)**: Connecting AI models, pipelines, and extending functionality.
+- **[Scaling Open WebUI](/getting-started/advanced-topics/scaling)**: The complete step-by-step technical scaling guide.
+- **[Multi-Replica Troubleshooting](/troubleshooting/multi-replica)**: Solutions for common issues in scaled deployments.
 
 ---
 

diff --git a/docs/enterprise/deployment/kubernetes-helm.md b/docs/enterprise/deployment/kubernetes-helm.md
@@ -8,7 +8,7 @@ title: "Kubernetes with Helm"
 Deploy using the official Open WebUI Helm chart on any Kubernetes distribution (EKS, AKS, GKE, OpenShift, Rancher, self-managed).
 
 :::info Prerequisites
-Before proceeding, ensure you have configured the [shared infrastructure requirements](/enterprise/deployment#shared-infrastructure-requirements) — PostgreSQL, Redis, a vector database, shared storage, and content extraction.
+Before proceeding, ensure you have configured the [shared infrastructure requirements](/enterprise/deployment#shared-infrastructure-requirements): PostgreSQL, Redis, a vector database, shared storage, and content extraction.
 :::
 
 ## When to Choose This Pattern
@@ -62,7 +62,7 @@ helm repo update
 helm install openwebui open-webui/open-webui -f values.yaml
 ```
 
-Your `values.yaml` should override the defaults to point at your shared infrastructure. The chart has dedicated values for many common settings — use these instead of raw environment variables where available:
+Your `values.yaml` should override the defaults to point at your shared infrastructure. The chart has dedicated values for many common settings: use these instead of raw environment variables where available:
 
 ```yaml
 # Example values.yaml overrides (refer to chart documentation for full schema)

diff --git a/docs/enterprise/deployment/python-pip.md b/docs/enterprise/deployment/python-pip.md
@@ -8,7 +8,7 @@ title: "Python / Pip on VMs"
 Deploy `open-webui serve` as a systemd-managed process on virtual machines in a cloud auto-scaling group (AWS ASG, Azure VMSS, GCP MIG).
 
 :::info Prerequisites
-Before proceeding, ensure you have configured the [shared infrastructure requirements](/enterprise/deployment#shared-infrastructure-requirements) — PostgreSQL, Redis, a vector database, shared storage, and content extraction.
+Before proceeding, ensure you have configured the [shared infrastructure requirements](/enterprise/deployment#shared-infrastructure-requirements): PostgreSQL, Redis, a vector database, shared storage, and content extraction.
 :::
 
 ## When to Choose This Pattern

diff --git a/docs/enterprise/index.mdx b/docs/enterprise/index.mdx
@@ -83,7 +83,7 @@ Understand how Open WebUI supports large-scale deployments. Explore multi-node c
 Learn how Open WebUI integrates with your existing identity infrastructure, including LDAP, Active Directory, and SSO providers. Ideal for organizations requiring on-premise or air-gapped deployments.
 
 #### [🚀 Deployment Options](./deployment)
-Choose the right deployment pattern for your organization — from Python on auto-scaling VMs to managed container services to Kubernetes with Helm.
+Choose the right deployment pattern for your organization, from Python on auto-scaling VMs to managed container services to Kubernetes with Helm.
 
 #### [🔗 Integration](./integration)
 Connect proprietary, third-party, or local AI models. Extend functionality with plugins, pipelines, and custom workflows that fit your existing infrastructure.