Self-host Open WebUI with Levelrail

Verified

A self-hosted chat interface for running local large language models through Ollama.

  • Authoropen-webuiVerified by Levelrail
  • LicenceLicenseRef-Open-WebUI
  • Memory1 GiB
  • Archarm64
  • Services2

How to self-host Open WebUI

  1. Pull the images

    2 images are pulled on your server.

    Show images
    • ollama/ollama:0.33.3
    • ghcr.io/open-webui/open-webui:0.11.3
  2. Create the app

    2 services start in a single Compose app, with 2 named volume mounts for your data, on port 8080.

  3. Fill in the secrets

    1 secret is generated and stored encrypted, 1 setting is preset, you do not have to fill in anything.

  4. Open it

    Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.

Open WebUI requirements

Memory
About 1 GiB
Architectures
amd64 image published, arm64 tested
Ports
8080
Domain
Optional, an sslip.io address is used without one
Settings
none to fill in
License
LicenseRef-Open-WebUI, source available
  • Verified. Verified on arm64 with image tag 0.11.3. Our CI ran this exact image version and it answered on its health path. Evidence
  • Host ports. It publishes port 8080 on the host, so open them in the VPS firewall only if you want that.

Install Levelrail first

On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Open WebUI. New to Levelrail? Install it on a fresh VPS first.

docker pull ghcr.io/glincker/levelrail:latest

Then levelrail-cli login --device. See Getting started and the Open WebUI docs page.

Deploy Open WebUI your way

Every format below deploys the same pinned images. Pick the one that fits how you work.

Deploy Open WebUI from the CLI

levelrail-cli templates deploy open-webui --name my-open-webui

Deploy Open WebUI with the API

Create a token in the dashboard first. This one-click route deploys it as a trial app you can keep or remove.

curl -X POST -H "Authorization: Bearer $TOKEN" \
  https://levelrail.example.com/api/v1/service-templates/open-webui/deploy

Open WebUI configuration

Open WebUI services

ServiceImagePortsVolumes
ollama ollama/ollama:0.33.3 none ollama_data -> /root/.ollama
open-webui ghcr.io/open-webui/open-webui:0.11.3 8080 openwebui_data -> /app/backend/data

Open WebUI environment variables

VariableServiceValue
OLLAMA_BASE_URL open-webui Preset by the template
WEBUI_SECRET_KEY open-webui Generated at deploy

Ports and volumes

Ports
8080
Volumes
2 named mounts: ollama_data -> /root/.ollama, openwebui_data -> /app/backend/data

Open WebUI FAQ

How much memory does Open WebUI need?

The catalog lists about 1 GiB of memory for Open WebUI across its 2 services.

Does Open WebUI run on arm64?

For Open WebUI, arm64 is tested; amd64 is image published.

What licence is Open WebUI under?

Open WebUI is licensed under LicenseRef-Open-WebUI, which is source-available, so read the terms before commercial use.

Does Open WebUI need configuration before it starts?

No. The template fills in its own defaults and generates secrets at deploy time.

Which ports does Open WebUI use?

Open WebUI listens on port 8080 inside the stack.

Where does Open WebUI keep its data?

In named volumes: ollama_data mounted at /root/.ollama and openwebui_data mounted at /app/backend/data.

Can I deploy Open WebUI on Dokploy or Dokku?

The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list has an entry with the id open-webui for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image ollama/ollama:0.33.3, ghcr.io/open-webui/open-webui:0.11.3 is what you deploy there.

levelrail-cli templates deploy open-webui --name my-open-webui