Open-WebUI — Self-Hosted, Open-Source

User-friendly AI Interface, supports Ollama, OpenAI API.

Open-WebUI is commonly used as a self-hosted alternative to ChatGPT. Replacing a SaaS tool with a self-hosted equivalent lets you avoid recurring subscription fees, keep full control of your data, and continue working even when the original vendor changes pricing, ships limits, or shuts down.

License: BSD-3-Clause. Built with: Python, Svelte, JavaScript, TypeScript, CSS, Shell, Dockerfile, HTML, Batchfile, Mako. Website: https://openwebui.com. Source: https://github.com/open-webui/open-webui.

Features

Installation

docker run -d -p 3000:8080 --add-host=host.docker.internal:host-gateway -v open-webui:/app/backend/data --name open-webui --restart always ghcr.io/open-webui/open-webui:main

Why self-host Open-WebUI

Self-hosting gives you three things SaaS can’t: data ownership (the files live on disks you control), cost predictability (a one-time setup vs. recurring per-seat fees that grow with your household or team), and longevity (open-source means the app keeps working even if the maintainers move on, since you can pin a working version). The trade-off is that you take on the operational work of running a server, applying updates, and handling backups.

What hardware do you need

Most self-hosted apps run comfortably on modest hardware — a Raspberry Pi 4, a mini PC, a NAS with Docker support, or a small VPS is usually enough for personal or family use. CPU and RAM requirements scale with how many simultaneous users or how much data you push through Open-WebUI. Storage requirements depend on the kind of data you keep; check the README for guidance on data retention.

Open-WebUI replaces

Where to go from here

Last verified: 2026-04-22