Deploy OneUptime
Uptime monitoring, status pages, incidents, on-call and OpenTelemetry
Just deployed
/var/lib/postgresql/data
Just deployed
Just deployed
Just deployed
clickhouse
Just deployed
/var/lib/clickhouse
Redis
Just deployed
/data
Just deployed
Deploy and Host OneUptime on Railway
OneUptime is an open-source observability platform. It monitors websites, APIs, ports and SSL certificates, publishes status pages, manages incidents, alerts and on-call schedules, and collects logs, metrics and traces over OpenTelemetry. It is a self-hosted alternative to tools such as Pingdom, Statuspage.io, PagerDuty and Datadog, licensed under Apache 2.0.
About Hosting OneUptime
OneUptime runs as several services. This template deploys OneUptime 16.0.0 as seven Railway services wired over the private network: the ingress gateway (the only public service), the app (dashboard, API, status pages, workers and telemetry ingest), a probe that runs your monitors, the global runner for workflow and runbook steps, ClickHouse for telemetry, Railway PostgreSQL and Railway Redis. Every secret is generated at deploy time and every data store has its own volume. The app applies its database migrations on boot, and the other services wait for it. The first start takes a few minutes. Then open the ingress URL and sign up. The first account becomes the admin.
Common Use Cases
- Uptime and API monitoring with alerts, from a probe you host yourself
- Public or private status pages with incident and scheduled-maintenance updates
- On-call schedules, escalation policies and incident management
- Collecting OpenTelemetry logs, metrics and traces in one place
Dependencies for OneUptime Hosting
- PostgreSQL (Railway PostgreSQL, bundled) for accounts, projects, monitors and incidents
- Redis (Railway Redis, bundled) for the cache and job queues
- ClickHouse 26.7 (bundled, built from the template repo) for logs, metrics, traces and monitor history
Deployment Dependencies
- OneUptime on GitHub and its 16.0.0 release
- OneUptime documentation
- Template repository, with the pinned images and the changelog
Implementation Details
The services in this template:
ingress: OneUptime's nginx gateway on the public Railway domain. It routes the dashboard, API, status pages and OTLP ingest (https://YOUR-DOMAIN/otlp) to the app.app: the main OneUptime server. It is private and reached through the ingress.probe: a global probe ("Railway Probe") that every project can use for monitors.runner: the global runner for workflows and runbooks.clickhouse: OneUptime's one-node ClickHouse cluster with embedded Keeper and a volume at/var/lib/clickhouse.PostgresandRedis: Railway's own databases, each with a volume.
After the first deploy:
- Open the ingress URL and sign up. The first account becomes the instance admin.
- Open
https://YOUR-DOMAIN/admin/setupto set up email (SMTP, SendGrid, Mailgun, Postmark, Resend or Amazon SES), and optionally SMS and calls. Outbound SMTP needs Railway's Pro plan, so on other plans use an API-based email provider. Until email is set up, OneUptime can't send invitations or alerts by email. - To stop strangers from signing up, turn off sign-ups in the Admin Dashboard settings.
- To use your own domain, add it to the
ingressservice in Railway and setHOSTon bothingressandappto that domain.
Not included: OneUptime's optional ClamAV file scanner and a second probe. Railway exposes no UDP ports, so the probe's SNMP-trap, syslog and NetFlow receivers are turned off, and ICMP ping monitors may not work. The services use about 2.5 GB of memory in total when idle, so use a Hobby or Pro plan.
Updates: the services build from the template's GitHub repository, with each image pinned by version and digest. When a new OneUptime version is published to the repository, Railway shows an update notice in your project. Read the repository's CHANGELOG.md before you apply it, and back up PostgreSQL and ClickHouse before a major upgrade.
Why Deploy OneUptime 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 OneUptime 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.
Template Content

