Overview
Open WebUI is a self-hosted, ChatGPT-style chat interface for large language models with user accounts, RAG (chat grounded in your uploaded documents), and model management. This template deploys a single stateful workload that keeps all of its state on a persistent volume and connects to your models through an in-GVC Ollama server and/or any OpenAI-compatible endpoint, served over HTTPS on the canonical*.cpln.app endpoint. Sign-ups are open on a fresh install so you can onboard immediately — the first account you register becomes the admin, and you lock registration down afterward.
Architecture
- Open WebUI — A single-replica stateful workload serving the web UI and API on port
8080. Its publicWEBUI_URLis derived from the canonical endpoint at boot, so links resolve correctly with no manual configuration. - Embedded SQLite on a persistent volume — All durable state (the
webui.dbdatabase, uploaded files, the default Chroma vector store used for RAG, and cache) lives on the workload’s volume set at/app/backend/data. SQLite is single-writer, so there is no external database dependency and the workload runs as exactly one replica. - Model backends — Chat completions are served by an existing Ollama workload in the same GVC (default), an OpenAI-compatible API (optional), or both. Neither backend is bundled by this template — you point it at model providers you run or subscribe to.
What Gets Created
- Stateful Open WebUI Workload — A single replica serving the web UI and API on port
8080. - Volume Set — A 10 GiB persistent volume mounted at
/app/backend/dataholding the SQLite database, uploaded files, the RAG vector store, and cache. Scheduled snapshots protect the data, and a final snapshot is kept on delete. - Config Secret — Holds the stable
WEBUI_SECRET_KEYthat signs sessions and JWTs. - Start-Script Secret — An opaque secret whose boot script sets
WEBUI_URLfrom the canonical endpoint. - Identity & Policy — An identity bound to the workload with a least-privilege policy granting
revealaccess to exactly the secrets it mounts (the config and start-script secrets, plus your OpenAI-key secret only when you configure one).
This template does not create a GVC. You must deploy it into an existing GVC.
Prerequisites
None for a default install — no secrets, cloud accounts, or external resources are required to bring the UI up. The items below are optional and only needed for the corresponding feature.- License awareness — Open WebUI ships under the “Open WebUI License” (BSD-3-Clause plus a branding-protection clause). It is free to self-host and run in production at any scale, but you must keep the “Open WebUI” branding visible in the UI unless your deployment serves 50 or fewer users, or you obtain enterprise permission. See Important Notes.
- Ollama backend (recommended) — An existing Ollama workload in the same GVC. Deploy the Ollama template first, then set its workload name in
ollama.workloadName. Enabled by default. - OpenAI-compatible backend (optional) — Create, before installing, an opaque secret (
encoding: plain) in your org holding your API key, and set its name inopenai.apiKeySecretName. An empty value leaves this backend off.
UI
Browse, install, and manage templates visually
CLI
Manage templates from your terminal
Terraform
Declare templates in your Terraform configurations
Pulumi
Declare templates in your Pulumi programs
Configuration
The defaultvalues.yaml for this template:
Instance & Resources
image— The Open WebUI container image.resources— CPU and memory for the container. RAG loads a local embedding model into RAM on first use, so keep memory at or above the default.volumeset.capacity— Volume size in GiB (minimum 10) for the SQLite database, uploads, RAG vector store, and cache.
Backup
Scheduled, crash-consistent snapshots of the data volume, managed by the platform — no cloud account or bucket is required. See Backing Up for how snapshots and restores work.backup.enabled— Take periodic snapshots of the data volume (defaulttrue).backup.schedule— Cron expression in UTC (default0 3 * * *, daily at 03:00). The platform does not accept schedules more frequent than hourly.backup.retention— How long each snapshot is kept, e.g.7d,720h,30d.
Authentication
auth.webuiSecretKey— Signs session tokens and JWTs. Override it once at install withopenssl rand -base64 32, then keep it stable forever — see Important Notes.auth.enableSignup— Open registration on the public endpoint (defaulttrueso a fresh install is usable). The first account registered becomes the admin; turn this off after onboarding — see Important Notes.
Model backends
At least one backend is needed to actually chat. The Ollama backend is on by default; the OpenAI-compatible backend is off until you supply a key secret. You can enable both.ollama.enabled— Connect to an existing Ollama workload in this GVC (defaulttrue).ollama.workloadName— The Ollama workload’s name in this GVC. The base URL is derived ashttp://{workloadName}.{gvc}.cpln.local:{port}.ollama.port— The Ollama API port (default11434).openai.baseUrl— Any OpenAI-compatible endpoint (defaulthttps://api.openai.com/v1).openai.apiKeySecretName— Name of your pre-created opaque secret holding the API key (see Prerequisites). Empty (default) leaves the OpenAI backend off.
Access
customDomain— Full URL of a custom domain, e.g.https://chat.example.com. Empty (default) uses the canonical*.cpln.appendpoint.publicAccess.enabled— Serve the UI over public HTTPS on the canonical*.cpln.appendpoint (default). When disabled, external requests are blocked at the edge and only in-GVC callers reach it perinternalAccess.internalAccess.type— Internal firewall scope for in-GVC callers of the Open WebUI API:
Connecting
Using a Model Backend
Deploy the Ollama template into the same GVC and pull at least one model, then install Open WebUI withollama.workloadName set to that workload’s name — its models appear in the model picker automatically. To use a hosted provider instead, create the API-key secret (see Prerequisites), set openai.apiKeySecretName, and Open WebUI lists that provider’s models. If a configured Ollama backend is unreachable the UI still boots and simply shows no Ollama models — confirm ollama.workloadName names a ready Ollama workload in the same GVC.
Backing Up
Backups are scheduled volume snapshots managed by the platform — no cloud account or bucket is required. On the configured cron schedule the platform takes a crash-consistent snapshot of the data volume; SQLite recovers cleanly from one. Snapshots are pruned automatically afterbackup.retention, and a final snapshot is always taken when the release is uninstalled.
- Default schedule — Daily at 03:00 UTC (
backup.schedule: "0 3 * * *"), kept for 7 days (backup.retention: 7d). - Minimum interval — The platform does not accept schedules more frequent than hourly.
Snapshots live in the platform storage layer alongside the volume, not off-site. They protect against data corruption and accidental changes, but losing the whole GVC would lose them too.
Restoring a Backup
Restore is in-place on the release’s own volume set: the platform provisions a fresh volume from the chosen snapshot and swaps it in, then the workload restarts to remount it.1
Find the snapshot to restore
List snapshots and note the
name, location, and volumeIndex of the one you want:2
Restore it in place
Provision a fresh volume from the snapshot and swap it in. The workload restarts to remount it:
3
Verify
Once the workload is ready again, log in and confirm your chats and settings are present.
Important Notes
- License / branding clause — You must keep the “Open WebUI” branding visible in the UI unless your deployment serves 50 or fewer users, or you have enterprise permission. Removing the branding outside those cases violates the license; it is not a template setting.
- The first user to register becomes the admin. Sign-ups are open by default so the install is immediately usable, which means anyone reaching the public endpoint can register while it is open. Register your admin account first, then set
auth.enableSignup=falseto lock it down. auth.webuiSecretKeymust never change after first install. It is the key that signs session tokens and JWTs. Rotating it — or letting a fresh volume regenerate one — logs every user out. Override it once withopenssl rand -base64 32and keep it stable.- Single replica, by design. The embedded SQLite is single-writer and the volume set is per-replica, so the workload is pinned to one replica with no
replicasknob. A restart or upgrade is a brief full outage (about a minute). - Model-backend settings apply at install, then persist in the app database.
ollama.workloadNameandopenai.*are read from the environment only on the first boot and then stored inwebui.db. Changing them via a laterhelm upgradeis silently ignored — update model connections afterward from the admin UI (Settings → Connections). - Data lives only on the volume set. Uninstall deletes it (a final snapshot is taken first); a reinstall starts empty. Changing the secret and redeploying does not re-key existing data.
- Backups are in-platform, not off-site. Scheduled snapshots and the final snapshot on uninstall live in the platform storage layer next to the volume; losing the whole GVC would lose them too. See Backing Up.
External References
Open WebUI on GitHub
Upstream source repository
Open WebUI Documentation
Official documentation and getting-started guides
Environment Variable Reference
Full list of supported configuration variables
License
The Open WebUI License and its branding clause
Ollama Template
Deploy the in-GVC Ollama model backend
Open WebUI Template
View the source files, default values, and chart definition