Gatus vs 
Uptime Kuma
Compared on data, not vibes. Metrics refresh nightly; verdict links carry the math.
| Gatus | Uptime Kuma | |
|---|---|---|
| GitHub stars | 11,772 | 90,062 |
| Last commit | 2d ago | 0d ago |
| Latest release | v5.36.0 | 2.5.0 |
| Docker pulls | — | — |
| License | Apache-2.0 | MIT |
| Min RAM | 512 MB | 512 MB |
| Containers | 1 | 1 |
| 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
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.