opensourceprojects.dev

A broadsheet for software that doesn't ask for your email

Open source uptime monitoring that runs 1,600+ servers in production
GitHub RepoViews19

Project Description

View on GitHub

You Need to Know When Your Servers Go Down. Checkmate Is an Open Source Way to Do That.

You've got servers. Maybe a handful, maybe a lot. Either way, you want to know when one of them stops responding before your users do. You could wire together a pile of scripts and a cron job, or you could reach for a hosted service and hand over a credit card. Checkmate is a third option: an open-source, self-hosted monitoring tool that tracks uptime, response times, and incidents in real time.

What It Does

Checkmate is an uptime and infrastructure monitoring application. It regularly checks whether a server or website is accessible and performing as expected, then gives you real-time alerts and reports on availability, downtime, and response time. The repository contains both the frontend and the backend, so it's a complete application rather than a piece of a larger puzzle.

There's also a companion agent called Capture, which pulls data from remote servers to give you more detail on CPU, RAM, disk, and temperature. Capture isn't required to run Checkmate—it's an optional add-on for deeper hardware insight. It runs on Linux, Windows, Mac, Raspberry Pi, or really anything that can run Go. The main app is self-hosted, and the README points to a one-click deployment option through PikaPods if you'd rather not set it up by hand.

Why It's Cool

  • It's been tested at a scale most side projects never see. The README states Checkmate runs in production monitoring 1,600+ servers on a single deployment, with no reported performance bottlenecks or significant operational issues. That's a concrete number, and it's the kind of thing you want to hear before you trust a tool with your infrastructure.

  • It scales horizontally when you need it to. If 1,600 servers isn't enough, you can run dedicated worker nodes that share the check load through MongoDB. That's a real architecture decision, not a marketing bullet—it means the check workload can be distributed rather than pinned to one process.

  • The optional agent is a smart split. Core uptime checking works out of the box. If you want hardware telemetry—CPU, RAM, disk, temperature—you deploy Capture on the machines you care about. You're not forced to install an agent everywhere just to get basic monitoring, which keeps the barrier to entry low.

  • Self-hosted means your monitoring data stays yours. You run it, you own it. For teams that can't or won't send infrastructure data to a third party, that matters.

  • The project is genuinely international. The README ships with translations in Arabic, Catalan, Czech, German, Spanish, Finnish, French, Italian, Japanese, Portuguese, Russian, Thai, Turkish, Ukrainian, Vietnamese, and both Simplified and Traditional Chinese. That's a lot of languages for a monitoring tool, and it suggests a broad contributor base.

How to Try It

The fastest path is the PikaPods button in the README, which spins up a hosted instance for you. If you'd rather self-host (which is the whole point), head to the repository and follow the installation section of the docs.

  1. Go to the repo: github.com/bluewave-labs/checkmate
  2. Read the installation guide in the README and the linked user's guide.
  3. Deploy the app—either via PikaPods or your own self-hosted setup.
  4. Optionally, deploy Capture on the servers you want hardware metrics from.
  5. Point Checkmate at the services you want to monitor and let it start checking.

If you're planning to run at serious scale, the docs cover distributed workers, which is where the MongoDB-backed horizontal scaling comes in.

Final Thoughts

Checkmate is aimed at people who want real monitoring without renting it. If you're running a modest fleet and want something you can stand up and own, it's a reasonable fit. If you're running something much larger, the fact that it's documented at 1,600+ servers on one deployment—with a path to scale further—is the detail worth paying attention to. It's a mature-enough project with a clear job, and the optional agent split means you can start small and add depth later. Worth a look if self-hosted monitoring has been on your list.


Follow @githubprojects for more developer tools and open source projects.

Back to Projects
Project ID: checkmateLast updated: November 17, 2026 at 06:53 AM