Deploy Healthchecks
Cron job monitoring: get alerted when a scheduled job doesn't check in
Healthchecks
Just deployed
Just deployed
/var/lib/postgresql/data
Deploy and Host Healthchecks on Railway
Healthchecks monitors cron jobs and background tasks. Each job pings a unique URL when it runs, and if a ping is late, Healthchecks alerts you. Alerts go to Slack, Discord, Telegram, email, webhooks, ntfy, PagerDuty and 20+ other channels.
About Hosting Healthchecks
This template runs the official healthchecks/healthchecks image (uWSGI + Django) with Railway Postgres. On every deploy, a pre-deploy step runs the database migrations and creates your admin account from ADMIN_EMAIL and ADMIN_PASSWORD. You can log in immediately, with no shell and no SMTP needed. Public sign-up is off by default.
The alert sender (sendalerts) and the report sender (sendreports) run inside the same container, so there is only one app service to pay for.
Common Use Cases
- Know when a nightly backup, cron script or Railway cron service silently stops running.
- Monitor background workers and queues with start and finish pings that track run time.
- Give a team a shared dashboard and status badges for scheduled jobs.
Dependencies for Healthchecks Hosting
- PostgreSQL (included)
Deployment Dependencies
- Upstream:
- Self-hosting docs:
- Configuration reference:
Implementation Details
| Variable | Default | Notes |
|---|---|---|
ADMIN_EMAIL | (you set it) | Superuser login |
ADMIN_PASSWORD | random | Copy it from the service's Variables tab |
SITE_ROOT | https://${{RAILWAY_PUBLIC_DOMAIN}} | Change it if you add a custom domain |
ALLOWED_HOSTS | public domain + healthcheck.railway.app | Add your custom domain here too |
REGISTRATION_OPEN | False | Set True to allow public sign-up |
EMAIL_HOST and other EMAIL_* | empty | Optional SMTP for email alerts and invites |
UWSGI_PROCESSES | 2 | Keeps RAM low; raise it for heavy ping traffic |
- Pings:
https:///ping/. Usecurl -fsS -m 10 --retry 5 -o /dev/nullat the end of a job. - Healthcheck: Railway probes
/api/v3/status/, which also checks the database connection. - Email: some Railway plans restrict outbound SMTP. Chat, webhook and push integrations work without email.
- Changing
ADMIN_PASSWORDlater doesn't reset an existing account. Change your password in the UI instead.
Why Deploy Healthchecks on Railway?
Railway is a single platform for deploying your whole stack: servers, databases, AI agents and more. It handles the infrastructure, so you don't have to manage servers or configure scaling.
When you deploy Healthchecks on Railway, you're one step closer to running your full stack with minimal effort. Host your servers, databases, AI agents and more on Railway.
Template Content
Healthchecks
healthchecks/healthchecks:v4.4ADMIN_EMAIL
Email of the superuser created on first deploy (used to log in).


