Deploy and Host uptimekit on Railway

Important: read the “Important Notes” section below before deploying/using this template.

UptimeKit is an open-source uptime monitoring platform for tracking service availability, incidents, and performance over time. It includes a dashboard to manage monitors, a scheduler for background checks, a public status page for incident communication, and analytics storage backed by Postgres, Redis, and ClickHouse.

About Hosting uptimekit

Hosting uptimekit involves running multiple services that work together: the Dashboard (UI and core API), the Scheduler (background jobs and monitoring orchestration), the Status Page (public-facing pages), and a Worker (executes monitoring work). Data services include Postgres for primary application data, Redis for queues/caching, and ClickHouse for high-volume event and time-series analytics. On Railway, each service is deployed independently and connected via private networking, making it easy to scale services as your monitoring needs grow.

Common Use Cases

• Monitoring internal services and public endpoints with uptime history and incident tracking
• Publishing a public status page for customers and stakeholders during outages
• Collecting long-term performance/availability analytics for SLA reporting

Dependencies for uptimekit Hosting

• Postgres
• Redis
• ClickHouse

Deployment Dependencies

• Project repository: https://github.com/uptimekit/uptimekit
• Documentation: https://docs.uptimekit.dev/
• LLM docs index: https://docs.uptimekit.dev/llms.txt

Important Notes

• Status pages are served under the Status Page service public URL. Example: if you create a status page with slug test, it will be available at https:///test.
• The Worker service is deployed by this template with a placeholder WORKER_API_KEY. After deploying, generate a Worker in the Dashboard and replace the Worker service’s WORKER_API_KEY with the generated value.
• Worker “regions” configured in the Dashboard do not change where checks run. When hosted on Railway, each Worker executes from the Railway service’s deployment region. For multi-region monitoring, deploy multiple Worker services in different Railway regions and assign each its own WORKER_API_KEY.
• Changing the Status Page domain in the Dashboard UI does not affect routing on Railway. To use a custom domain, configure it on the Status Page Railway service -> public networking settings.

Why Deploy uptimekit 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 uptimekit 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.