Self-hosted Pingdom alternative: monitoring you own with Checkmate

Knowing whether your site is up sounds like a solved problem, right until you read the pricing page. Pingdom and UptimeRobot both meter the thing you actually want: how many endpoints you can watch, how often they get checked, how many places the checks run from, and whether you can put your logo on a status page. Monitoring is a utility — it should just run — but the hosted versions quietly turn it into a per-monitor subscription that grows every time your stack does. Checkmate is the version you own: one self-hosted dashboard watching your sites, services and servers, with no meter on the checks.

What Checkmate is

Checkmate is an open-source, self-hosted monitoring platform from Bluewave Labs. It isn't a stripped-down status widget — it's a full monitoring stack: uptime checks across multiple protocols, response-time history, real server-level metrics, alerting through the channels your team already uses, and public status pages. You run it, so the number of monitors, the check frequency, and the retention are yours to decide rather than yours to pay for. It's licensed AGPL-3.0, so the code is yours to read, fork and audit, and it doesn't phone home — the only place your checks and metrics land is the box you put them on.

The contrast with the SaaS tools is the whole point. Pingdom bills by check volume and frequency and reserves infrastructure metrics and branded status pages for higher tiers. UptimeRobot's free plan throttles your check interval and caps your monitors, and the good features live behind the paid wall. Checkmate hands you the equivalent feature set to run on a small box, with the monitor count limited only by the resources you give it.

The features that actually matter

• Uptime monitoring across protocols. HTTP/HTTPS, TCP port, ping, and SSL-certificate checks, each on an interval you choose. There's no "1-minute checks cost extra" — the frequency is a setting, not a line item.
• Response-time history. Every check records latency, and the dashboard charts it over time, so you see a site degrading before it falls over rather than only learning it went down.
• Incident history. Each outage is logged with when it started and how long it ran, so you get a record you can look back over instead of a red light that clears the moment the outage does.
• Infrastructure monitoring with the Capture agent. A lightweight agent installed on each server reports CPU, memory, disk and temperature back to the dashboard. Neither competitor gives you host-level metrics without pushing you toward a separate, pricier product.
• Docker container monitoring. Watch container health alongside the hosts they run on, in the same dashboard.
• Alerts through the channels you use. Notifications go out over email, Slack, Discord, Telegram, and webhooks — the multi-channel alerting the SaaS tools tend to reserve for paid tiers.
• Public status pages. Branded pages so customers can check for themselves during an incident instead of flooding your inbox. This is a paid add-on on both Pingdom and UptimeRobot.
• Page speed monitoring. Performance checks so front-end regressions show up on the same board as availability.
• Maintenance windows. Pause checks during planned work so a deploy doesn't page the whole team with false alarms, and your uptime numbers don't take the hit for work you scheduled.

Why self-host it instead of the hosted version

Your monitoring data stays yours. Uptime history, response times, and server metrics are a quiet map of your infrastructure — where it lives, how it's shaped, when it's weak. Self-hosting keeps that map on a box you control instead of on a vendor's analytics platform.

The cost doesn't scale with your stack. Hosted monitoring charges per monitor, per check frequency, per status page. Add a service, add a bill. Checkmate's price is the small server it runs on, whether you watch ten endpoints or two hundred, at one-minute intervals or five.

Control and branding are yours. Status pages carry your name, not a "powered by" footer. Retention is set by your disk, not a plan. And because it's open source, nothing you rely on can be moved behind a new paywall in next quarter's pricing update.

Who it's for

Agencies and freelancers juggling a dozen client sites, who need branded status pages and don't want a per-monitor bill that eats the margin on every retainer.

Homelabbers and self-hosters already running a rack of services who want one dashboard for uptime and host health — CPU, disk, temperature — without paying a cloud vendor to watch a machine sitting in their own closet.

Small SaaS and ops teams who need real alerting into Slack or a PagerDuty-style webhook and server metrics next to their availability checks, but aren't ready to stand up a full Prometheus-and-Grafana operation to get it.

The honest setup notes

Rolling this out yourself is real work, and we'd rather say so. Checkmate is a MERN-stack app: it needs MongoDB running alongside it in the same Docker Compose stack, and that datastore is yours to back up — your uptime history and metrics live in Mongo, and a box that dies without a backup takes the history with it. Email alerts need working SMTP, which means credentials, a sending domain, and the usual deliverability care so your outage notices don't land in spam. Server metrics need the Capture agent installed on each host you want to watch, and kept in step with the main app. And like anything you self-host, updates are on you — new releases arrive on the project's cadence, not automatically.

None of it is exotic, but it is a standing chore, and monitoring that itself needs babysitting somewhat defeats the purpose. Or let us run it.

Deploy it in one click

Doing it by hand means a compose file, a MongoDB instance, an SMTP configuration, a reverse proxy with TLS, and a plan for backups and upgrades before you monitor a single URL. That's an afternoon, and then it's a thing you maintain forever.

On Caliber Node it's one click. We stand up Checkmate with its database, terminate TLS, wire in mail so alerts actually send, and handle the backups and updates underneath — the database is snapshotted on a schedule, the certificate renews itself, and a new Checkmate release is ours to roll out rather than a maintenance window on your calendar. You get the dashboard and a login; we keep the plumbing healthy. When you're ready, deploy Checkmate in one click and start adding monitors instead of building infrastructure.

First run

1. Open your Checkmate dashboard and create the admin account — this is your instance, so the first user is you.
2. Add your first uptime monitor: paste a URL, pick HTTP/HTTPS, and set the check interval.
3. Save it and watch the first checks land — within a minute you'll have a live status and a response-time reading.
4. Connect a notification channel — email, Slack, Discord, or a webhook — so the next time that monitor goes red, you hear about it.
5. Install the Capture agent on one server to pull CPU, memory and disk into the same board, and you've gone from a single URL check to real infrastructure visibility.

The bigger picture

Knowing your systems are healthy shouldn't be something you rent back one monitor at a time. Availability, latency, and host metrics are the most basic feedback loop you have on the things you've built — and that loop belongs on hardware you control, reporting to a dashboard nobody can reprice. Self-hosting Checkmate turns monitoring back into infrastructure you own rather than a subscription that grows with your success.

Deploy Checkmate in a few minutes →

Or browse the full app catalog to see what else you can own instead of rent.

One-click self-hosted apps, managed for you — real logs, SFTP, and your data always exportable. Never a black box.