How do I deploy Railway Uptime Monitor on Railway?

You can deploy Railway Uptime Monitor on Railway by clicking the "Deploy Now" button on this page. Railway will automatically set up all the necessary services and configurations for you.

What are the system requirements?

Railway handles all the infrastructure requirements. You only need a web browser to deploy and manage your application.

Is this template free to use?

Yes, this template is free to use within your existing Railway account.

Can I customize this template?

Yes, you can fully customize this template. After deployment, you will have full control of what you've deployed in your Railway project.

How do I get support for this template?

You can get support through our community forum: railway-uptime-monitor-881176b1, or click "Get template help" for this template for more assistance.

Deploy Railway Uptime Monitor

Deploy and Host Railway Uptime Monitor on Railway

Railway Uptime Monitor is a lightweight monitoring service built for Railway projects. It discovers services in your target environment, performs recurring HTTP health checks, tracks outages and recoveries, and sends alerts to Slack, Discord, Telegram, or email. It supports both private Railway networking and public domains with configurable reliability thresholds.

About Hosting Railway Uptime Monitor

Hosting this template on Railway involves deploying a Bun-based worker service, configuring a few environment variables, and attaching persistent storage for SQLite state. You provide a Railway API token plus target project/environment IDs, and the monitor continuously discovers services and checks their health endpoints. Optional notifier variables enable incident alerts through your preferred channels. A mounted volume keeps monitor history and incident state durable across restarts and deploys. The service also exposes a health endpoint for platform-level health checks. Once deployed, it runs continuously with configurable intervals, timeouts, expected status code ranges, and failure/recovery thresholds.

Common Use Cases

Monitor internal microservices over Railway private networking and alert on downtime.
Track production API availability and notify incident channels on failures and recovery.
Centralize uptime checks for multi-service Railway environments with persistent incident history.

Dependencies for Railway Uptime Monitor Hosting

Railway API token with access to the monitored project/environment.
Persistent volume mounted at /data with DATABASE_PATH=/data/monitor.db.

Deployment Dependencies

Implementation Details

# Required
RAILWAY_API_TOKEN=ra_...
RAILWAY_PROJECT_ID=...
RAILWAY_ENVIRONMENT_ID=...

# Recommended for persistence
DATABASE_PATH=/data/monitor.db

# Optional behavior tuning
DISCOVERY_INTERVAL_SECONDS=120
CHECK_INTERVAL_SECONDS=30
CHECK_TIMEOUT_MS=5000
FAILURE_THRESHOLD=3
RECOVERY_THRESHOLD=2
EXPECTED_STATUS_MIN=200
EXPECTED_STATUS_MAX=299
TARGET_DOMAIN_MODE=private  # private|public|auto

Why Deploy Railway Uptime Monitor 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 Railway Uptime Monitor 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.