---
title: "Deploy Uptime Kuma with Persistent Storage"
description: "Uptime checks, alerts and status pages with persistent monitor data."
category: "Observability"
url: https://railway.com/deploy/uptime-kuma-with-persistent-storage
---

# Deploy Uptime Kuma with Persistent Storage

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

**[Deploy Uptime Kuma with Persistent Storage on Railway](https://railway.com/template/uptime-kuma-with-persistent-storage)**

Machine-readable deploy manifest (JSON, validated by TemplateCI): https://railway.com/deploy/uptime-kuma-with-persistent-storage/manifest.json

- **Creator:** dankeewithtwoes's Projects
- **Category:** Observability

## Template content

### Uptime Kuma

- **Image:** louislam/uptime-kuma@sha256:9912da7d7d9b6ddc0c2d904beb84d24689c1ed9c33b81419eb9008663a92a329
- **Health check:** /
- **Public domain:** Yes

## Documentation

# 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

1. Deploy the template and open its generated domain.
2. Create the administrator account immediately.
3. Add your first HTTP, TCP or keyword monitor.
4. 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](https://github.com/louislam/uptime-kuma)


## Similar templates

- [Rootprint](https://railway.com/deploy/rootprint-1) — Open-source logs and traces with full-text search on object-storage.
- [Pyroscope profiling](https://railway.com/deploy/pyroscope-profiling) — Protected continuous profiling with durable Pyroscope storage.
- [SigOnly](https://railway.com/deploy/sigonly) — Deploy SigNoz with a working demo app & config in one click

Open this page in a browser: https://railway.com/deploy/uptime-kuma-with-persistent-storage