feat: #5864

New Issue

GiteaMirror · 2025-11-11T16:36:17-06:00

GiteaMirror commented

2025-11-11 16:36:17 -06:00

Originally created by @jtmyd-top on GitHub (Jul 24, 2025).

Check Existing Issues

I have searched the existing issues and discussions.

Problem Description

Feature Request: Support for Alternative Databases (e.g., MySQL)

Desired Solution you'd like

First of all, thank you for creating such an amazing project! Open WebUI's simplicity and ease of deployment are fantastic. The choice of SQLite as the default database is perfect for getting started quickly and for most personal use cases.
owever, for larger-scale deployments, enterprise environments, or users looking to integrate Open WebUI into their existing infrastructure, being limited to SQLite presents a few challenges:
Scalability: For environments with many users and high concurrency, SQLite can become a performance bottleneck. An external database like MySQL or PostgreSQL is designed to handle this level of load more effectively.
Centralized Management & Backup: Many organizations already have managed database clusters (e.g., AWS RDS, or a dedicated on-premise DB). They prefer to have all application data in a central, monitored, and regularly backed-up location. Managing a separate SQLite file falls outside of these standard operational procedures.
High Availability (HA): It's difficult to run Open WebUI in a highly available, multi-replica setup because SQLite is a single-file database, creating a single point of failure and contention. Using an external database is a prerequisite for a true HA deployment.

Alternatives Considered

No response

Additional Context

No response

Originally created by @jtmyd-top on GitHub (Jul 24, 2025). ### Check Existing Issues - [x] I have searched the existing issues and discussions. ### Problem Description Feature Request: Support for Alternative Databases (e.g., MySQL) ### Desired Solution you'd like First of all, thank you for creating such an amazing project! Open WebUI's simplicity and ease of deployment are fantastic. The choice of SQLite as the default database is perfect for getting started quickly and for most personal use cases. owever, for larger-scale deployments, enterprise environments, or users looking to integrate Open WebUI into their existing infrastructure, being limited to SQLite presents a few challenges: Scalability: For environments with many users and high concurrency, SQLite can become a performance bottleneck. An external database like MySQL or PostgreSQL is designed to handle this level of load more effectively. Centralized Management & Backup: Many organizations already have managed database clusters (e.g., AWS RDS, or a dedicated on-premise DB). They prefer to have all application data in a central, monitored, and regularly backed-up location. Managing a separate SQLite file falls outside of these standard operational procedures. High Availability (HA): It's difficult to run Open WebUI in a highly available, multi-replica setup because SQLite is a single-file database, creating a single point of failure and contention. Using an external database is a prerequisite for a true HA deployment. ### Alternatives Considered _No response_ ### Additional Context _No response_

GiteaMirror closed this issue

2025-11-11 16:36:18 -06:00

GiteaMirror referenced this issue

2025-11-11 17:59:53 -06:00

[PR #5864] [MERGED] build: Remove bun #8564

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/open-webui#5864