Checkmate
Checkmate is an open-source, self-hosted infrastructure monitoring tool for self-hosters that tracks servers, websites, Docker containers, hardware, uptime,…
Platform availability
Available on 2 of 10 platforms
- Unraid (not listed)
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox
- Helm (not listed)
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
- Any server
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
65/100 Good
- Maintained
- 100last commit 4 days ago
- Popular
- 8111,061 GitHub stars
- Easy to install
- 352 install platforms, install notes
- Light to run
- No data
- Security check
- 54 serious findings, 24 minor, CI, tests
Based on 4 of 5 factors.
Security check: 4 serious findings
- A private key is committed in the source code (server/src/utils/pem.ts:18)
- Uses handlebars 4.7.9, which has a known critical vulnerability (npm)
- Uses handlebars 4.7.9, which has a known critical vulnerability (npm)
- Uses maplibre-gl 5.19.0, which has a known critical vulnerability (npm)
Automated checks on commit 08e9ad6, 15 Oct 2026. Not an audit.
Availability: platform listings confirmed today, links checked today
- GitHub stars
- 11,061
- Open issues
- 110
- Last commit
- 2026-11-17
- Latest release
- v4.0.0
- License
- AGPL-3.0
- Activity
- steady
Checked 4 days ago - source: GitHub (bluewave-labs/Checkmate)
Resources & Compatibility
Requirements not published yet.
First-install notes
- Start Checkmate from the docker/dev folder Open the Checkmate folder, run `cd docker/dev`, then run `docker-compose up -d`. This starts the app’s containers; starting from the wrong folder can leave it unable to find its configuration files. source
- Add a custom CA if your network uses it If your home network uses its own certificate authority (CA), put the certificate in `docker/dev/certs/custom-ca.pem` and start Checkmate with the custom CA example override. Without this, Checkmate may fail to trust some internal or self-signed services. source
- Set Docker host to the local socket Use `unix:///var/run/docker.sock` when telling Checkmate where to find Docker on the machine. If this points to the wrong place, Checkmate may not be able to see or monitor Docker containers. source
Fetched 53 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
Do I need to run MongoDB separately for Checkmate?
Yes, Checkmate requires MongoDB and the reference Docker Compose file starts a MongoDB service for you. If you use an external MongoDB instance, set DB_CONNECTION_STRING to it.
Which origin should I tell Checkmate about if I access it by domain or LAN IP?
The reference setup is normally reached on port 52345 from the local machine. If the app is accessed from another domain or LAN IP, set CLIENT_HOST to that origin.
How can Checkmate monitor remote server hardware like CPU, RAM, disk, and temperature?
Run the optional Capture agent on the remote server to collect those hardware metrics. Capture is not required for Checkmate, but it adds the extra insight.
Why might Checkmate not see Docker containers on the same host?
Checkmate needs the correct Docker host setting so it can reach the local Docker socket. If that setting points to the wrong location, it may not be able to monitor containers.
How do I make Checkmate trust internal or self-signed services?
Place your custom CA certificate in docker/dev/certs/custom-ca.pem and start Checkmate with the custom CA override. Without this, some internal or self-signed monitored services may fail trust checks.
From which directory should I start Checkmate with Docker Compose?
Start Checkmate from the docker/dev folder with docker compose up -d. Starting it from the wrong folder can prevent Checkmate from finding its configuration files.
Answers sourced from github.com, github.com, github.com, github.com
Community
Collected 48 days ago - public community threads