comparing platforms
The Better Uptime (Better Stack) alternative you self-host
Better Uptime rebranded to Better Stack, and if it got too expensive or you want your data on your own servers, Uptimepage is a focused monitor and status page you run yourself. One binary, open source under AGPL, and everything you can click you can also declare in code. Start free on the hosted 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 | Better Stack | |
|---|---|---|
| fastest check interval | 60s hosted · 10s self | 3 min free · 30s paid |
| check types | HTTP · TCP · DNS · TLS · domain · ping · heartbeat · flow | HTTP · TCP · UDP · DNS · mail · ping |
| ping / ICMP | yes | yes |
| push / heartbeat monitor | yes | 1s heartbeat |
| TLS + domain expiry | yes | yes |
| branded status page | yes | white-label |
| status-page subscribers | email + webhook | 1,000 included |
| on-call & escalation | yes | yes |
| multi-region probes | yes | 4 regions |
| config-as-code | Terraform · REST · MCP | Terraform · REST |
| teams / RBAC + SSO | orgs + roles | RBAC + SSO |
| self-host (open source) | yes · AGPL | no |
| price to start | free, no card | free 10 · paid $29/mo |
Better Stack's free plan covers 10 monitors at 3-minute checks with 1 status page; 30-second checks and other paid features start around $29/month. It is a hosted service, not open-source or self-hostable.
Better Stack takes heartbeats as often as every second and covers more check types than Uptimepage does. Uptimepage is AGPL and self-hostable, adds an MCP server, and starts free with no card.
Verified against betterstack.com/pricing in July 2026. SaaS plans change, so check their current pricing before you decide.
Yours to run
The whole thing ships as one self-contained binary. `docker compose up` brings up the monitor with Postgres and ClickHouse, migrations run on boot, and the source is AGPL if you’d rather host it on your own servers.
No clicking through a UI
Declare monitors, status pages and notification channels in HCL with the official Terraform provider, and point an LLM client at the MCP server to read your monitoring, with every write waiting on your approval.
Checks from your own regions
Run region agents on your own machines, wherever your customers actually are; each one authenticates with a scoped, org-bound token.
Where Uptimepage fits
Uptimepage is deliberately smaller: uptime monitoring and a status page, with no log platform or incident suite beside them. It is one Rust binary with Postgres and ClickHouse, so self-hosting is a compose file rather than a project, and the licence is AGPL, so leaving the hosted tier is a migration instead of a rewrite. Checks run from several regions, and you can run your own probe agent for targets that never leave your network.
- 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