Skip to content
Merged
Show file tree
Hide file tree
Changes from 25 commits
Commits
Show all changes
33 commits
Select commit Hold shift + click to select a range
724a246
Update index.mdx
peetuhr Dec 23, 2025
c5efbb1
Add files via upload
peetuhr Dec 23, 2025
3b8370c
Update partners.md
peetuhr Dec 23, 2025
134d4eb
Add files via upload
peetuhr Dec 23, 2025
3cfaf7b
Update architecture.md
peetuhr Dec 23, 2025
6b677a5
Update architecture.md
peetuhr Dec 23, 2025
9b890da
Add files via upload
peetuhr Dec 23, 2025
dfff36a
Delete docs/enterprise/security.md
peetuhr Dec 23, 2025
96de5ae
Add files via upload
peetuhr Dec 23, 2025
96bd211
Update security.md
peetuhr Dec 23, 2025
83dc0fc
Add files via upload
peetuhr Dec 23, 2025
903d629
Update customization.md
peetuhr Dec 23, 2025
e8dd704
Add files via upload
peetuhr Dec 23, 2025
ac2f722
Update _category_.json
peetuhr Dec 23, 2025
ba05162
Update index.mdx
peetuhr Dec 23, 2025
14b8089
Update architecture.md
peetuhr Dec 23, 2025
b82f5e8
Update customization.md
peetuhr Dec 23, 2025
1907b41
Update support.md
peetuhr Dec 23, 2025
7876629
Update support.md
peetuhr Dec 23, 2025
3ffbcc6
Update partners.md
peetuhr Dec 23, 2025
8055c9e
Add files via upload
peetuhr Dec 23, 2025
79993e6
Update index.mdx
peetuhr Dec 23, 2025
44c1fe5
Delete docs/enterprise/customers/_category_.json
peetuhr Dec 23, 2025
493a9fe
Update partners.md
peetuhr Dec 23, 2025
d8e1a58
Update index.mdx
peetuhr Dec 23, 2025
c5415f4
docs: address feedback on Support page, refine CTAs, update index
peetuhr Dec 27, 2025
4cfeea0
docs: added sales email guidelines
peetuhr Dec 27, 2025
04a2d9a
Merge branch 'open-webui:main' into main
peetuhr Dec 28, 2025
9bb5d39
refac
tjbck Jan 1, 2026
e62c8f4
refac
tjbck Jan 1, 2026
0a4fe73
refac
tjbck Jan 1, 2026
bc70a2f
refac
tjbck Jan 1, 2026
9fda846
refac
tjbck Jan 1, 2026
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
99 changes: 99 additions & 0 deletions docs/enterprise/architecture.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,99 @@
---
sidebar_position: 1
title: "🏗️ High Availability"
---

# High Availability & Architecture

## Built for Mission-Critical Reliability

When AI becomes central to your organization's operations, downtime isn't just inconvenient—it's costly. Open WebUI is architected from the ground up to support enterprise-scale deployments where reliability isn't optional.

Whether you're supporting a pilot team of 15 or a global workforce of 10,000+, Open WebUI's architecture scales with you—without requiring a complete rebuild as your needs grow.

---

## Architecture Overview

### Stateless, Container-First Design

Open WebUI follows a **stateless, container-first architecture**, meaning you are never bottlenecked by a single server. This design philosophy enables:

* **Horizontal Scaling:** Add more instances as demand grows, rather than upgrading to larger (and more expensive) hardware.
* **Flexible Deployment:** Run on-premise, in private clouds, or hybrid environments without architectural changes.
* **Container Orchestration Compatibility:** Full support for Kubernetes, Docker Swarm, and other orchestration platforms.

For decision-makers, this means your initial investment in Open WebUI doesn't become technical debt. The same architecture that supports your proof-of-concept can scale to support your entire organization.

---

## High Availability Configuration

For organizations with demanding uptime requirements, Open WebUI supports production-grade high availability configurations:

| Component | Capability |
| :--- | :--- |
| **Load Balancing** | Multiple container instances behind a load balancer for resilience and optimal performance. |
| **External Databases** | Scalable, reliable data storage separate from application instances. |
| **Persistent Storage** | Flexible storage backends to meet your data residency and performance requirements. |
| **Observability** | Integration with modern logging and metrics tools for proactive monitoring. |

When properly configured, Open WebUI can achieve **99.99% uptime**—the reliability standard expected for mission-critical enterprise systems.

---

## Scalability in Practice

Open WebUI isn't theoretically scalable—it's **proven at scale**. The platform is already trusted in deployments supporting extremely high user counts, including:

