Kener vs 
Uptime Kuma
Compared on data, not vibes. Metrics refresh nightly; verdict links carry the math.
| Kener | Uptime Kuma | |
|---|---|---|
| GitHub stars | 5,097 | 90,062 |
| Last commit | 8d ago | 0d ago |
| Latest release | v4.1.2 | 2.5.0 |
| Docker pulls | — | — |
| License | MIT | MIT |
| Min RAM | 1,024 MB | 512 MB |
| Containers | 2 | 1 |
| ARM (Pi-friendly) | yes | yes |
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
Uptime Kuma
Uptime monitoring and status pages from one container, with no monitor quota and no per-check billing.
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.