Gatus vs 
Kener
Compared on data, not vibes. Metrics refresh nightly; verdict links carry the math.
| Gatus | Kener | |
|---|---|---|
| GitHub stars | 11,772 | 5,097 |
| Last commit | 2d ago | 8d ago |
| Latest release | v5.36.0 | v4.1.2 |
| Docker pulls | — | — |
| License | Apache-2.0 | MIT |
| Min RAM | 512 MB | 1,024 MB |
| Containers | 1 | 2 |
| ARM (Pi-friendly) | yes | yes |
Gatus
A public status page whose entire configuration is one YAML file you own: the checks, the pass conditions and the alerting, declared once and served as a page.
Backs these verdicts
Kener
A public status page with the incidents, the maintenance windows and the monitors behind it, all managed in a browser rather than a config file.
Backs these verdicts
Neither page tells you which is "better" — they solve the same jobs differently. Pick by the constraint that binds you: RAM, ARM, license, or how alive the project looks.