#1★ TOP PICK
Uptime Kuma
The self-hosted monitor that beat the paid ones on features.
96
OPEN SOURCEMITSELF-HOSTLOCAL-FIRST
Uptime Kuma is a self-hosted monitoring tool that does, for free and on your own server, most of what the paid services charge monthly for: HTTP, TCP, ping, DNS and keyword checks, 60-second intervals, a genuinely good dashboard, public status pages, and notifications to more than ninety services including Slack, Discord, Telegram, email and webhooks. It runs as one Docker container on hardware you already have. At roughly 89.7k GitHub stars it is one of the most-starred self-hosted projects in existence, and that popularity is deserved rather than fashionable — the free tiers of the commercial services are more limited than this is. MIT licensed, pushed to daily.
Strengths
- +60-second checks and unlimited monitors with no plan to upgrade to
- +Public status pages included rather than sold separately
- +Notifications to 90+ services out of the box
- +MIT, one container, and the most-starred tool in the category
Trade-offs
- −It runs on your infrastructure — so it cannot tell you your infrastructure is down
- −Single-node by design; no multi-region checking
- −You own updates, backups and the uptime of the uptime monitor
- −No phone-call escalation or on-call rotation
Free and open source. One Docker container on a server you already run. #2
Gatus
Monitoring as a YAML file, for people who already run everything from Git.
94
OPEN SOURCEApache-2.0SELF-HOSTLOCAL-FIRST
Gatus is a developer-first health-check service configured entirely in YAML, which means your monitoring lives in the repository, gets reviewed in pull requests, and is deployed like any other code. It handles HTTP, TCP, ICMP, DNS and TLS-expiry checks, evaluates rich conditions on responses — status code, body content, response time, certificate age — and ships a clean dashboard and status page. Apache-2.0, around 11.7k stars, actively developed. It is the natural pick for a team already doing GitOps, and the wrong one if a non-engineer needs to add a monitor.
Strengths
- +Configuration is YAML in Git — reviewed, versioned and diffable
- +Rich condition evaluation, including response body and TLS expiry
- +Apache-2.0 with no enterprise carve-out
- +Very light: one small binary, minimal memory
Trade-offs
- −No UI for adding monitors — everything is a config change
- −Same blind spot as any self-hosted monitor: it can go down with you
- −Fewer notification integrations than Uptime Kuma
- −Not usable by non-technical team members
Free and open source. A single binary or container. #3
Statping-ng
A self-hosted status page in one binary — but check the commit dates.
78
OPEN SOURCEGPL-3.0SELF-HOSTLOCAL-FIRST
Statping-ng is the community continuation of Statping: a single Go binary that monitors services and renders a public status page, with no database server required for small deployments. GPL-3.0, and the design is genuinely nice. The reason it is ranked where it is rather than higher is a fact worth stating plainly: its last push was 2025-06-04, more than a year ago. That is not automatically disqualifying for a small, feature-complete tool, but unmaintained software that faces the public internet is a security decision rather than a convenience one, and anyone choosing it should do so knowingly.
Strengths
- +Single binary with a good-looking status page out of the box
- +No database server needed for small deployments
- +GPL-3.0 with no enterprise carve-out
- +Lightweight enough for the smallest VPS
Trade-offs
- −Last commit 2025-06-04 — effectively dormant, and it is internet-facing
- −Small community, so few answers when something breaks
- −Fewer notification integrations than Uptime Kuma
- −Uptime Kuma does everything it does and is actively maintained
Free and open source. One binary, no database server required for small setups. #4
UptimeRobot
Hosted checks from outside your network, with a free tier that is actually usable.
48
SOURCE-AVAILABLEProprietary (hosted service)
UptimeRobot is the hosted answer, and it solves the one problem no self-hosted monitor can: it watches your site from outside your own infrastructure, so when your server, your network or your data centre goes down, the thing telling you about it is not also down. The free tier is unusually generous — 50 monitors at 5-minute intervals, email alerts and a public status page — which is more than enough for most personal sites and small businesses. Paid plans add 30-second checks, SMS and voice alerts, and multi-location verification to cut false alarms. It is proprietary and hosted, which is why it scores where it does; it is on this page because external monitoring is a real requirement and pretending otherwise would not serve the reader.
Strengths
- +Checks from outside your network — the one thing self-hosting cannot do
- +Free tier covers 50 monitors, which is genuinely enough for most people
- +Nothing to install, patch or keep running
- +Multi-location verification cuts false alarms from transient network blips
Trade-offs
- −Proprietary and hosted — you do not own the monitoring or its history
- −Free tier is capped at 5-minute checks, so a short outage can be missed
- −SMS and voice alerts are paid add-ons
- −Your uptime data lives in a third party's system
Free tier: 50 monitors at 5-minute checks, with a public status page. Paid plans add 30-second intervals, SMS/voice alerts and multi-location checks. Checked 2026-08-01. #5
Instatus
A fast, cheap status page that does the one job well.
44
SOURCE-AVAILABLEProprietary (hosted service)
Instatus is a focused competitor to Statuspage: fast pages, unlimited subscribers on paid plans rather than metered ones, custom domains, and a free tier that is genuinely usable. It is proprietary and hosted, and it is here because subscriber-metered pricing is the specific complaint that sends people looking, and Instatus's answer to it is to not meter subscribers. For a team that wants a customer-facing status page and does not want to self-host one, it is usually the cheaper straight swap.
Strengths
- +Does not meter subscribers, which is Statuspage's sharpest cost edge
- +Very fast pages and a clean, modern design
- +Custom domains available on low tiers
- +Straight swap — migration is mostly re-entering components
Trade-offs
- −Proprietary and hosted; no self-host path
- −Smaller company than Atlassian, which matters to some procurement teams
- −Fewer integrations than Statuspage
- −Still a second tool if you already run Uptime Kuma
Free tier with a usable feature set; paid plans are a flat monthly fee rather than per-subscriber. Checked 2026-08-01.