Best / Incident management
Best open-source Incident management
The best self-hosted incident split in the c17.io catalog is Keep for MIT alert routing (the published PagerDuty / Opsgenie / incident.io / FireHydrant / Rootly stack; skip ee/ if that directory exists), Checkcle when the job is MIT Go HTTP uptime rather than an incident desk, Grafana when the job is AGPL dashboards rather than a pager, and Uptime Kuma when the job is MIT HTTP/TCP checks. Grafana OnCall OSS was archived 24 Mar 2026 — not the path. This is not PagerDuty's every AIOps SKU.
Open the stackStart on Railway
Ranked picks
1
KeepMIT AIOps and alert management — the c17 PagerDuty / incident.io path. Skip ee/. Grafana OnCall OSS is archived.
When to pick it: Routing, incidents, and a webhook you host.
12,437 stars in the catalog
2
checkcleMIT Go uptime already on /replace/pingdom. Not an on-call desk.
When to pick it: HTTP checks plus a public page.
3,305 stars in the catalog
3
GrafanaAGPL Grafana OSS already on /replace/datadog. Not a pager.
When to pick it: Graphs you read, not a night-time rotation.
4
Uptime KumaMIT HTTP/TCP uptime already on /best/status-pages. Not incident command.
When to pick it: A URL check, not a war room.
92,564 stars in the catalog
How they compare
| Tool | License | Self-host | Best for |
|---|---|---|---|
| Keep | MIT License | Medium | Routing, incidents, and a webhook you host. |
| checkcle | MIT License | Easy | HTTP checks plus a public page. |
| Grafana | Not listed | Medium | Graphs you read, not a night-time rotation. |
| Uptime Kuma | MIT License | Easy | A URL check, not a war room. |
Related pages
- Keep stack
- Checkcle uptime stack
- Grafana OSS + Prometheus stack
- Replace PagerDuty
- Replace Opsgenie
- Replace incident.io
- Replace FireHydrant
- Replace Rootly
- Replace Pingdom
- Replace Statuspage
- Replace UptimeRobot
- Replace StatusCake
- Replace Better Uptime
- Replace Datadog
- Replace Grafana Cloud
- All best open-source pages
- All compare pages
- All replace pages
- All stacks
- Tools catalog
FAQ
- Keep or Grafana OnCall?
- Keep. Grafana archived OnCall OSS on 24 Mar 2026. Do not install that repo as a new path.
- incident.io, FireHydrant, or Rootly?
- Same published alert desk — /replace/incident-io, /replace/firehydrant, and /replace/rootly.
- Is this Pingdom?
- HTTP uptime stays on /replace/pingdom (Checkcle). This page is on-call routing.
- Are these free?
- Keep community is MIT (skip ee/). Checkcle and Uptime Kuma are MIT. Grafana OSS is AGPL-3.0. You pay hosting. Template users never pay c17.
- How do I deploy it?
- Open /stacks/keep-oncall. Persist Postgres. Connect one alert source. Create one test incident.
Stack of the Week
Get one stack a week that replaces a SaaS bill.