Deploy and Host On-call Notification Router with Apprise on Railway

An authenticated notification router with persistent provider routes.

About Hosting On-call Notification Router with Apprise

Small on-call teams consolidating alert delivery from scripts.

Sign in through the operator gateway, create a route configuration with your own provider URLs and send a test notification. Scripts must authenticate to the gateway with Basic auth. Use curl -u operator:YOUR_PASSWORD and the upstream /notify endpoint.

Included services and storage

Service	Persistent storage	Public access
App	/config	Private network only
Gateway	None; container state is disposable	HTTPS domain

First deployment

Review required inputs in the deploy form and supply your own administrator email where requested.
Deploy the services and wait for the application and any database migrations to finish.
Open the generated HTTPS domain and follow the workflow above.
For the first browser prompt use username operator and the generated Gateway.GATEWAY_PASSWORD from Railway variables. App-specific accounts, where present, remain separate. The App service has no public domain.

Why Deploy On-call Notification Router with Apprise on Railway

The definition supplies an HTTPS endpoint, generated credentials where supported and explicit storage paths. PostgreSQL, when present, stays private. Public upstream image manifests are locked to immutable digests so an upstream tag change does not silently replace a running version.

Common Use Cases

Route a backup-script alert.
Fan out a deployment notification.
Keep notification destinations outside application code.

Dependencies for On-call Notification Router with Apprise

Upstream application and its documentation. The upstream authors own the application and its license. This recipe does not claim application authorship or official endorsement.
Caddy gateway using generated Basic authentication and WebSocket-capable reverse proxying.
A Railway plan with resources sufficient for these services. Hosting, storage and outbound traffic are billed by Railway; no software subscription, bank connection, SMTP account or provider credit is included.

Operational limits and backups

The template includes no messaging accounts or delivery credits. Provider URLs can contain secrets and are stored on the /config volume. Attachments are disabled. This is a notification gateway, not an alert scheduler or an end-to-end delivery guarantee.

Run one replica for volume-backed applications. Schedule volume backups and export important application data; a persistent volume is not a backup. Keep generated secrets with the backups and review upstream migration notes before changing the pinned image. Credentials cannot all be rotated by changing first-run environment variables after accounts already exist.

Validation status

Prepared on 2026-10-18 from upstream installation documentation and public image manifests. Railway schema, variable references and publication metadata are checked before publication. Application runtime boot checks were not performed. This is an independently authored deployment recipe for existing software, not a claim of novel software, audited security or Railway partner verification.

Deploy this recipe

Review the required inputs and hosting resource costs before deploying.

Related deployment recipes

ntfy Private Notifications with Persistent Data — Private push notifications with generated admin and persistent storage.
n8n with PostgreSQL & Durable Storage — Workflow automation with private Postgres, durable files and webhook URLs.
Uptime Kuma with Persistent Storage — Uptime checks, alerts and status pages with persistent monitor data.

These are separate deployments; no preconfigured integration between the applications is implied.

Disclosure: this template is maintained independently. Its maintainer may earn Railway usage kickbacks when other people deploy it. Railway bills hosting separately; no paid software subscription or provider credits are included.