Important: monitors vs on-call management
Uptime Kuma, Gatus, and Nagios detect failures and send notifications, but they do not provide on-call rotations and escalation policies. Keep centralizes and routes alerts from other tools. OneUptime, Wachd, and Uptimepage add on-call scheduling and incident management, and Operational notifies you about product events rather than infrastructure incidents.
What replaces which part of Opsgenie
For alert aggregation and routing, use Keep or Wachd, which receive alerts from Grafana, Datadog, and Prometheus. For on-call schedules and escalation, look at OneUptime, Wachd, or Uptimepage. For basic monitoring and notifications, Uptime Kuma, Gatus, and Nagios are enough, and many teams combine them with a dedicated on-call tool.
License details
Uptime Kuma and Keep's core are MIT, with Keep's ee directory under a separate license. Gatus and Wachd are Apache-2.0, OneUptime is Apache-2.0 with an enterprise directory, and Nagios Core is GPL-2.0. Operational and Uptimepage are AGPL-3.0.
Self-hosting
All eight can be self-hosted: Uptime Kuma and Gatus run as a single container or binary, Wachd needs Kubernetes, and Keep and OneUptime are heavier platforms. Operational and Uptimepage also offer hosted services.
Maintenance status
Uptime Kuma, Keep, Gatus, OneUptime, Nagios, Operational, Wachd, and Uptimepage were all updated within days or weeks of this update. Wachd and Uptimepage are very small and new projects.