Deploy and Host Wizarr on Railway

Wizarr is a self-hosted invitation and onboarding portal for operators of Plex, Jellyfin, Emby, Audiobookshelf, RomM, Komga, and Kavita servers. This community template runs the pinned Wizarr container on Railway with persistent /data, a generated public domain, safe defaults, and no credentials or media-server integration preconfigured. It is not affiliated with the Wizarr project.

About Hosting Wizarr

This template deploys one public Wizarr service on Railway's generated HTTPS domain and routes application traffic to the container's fixed port 5690. The attached /data volume stores Wizarr's persistent application state. The image is pinned by immutable digest, while the template supplies deterministic values for PUID, PGID, DISABLE_BUILTIN_AUTH, PORT, and TZ. After deployment, configure only media servers and users that you are authorized to manage or invite. No source credentials or customer data are included.

Common Use Cases

Create invitation links for an authorized household or community media server.
Guide new users through installing and connecting their approved media applications.
Centralize onboarding steps and invitation access without exposing the media server itself.

Dependencies for Wizarr Hosting

Deployment Dependencies

Wizarr: pinned container image, public HTTP service on port 5690, and persistent /data volume.
Railway: generated HTTPS domain, deployment health check at /, and volume-backed application state.
Operator configuration: a media-server integration and invitation policy must be configured after deployment using services and accounts the operator is authorized to manage.

Implementation Details

The template uses the community-maintained Wizarr container at the reviewed immutable digest. Built-in administrator authentication remains enabled, the container timezone is UTC, and Railway's ON_FAILURE restart policy allows up to 10 retries. This template intentionally omits app_proxy, custom domains, TCP proxies, credentials, and preconfigured media-server integrations.

Why Deploy Wizarr on Railway?

Railway provides managed HTTPS, deployment history, health checks, logs, and persistent volumes in one repeatable deployment. The template keeps the Wizarr application public while its persistent state remains on the attached volume.

For application setup and operator guidance, see the Wizarr documentation and Railway volume documentation. Operators remain responsible for lawful use and for sharing only media-server content and invitations they are authorized to manage.