comparing open source
A OneUptime alternative that’s quick to run
Uptimepage is open source and focused on two jobs done well: uptime monitoring and a public status page. One binary plus two databases, up with a single command, or skip hosting it and use the free tier. No card.
The table below is the whole comparison, unedited. Read it first if you like, it is the same one we would send you.
AGPL-3.0 · one binary · free tier · no card required
How they compare
| Uptimepage | OneUptime | |
|---|---|---|
| fastest check interval | 60s hosted · 10s self | 60s |
| check types | HTTP · TCP · DNS · TLS · domain · ping · heartbeat · flow | 25+ types |
| ping / ICMP | yes | yes |
| push / heartbeat monitor | yes | yes |
| TLS + domain expiry | yes | yes |
| branded status page | yes | yes |
| status-page subscribers | email + webhook | email · SMS · Slack |
| auto incidents from checks | yes | yes |
| on-call & escalation | yes | yes |
| multi-region probes | yes | yes |
| config-as-code | Terraform · REST · MCP | Terraform · CLI |
| tech stack | Rust | TypeScript |
| deploy footprint | 1 binary + 2 DBs | 6-14 services |
| license | AGPL-3.0 | Apache-2.0 |
OneUptime is a broad incident platform (monitoring, status pages, on-call, logs and tracing) that runs as 6-14 services with Postgres, ClickHouse and Redis; Uptimepage is a single binary with Postgres and ClickHouse.
OneUptime covers more check types than Uptimepage does; Uptimepage runs a tighter footprint and a faster self-hosted interval.
Verified against OneUptime 11.0.12 source in July 2026. Fast-moving project, so check the current source before you decide.
Up in minutes
One self-contained binary, Postgres for config and ClickHouse for the time-series. `docker compose up` and the whole stack is running with migrations applied. Nothing else to set up first.
Drive it from a repo
An official Terraform provider for monitors, status pages and channels, plus an MCP server so an LLM client can read your monitoring, with writes gated behind your approval and audited. Review your monitoring in a pull request.
Hosted or self-hosted, you choose
Start on the free hosted tier with no card, or run the AGPL source yourself. Switching later is an endpoint change, not a migration.
Where Uptimepage fits
Two jobs done properly, with no platform built around them. Checks over HTTP, TCP, DNS, TLS, domain expiry, ping, heartbeat and browser flows, organizations with roles, a Terraform provider, a REST API and an MCP server, and a branded status page where incidents open on their own and customers subscribe by confirmed email or signed webhook. One binary and two databases, up with a single command, or hosted free with no card.
- 01Sign in with GitHub or Google. No card, no sales call.
- 02Paste a URL. The first check runs before you have finished reading this.
- 03Publish the status page, or export it to Terraform and keep it in Git.
api99.98%
p95 142ms · one incident in 45 days
dashboard99.91%
p95 318ms · two degraded days
webhooks99.99%
p95 88ms · no incidents
RESOLVED14 min
Elevated latency on the dashboard API
14:22 resolved, latency back under 300ms
14:08 opened automatically by the dashboard check
up degraded down 45 days · email & webhook subscribers