Callu review
A measurable, open-source incident lifecycle for teams running their own infrastructure.
Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026
Callu is an open-source, self-hosted, single-tenant incident management and on-call platform for organizations that want incident data on their own infrastructure. It supports the full incident lifecycle, from webhook-based alert ingestion through guarded state transitions, append-only timelines, escalation, stakeholder updates, postmortems, reporting, and runbooks. On-call teams can manage timezone-aware schedules, rotation overrides, and ordered escalation policies targeting users, schedules, or teams. Callu is best suited to self-hosters that need measurable incident operations without per-seat pricing.
Its operational scope is broad for an open-source product. Alerts can arrive through webhooks and JSONPath templates, while notification delivery includes email, SMS, voice calls, in-app push, Slack, Microsoft Teams, custom webhooks, and shared email. Prometheus Alertmanager, Grafana Alerting, Voximplant, Asterisk, and generic JSON webhooks are among the listed integrations. Public status pages add components, incident updates, uptime history, and subscribers. Structured postmortems include action items and workflow states, and reporting covers MTTA, MTTR, uptime, and team-performance metrics. Teams that value measurable follow-through will find the combination of timelines, metrics, postmortems, and Markdown runbooks particularly relevant.
The main trade-off is operational ownership. Callu is deployed with Docker Compose and uses PostgreSQL, with optional Redis and RabbitMQ, so it fits organizations prepared to run and maintain their own incident platform. Its integration breadth is narrower than its lifecycle coverage, and Slack and Microsoft Teams are positioned as notification channels rather than documented ChatOps action surfaces. Choose Callu when infrastructure control, open-source licensing, single-tenancy, and incident measurement matter most. Choose an alternative when you need a managed service, a wider ecosystem, or deeply documented in-channel incident actions.
Callu pros and cons
- Where it wins
- Covers schedules, escalations, alerts, postmortems, metrics, and runbooks
- Supports email, SMS, voice-call, push, Slack, and Teams notifications
- Includes status pages with components, updates, uptime history, and subscribers
- Where it doesn't
- Requires self-hosted deployment with Docker Compose and PostgreSQL
- Its integration set centers on webhooks, monitoring, and messaging tools
- Slack and Teams are documented as notification channels, not incident-action surfaces
Callu fact sheet, pricing and score →
Advertiser disclosure: iTechGuides is reader-supported. Vendors can pay for top positions in our rankings and for a place on other products' pages, and we may earn a commission when you click some links. Bought places stand at the number bought; this page and our disclosure say so. Paying vendors may get a fuller, more detailed review from our editors, and that review can change their score. How we rank.
Last updated · How we research and update