* 🎓 **Universities** managing institution-wide AI access.
* 🏢 **Multinational Enterprises** deploying across regions and business units.
* 🏛️ **Major Organizations** requiring consistent performance under heavy load.

With the right infrastructure configuration, Open WebUI scales from pilot projects to mission-critical worldwide rollouts.

---

## What This Means for Your Organization

### For IT Leadership
You are not adopting a tool that will need to be replaced as you grow. Open WebUI's architecture supports your long-term AI strategy without forced migrations or re-platforming.

### For Security & Compliance Teams
Stateless architecture and flexible deployment options mean you can meet data residency requirements and maintain control over where your AI infrastructure lives.

### For Finance & Procurement
Horizontal scaling means you pay for capacity as you need it. No over-provisioning of expensive hardware "just in case."

---

## Planning Your Deployment

The right architecture depends on your organization's specific requirements—user count, geographic distribution, uptime SLAs, and compliance needs all factor into the design.

For organizations planning high-availability, enterprise-grade deployments, we recommend:

1. **Review the [Getting Started Guide](../getting-started/index.md)** for foundational deployment concepts.
2. **Consult the [FAQ](../faq.mdx)** for answers to common questions.
3. **Contact our Enterprise team** for guidance on complex or large-scale deployments.

[**Contact Sales to Discuss Architecture**](mailto:sales@openwebui.com)

---

:::info Community Resource: Best practices for large-scale Open WebUI architecture
For engineers looking for a technical implementation guide regarding high-availability architecture, we recommend reviewing this excellent community resource:

