Deploy and Host Open WebUI on Railway

Published on the Railway marketplace: https://railway.com/deploy/open-webui-7 (category: AI/ML).

Open WebUI is a self-hosted AI chat interface for local and hosted language models. It provides a polished multi-user web experience, conversation history, model management, file and knowledge features, and connections to Ollama, OpenAI, and other OpenAI-compatible APIs while keeping application data under the deployer's control.

About Hosting Open WebUI

Hosting Open WebUI on Railway requires one public container and one persistent volume. This package pins the official Open WebUI v0.11.0 image, exposes container port 8080 through Railway HTTPS, checks the image-supported /health endpoint, and mounts /app/backend/data for the SQLite database, uploads, vector data, caches, and configuration. Authentication remains enabled. The first account is promoted atomically to administrator even though later signup is disabled, preventing an unclaimed public registration window after setup. Railway generates the JWT/session secret once per deployment. Ollama and OpenAI-compatible URLs and API keys remain optional no-default inputs and can also be configured later from the administrator UI.

Common Use Cases

Chat with local Ollama models from a browser
Use OpenAI or another OpenAI-compatible model provider through one self-hosted interface
Build private team workflows around conversations, files, knowledge bases, tools, and model access controls

Dependencies for Open WebUI Hosting

The official ghcr.io/open-webui/open-webui:v0.11.0 container image
One Railway persistent volume mounted at /app/backend/data
An optional reachable Ollama server or OpenAI-compatible provider
An optional provider-issued API key when the selected endpoint requires authentication

Deployment Dependencies

Implementation Details

Service: one service named exactly Open WebUI uses ghcr.io/open-webui/open-webui:v0.11.0 and targets public port 8080.
Authentication: WEBUI_AUTH=True keeps login protection enabled. ENABLE_SIGNUP=False blocks additional public registrations, while Open WebUI v0.11.0 still permits the first account and promotes that account to admin. DEFAULT_USER_ROLE=pending is defense in depth if an administrator later enables signup.
Secret handling: WEBUI_SECRET_KEY is generated once as a 64-character hexadecimal template value. No live source-project secret is copied into the package.
Optional providers: OLLAMA_BASE_URL, OPENAI_API_BASE_URL, and OPENAI_API_KEY are optional no-default deployer inputs. No endpoint-shaped placeholder or generated external credential is supplied.
Health and persistence: Railway checks GET /health, whose v0.11.0 response is {"status":true}. The /app/backend/data volume retains accounts, application configuration, chats, uploads, and local database state across restarts.
Scaling boundary: the default embedded SQLite database and attached Railway volume make this a single-replica deployment. Use an upstream-supported external database and shared storage design before attempting horizontal scaling.

Why Deploy Open WebUI on Railway?

Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.

By deploying Open WebUI on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.

This is a community deployment package and is not affiliated with or endorsed by Open WebUI. Open WebUI names and artwork belong to their respective owners.