3 teams that moved to uptime kuma
3 teams moved to uptime kuma. Most left UptimeRobot (2) or AWS (1). The typical team cut 86% of its bill. Each team's old bill, running cost and net saving.
What they left for uptime kuma
Left UptimeRobot
2 teams · median $29/mo saved · cut 91% of the bill- 1Pieter Levels$50/mo
Uptime Canary on Uptime Kuma · Hetzner$55→ $5 a month · cut 91% · since Sep 2026Pieter Levels replaced UptimeRobot with Uptime Canary, an in-house app on Uptime Kuma.
- 2Mossroy$8/mo
Uptime Kuma, monitored in a swap with another self-hoster$8→ running cost not disclosed · since Jul 2026When UptimeRobot retired his discounted legacy Pro plan, Mossroy cancelled and set up Uptime Kuma, configured as code with AutoKuma, in a reciprocal arrangement where he and another self-hoster each monitor the other's services from outside.
Left AWS
1 team · $66/mo saved · cut 82% of the bill- 3Eduardo$66/mo
Self-hosted MySQL on a Hetzner VPS · Hetzner$80→ $15 a month · cut 82% · since May 2026Eduardo cut the AWS bill for a project from $80 to $0.50 by dropping Amazon RDS for a self-hosted MySQL instance, which costs $14 on Hetzner. The move took 2 to 3 days to set up, including certs, backups and data migration. The source gives no billing period.
Thank you for not renewing