**[Read: The SRE's Guide to High Availability Open WebUI Deployment Architecture](https://taylorwilsdon.medium.com/the-sres-guide-to-high-availability-open-webui-deployment-architecture-2ee42654eced)**
:::

---

## Next Steps

* **[🛡️ Security & Governance](./security)** — Learn how Open WebUI integrates with enterprise identity systems.
* **[🔧 Integration & Customization](./customization)** — Explore how to tailor Open WebUI to your workflows.

* **[🤝 Support & SLAs](./support)** — Review enterprise support options and service guarantees.


8 changes: 0 additions & 8 deletions docs/enterprise/customers/_category_.json

This file was deleted.

45 changes: 45 additions & 0 deletions docs/enterprise/customers/index.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,45 @@
---
sidebar_position: 5
title: "👥 Customer Stories"
---

# Customer Stories

## Powering Innovation at Scale

Open WebUI is the interface of choice for individuals, engineering teams, researchers, and enterprises worldwide. With thousands of active deployments, it powers AI initiatives across startups, Fortune 500 companies, government agencies, and research institutions—helping people reclaim time for what truly matters.

Many of our users work in environments where privacy isn't optional—it's essential. That's by design. Open WebUI is built for those who need powerful AI capabilities with complete control over their data.

As our community grows, so does this showcase. We're proud to highlight those who are building in the open.

---

## Featured Case Study

### Samsung Semiconductor

See how Samsung Semiconductor built a secure, self-hosted AI platform to boost R&D efficiency—reducing workflow times **from days to hours**.

[![Samsung Semiconductor Case Study](/images/enterprise/customers/samsung-semiconductor/hero.png)](./samsung-semiconductor)

**[📖 Read the Full Case Study →](./samsung-semiconductor)**

---

## Share Your Story

We're actively expanding this showcase with organizations and teams driving real impact with Open WebUI.

Whether you're using Open WebUI to solve complex problems, strengthen data privacy, or democratize AI access for your team, we'd love to hear from you.

**Why participate?**

- **Visibility**: Position your team as a leader in the private AI space.
- **Community Impact**: Help others see what's possible with open, self-hosted AI.

:::info Interested in Being Featured?
Reach out to discuss a potential case study or community spotlight.

[**📩 Contact Us**](mailto:sales@openwebui.com?subject=Customer%20Story%20Submission)
:::
129 changes: 129 additions & 0 deletions docs/enterprise/customization.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,129 @@
---
sidebar_position: 3
title: "🔧 Integration & Customization"
---

# Integration & Customization

## Make Open WebUI Your Own

Off-the-shelf software rarely fits enterprise workflows perfectly. Teams have established processes, specific model requirements, and brand standards that generic tools can't accommodate.

Open WebUI is built differently. From the interface your users see to the AI models powering their work, every layer is designed for customization—without requiring you to fork the codebase or maintain a separate build.

---

## AI Model Integration

### Connect Any Model to Any Workflow

Your organization's AI needs are unique. Maybe you have fine-tuned models on proprietary data. Perhaps you are committed to specific providers for compliance reasons. Or you need different models for different use cases across departments.

Open WebUI supports flexible model integration:

* **Proprietary Models** — Connect models you have developed or fine-tuned specifically for your organization's domain.
* **Third-Party Providers** — Integrate commercial AI services that meet your compliance and performance requirements.
* **Local Models** — Run models entirely on-premise for maximum data control and reduced latency.
* **Multi-Model Environments** — Offer different models to different teams, or build multi-model agentic workflows based on specific needs.

### Model Optimization for Enterprise Workflows

Beyond basic connectivity, Open WebUI's enterprise offerings include guidance on optimizing model performance for your specific use cases:

* **Fine-Tuning Consultation** — Work with our team to optimize models for your domain vocabulary and use patterns.
* **Performance Benchmarking** — Understand how different models perform against your actual workflow requirements.
* **Cost Optimization** — Balance model capability against token costs for sustainable deployment at scale.

---

## White-Labeling & Custom Theming

### Your Brand, Your Platform

For organizations deploying AI tools to internal teams—or offering AI capabilities to clients—brand consistency matters. Open WebUI's enterprise licensing enables full white-labeling capabilities:

| Capability | What You Can Customize |
| :--- | :--- |
| **Visual Identity** | Replace default branding with your organization's logo, colors, and visual style. |
| **Interface Theming** | Customize the look and feel to match your existing internal tools. |
| **Naming & Terminology** | Adapt the interface language to align with your organization's conventions. |
| **User Experience** | Tailor the interface to emphasize the workflows most relevant to your teams. |

:::info Enterprise License Required
White-labeling and custom theming capabilities require an enterprise license. The standard version must retain Open WebUI branding as specified in the design guidelines.

[**Contact our Enterprise team to discuss licensing options.**](mailto:sales@openwebui.com)
:::

### Why This Matters

When AI tools look and feel like part of your existing ecosystem, adoption increases. Users don't experience cognitive friction switching between "your tools" and "that AI thing"—it becomes one seamless environment.

---

## Extensibility & Platform Integration

### Built to Extend, Not Replace

Enterprise software ecosystems are complex. The last thing you need is another silo. Open WebUI's modular architecture means it works *with* your existing infrastructure, not against it:

| Integration Type | Examples |
| :--- | :--- |
| **Identity Systems** | LDAP, Active Directory, SSO providers (SAML, OIDC). |
| **Enterprise Tools** | Connect to internal APIs, databases, and business systems. |
| **Workflow Automation** | Integrate with existing automation pipelines and orchestration tools. |
| **Observability** | Feed logs and metrics into your existing monitoring stack. |

### Extend Without Forking

Open WebUI's plugin and pipeline architecture allows you to add functionality without modifying core code:

* **Custom Workflows** — Build organization-specific AI workflows that reflect your actual business processes.
* **Data Connectors** — Create integrations that pull context from your internal knowledge bases.
* **Specialized Interfaces** — Develop custom UI components for specific departmental needs.
* **Automation Hooks** — Trigger actions in external systems based on AI interactions.

This approach protects your investment. **Core Open WebUI updates do not break your customizations**, and your customizations do not prevent you from receiving security patches and new features.

---

## What This Means for Your Organization

### For Product Owners
You are not forcing teams to adapt to the tool—the tool adapts to them. Customization options mean you can roll out AI capabilities that feel native to each department's workflow.

### For IT Teams
Integration flexibility means Open WebUI slots into your existing architecture. You are not rebuilding identity management, recreating monitoring dashboards, or maintaining yet another authentication silo.

### For Brand & Communications Teams
White-labeling ensures AI tools meet the same brand standards as every other internal platform. No awkward "third-party app" aesthetic undermining your carefully maintained internal experience.

---

## Planning Your Customization

The right level of customization depends on your organization's specific needs. Some enterprises need only basic theming; others require deep integrations with proprietary systems.

For organizations planning significant customization, we recommend:

1. **Inventory your requirements** — What must integrate? What should match your brand? What workflows need support?
2. **Review existing capabilities** — Many customizations are possible through configuration rather than development.
3. **Contact our Enterprise team** — For complex integrations or white-labeling, we can scope the effort together.

[**Discuss Your Customization Needs**](mailto:sales@openwebui.com)

:::tip Private Feature Development
Need capabilities that don't exist yet? Enterprise customers can work directly with the Open WebUI team to build custom features specific to their organization's needs.

[**Let's talk about your requirements.**](mailto:sales@openwebui.com)
:::

---

## Next Steps

* **[🏗️ High Availability](./architecture)** — Understand Open WebUI's scalable infrastructure design.
* **[🛡️ Security & Governance](./security)** — Learn how Open WebUI integrates with enterprise identity systems.

* **[🤝 Support & SLAs](./support)** — Review enterprise support options and service guarantees.

Loading