checkmatevsScrutiny
Two self-hosted Monitoring & observability projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| checkmate | Scrutiny | |
|---|---|---|
| Score | 73/100 | 69/100 |
| Rank in category | #14 of 105 in Monitoring & observability | #22 of 105 in Monitoring & observability |
| GitHub stars | 11 114 | 8 464 |
| Stars, last 30 days | +154 | +120 |
| Stable releases, 12 months | 17 | 12 |
| Latest release | v4.1.0 · 19 Nov 2026 | v0.10.0 · 1 Nov 2026 |
| Setup | Easy | Moderate |
| Official Docker image | Yes | Yes |
| License | AGPL-3.0 | MIT |
| Main language | Typescript | Go |
Which one should you pick?
checkmate scores 73/100 against 69/100 for Scrutiny, so it is the safer default.
checkmate ships more often: 17 stable releases in the past year, against 12 for Scrutiny.
If you want the quickest setup, checkmate is easier to run; Scrutiny needs more configuration.
Key differences
- License: checkmate is AGPL-3.0, Scrutiny is MIT.
- Language: checkmate is written mainly in Typescript, Scrutiny in Go.
- Platforms only checkmate lists: Kubernetes.
- Platforms only Scrutiny lists: Build from Source, Docker, Podman.
- Features only checkmate lists: Distributed worker scaling, Incident Tracking, Infrastructure Monitoring, JSON query monitoring and 8 more.
- Features only Scrutiny lists: Alerting / notifications, Automatic drive detection, Historical S.M.A.R.T trend tracking, Hub/spoke distributed collection and 7 more.
- Both offer: REST API.
checkmate details →Scrutiny details →All Monitoring & observability projects →
Swap a project
Keep checkmate, compare it with
Keep Scrutiny, compare it with