mirror of
https://github.com/open-webui/docs.git
synced 2026-03-27 13:28:37 +07:00
ChromaDB's default local PersistentClient uses SQLite which is not fork-safe. When uvicorn forks multiple workers, concurrent writes crash workers instantly. Added warnings and guidance across env config, HA/scaling, performance, troubleshooting, Docker Swarm, Helm, Redis, RAG, and enterprise architecture docs. https://claude.ai/code/session_01TPoquFdHG6dZxRrZ4Jormh
65 lines
3.6 KiB
Markdown
65 lines
3.6 KiB
Markdown
---
|
|
sidebar_position: 5
|
|
title: "Architecture & High Availability"
|
|
---
|
|
|
|
### 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 hundreds of thousands of users, 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** | PostgreSQL for the main database (SQLite is not supported for multi-instance). |
|
|
| **External Vector Database** | A client-server vector database (PGVector, Milvus, Qdrant) or ChromaDB in HTTP server mode. The default ChromaDB local mode uses SQLite which is not safe for multi-process access. |
|
|
| **Redis** | Required for session management, WebSocket coordination, and configuration sync across 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 is designed to support high availability suitable for enterprise environments.
|
|
|
|
### 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."
|
|
|
|
---
|
|
|
|
[**Contact Enterprise Sales → sales@openwebui.com**](mailto:sales@openwebui.com) |