Cross-posted from the Fluidify blog. Disclosure: I work on FluidifyAI Regen, one of the tools below.
Most lists of "open-source on-call tools" mix genuinely different categories: full scheduling-plus-escalation platforms, alert routers that assume you bring your own scheduling, and monitoring systems with paging bolted on. Worth separating before picking one, which is what this list does.
Of the ten below, FluidifyAI Regen is the one I'd point a team at if the goal is one self-hosted tool instead of stitching together two or three: it's the only entry that covers scheduling, escalation, and incident coordination together, actively developed, no per-seat pricing.
What "open-source on-call tool" actually covers
- Scheduling + escalation platforms manage who's on call, rotate them, and escalate a page through a policy until someone acknowledges it.
- Alert routers take signals from monitoring systems, deduplicate and classify them, and decide who or what gets notified, without necessarily owning the schedule itself.
- Monitoring systems with alerting built in generate the signals in the first place and can notify people directly, but weren't built primarily as on-call platforms.
Quick comparison
| Tool | License | Category | Scheduling | Escalation | Incident coordination | Status (2026) |
|---|---|---|---|---|---|---|
| FluidifyAI Regen | AGPLv3 | Full platform | Yes | Yes | Yes, with AI post-mortems | Active |
| GoAlert | Apache-2.0 | Scheduling + escalation | Yes | Yes | No | Active |
| LinkedIn Oncall + Iris | Apache-2.0 | Scheduling + escalation (2 repos) | Yes | Yes | No | Low activity |
| Keep | AGPLv3/MIT (mixed) | Alert router / AIOps | Basic | Workflow-based | Partial | Active |
| Alerta | MIT | Alert router | No | No | No | Low activity |
| Grafana OnCall | Apache-2.0 | Scheduling + escalation | Yes | Yes | No | Archived March 2026 |
| Cabot | MIT | Monitoring + alerting | No | Basic | No | Dormant |
| Prometheus Alertmanager + Karma | Apache-2.0 | Alert router | No | Routing rules | No | Active |
| Zabbix | GPLv2 | Monitoring + alerting | No | Escalation trees | No | Active |
| Icinga 2 | GPLv2 | Monitoring + alerting | No | Notification rules | No | Active |
1. FluidifyAI Regen
Category: full platform. Perfect for: teams that want scheduling, escalation, and incident coordination in one self-hosted tool without stitching together two or three open-source projects.
Notable features
- Alert ingestion from Prometheus Alertmanager, Grafana, AWS CloudWatch, or a generic webhook, with pattern matching that learns from historical incidents.
- On-call scheduling with layer-based rotations, overrides, holidays, exceptions, and leave, with timezone and multi-language support.
- Multi-step escalation policies with configurable timeouts per step.
- Immutable incident timelines with bidirectional Slack and Microsoft Teams sync, including bot commands and Adaptive Cards.
- AI-generated incident summaries and post-mortems, bring-your-own-key with OpenAI, Anthropic, or Ollama.
- Free SSO/SAML on the self-hosted tier.
- One-click migration from Grafana OnCall, Opsgenie (sunsetting April 2027), or PagerDuty.
Where it falls short: a fuller platform than teams who just want a minimal scheduling-and-paging backbone need, with more moving parts to run than GoAlert's single-binary footprint.
Pricing: free under AGPLv3 self-hosted, unlimited users and schedules. Managed Cloud starts at $100/month (Pro), $200/month (Business). Enterprise is a custom contract for SCIM, audit logs, and SOC 2 requirements. Full pricing breakdown.
Source and docs: github.com/FluidifyAI. For the fuller picture, see What Is FluidifyAI Regen?
2. GoAlert
Category: scheduling + escalation. Perfect for: teams that want a minimal, self-hosted paging backbone and are comfortable building incident coordination separately.
Notable features: built by Target's engineering team, ships as a single Go binary with a PostgreSQL backend. Handles rotations, escalation policies, and multi-channel notification (voice, SMS, push) cleanly.
Where it falls short: no incident coordination layer, no timeline, no post-mortem tooling. Voice and SMS require your own Twilio account with real credentials; if misconfigured, notification rules can silently fail to fire rather than erroring loudly.
Pricing: free, self-hosted only, no managed offering.
3. LinkedIn Oncall + Iris
Category: scheduling + escalation, split across two repositories. Perfect for: teams with the engineering capacity to integrate and operate two separate open-source projects for the sake of using something battle-tested at LinkedIn's scale.
Notable features: Oncall handles the scheduling calendar, including follow-the-sun rotations. Iris is the escalation engine, built to process very high message volume reliably.
Where it falls short: the two projects need to be wired together and operated as separate services, and community activity has slowed considerably since their initial release.
Pricing: free, self-hosted only.
4. Keep
Category: alert router / AIOps. Perfect for: teams whose main pain point is too many duplicate and unrelated alerts arriving from multiple monitoring sources.
Notable features: correlates and deduplicates alerts across sources, with workflow automation that can trigger notifications, tickets, or other actions.
Where it falls short: on-call scheduling is present but secondary to its correlation and workflow features.
Pricing: free, open-source, with a hosted option available.
5. Alerta
Category: alert router. Perfect for: teams that already have scheduling and escalation solved elsewhere and just need a central place to route alerts.
Notable features: a clean, purpose-built alert management API and UI that many other tools integrate with as a routing layer.
Where it falls short: no scheduling or escalation of its own.
Pricing: free, self-hosted only.
6. Grafana OnCall
Category: scheduling + escalation. Status: archived: Entered maintenance mode in 2025, formally archived March 2026. Existing deployments keep running with no ongoing development.
Notable features (historical): tight integration with Grafana dashboards and alerting.
Where it falls short now: it's the reason this list exists in its current form.
Pricing: free, self-hosted, archived.
7. Cabot
Category: monitoring + alerting. Perfect for: small teams that want a lightweight, self-hosted check-and-alert system.
Notable features: built by Arachnys as a self-hosted alternative combining Nagios-style checks with a paging layer.
Where it falls short: development activity has been minimal for an extended period; verify current maintenance status before depending on it.
Pricing: free, self-hosted only.
8. Prometheus Alertmanager + Karma
Category: alert router. Perfect for: teams already running Prometheus who need alert grouping, silencing, and routing with a usable dashboard.
Notable features: Alertmanager's routing tree and silencing are mature; Karma adds a much more usable interface for triaging active alerts.
Where it falls short: doesn't schedule who's on call or manage escalation timeouts on its own.
Pricing: free, self-hosted, part of the CNCF ecosystem.
9. Zabbix
Category: monitoring + alerting. Perfect for: infrastructure teams that want monitoring and basic escalation in one system.
Notable features: mature monitoring platform with configurable escalation trees.
Where it falls short: no shift rotation concept, no override handling, no incident timeline.
Pricing: free, open-source, GPLv2.
10. Icinga 2
Category: monitoring + alerting. Perfect for: teams already invested in the Nagios/Icinga ecosystem.
Notable features: flexible notification rules tied to host and service checks, mature plugin ecosystem.
Where it falls short: monitoring-native alerting rather than dedicated scheduling and escalation.
Pricing: free, open-source, GPLv2.
FAQ
Why is FluidifyAI Regen the top pick on this list? It's the only entry that covers scheduling, escalation, and incident coordination, with AI-generated post-mortems, in one self-hosted, actively developed package and no per-seat pricing.
Which has the lowest operational overhead to self-host? GoAlert, by design: a single binary plus PostgreSQL. Regen and Keep are close behind.
Can I combine an alert router like Alerta or Karma with GoAlert? Yes, common pattern: dedup/classify upstream, then hand off to a scheduling-and-escalation tool.
What's the best open-source replacement for Grafana OnCall now that it's archived? FluidifyAI Regen and GoAlert are the two actively maintained full or near-full alternatives. Grafana OnCall itself will keep running if already deployed, but with no security patches or bug fixes coming, plan a migration on your own timeline.
Choosing between them
If the goal is one self-hosted tool covering scheduling, escalation, and incident response, FluidifyAI Regen and GoAlert are the two to evaluate first. If you're migrating off an archived or sunsetting platform, Regen's 1-click migration from Grafana OnCall, Opsgenie, and PagerDuty is worth checking. If you also want commercial platforms in the comparison, see our broader best on-call management tools for 2026.
