Deploy and Host Uptime Kuma with Persistent Storage on Railway

Uptime checks, alerts and status pages with persistent monitor data.

About Hosting Uptime Kuma with Persistent Storage

Deploying this template creates Uptime Kuma in your Railway project. The application receives an HTTPS domain automatically. Database and Redis services, when included, use private networking and generated credentials. Persistent data is stored on the included volumes or object storage, so application redeploys do not discard it.

Why Deploy Uptime Kuma with Persistent Storage on Railway

Official Uptime Kuma v2 image.
The /app/data volume retains monitors, settings, status pages and notification credentials.
Automatic HTTPS domain and Railway health check.

Common Use Cases

Alert when a website, API or TCP endpoint stops responding.
Track service response times and uptime history.
Publish a status page for customers.

Dependencies for Uptime Kuma with Persistent Storage

A Railway account and a plan with capacity for 1 service(s).
Included services: Uptime Kuma.
1 persistent volume(s), provisioned by this template.
External integrations, mail delivery and your own business data are configured after installation as needed.

First launch

Deploy the template and open its generated domain.
Create the administrator account immediately.
Add your first HTTP, TCP or keyword monitor.
Configure a notification provider in the application, then create a status page if you need one.

Operations

Keep this service running continuously for reliable monitoring; sleeping it stops checks and alerts. Back up the data volume before upgrades. This template runs one monitor instance and does not provide independent monitoring of Railway itself. Notification provider credentials are configured in Uptime Kuma after setup.

Images are pinned to verified upstream image digests captured on 2026-10-17. Review upstream release notes, back up persistent data and update the image deliberately when upgrading. Railway charges the deployer for running services, storage and network usage.

Support and upstream

For Railway template wiring or deployment issues, use the discussion/support link on this template page. Include service names and redacted logs; omit passwords and tokens. Application documentation:

Uptime Kuma source and documentation

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.
Gotenberg PDF API with Authentication — PDF conversion API with generated Basic Auth and private URL filtering.

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.