Openstatus Incident Management is an open-source incident response and status page platform that enables teams to declare incidents, coordinate in Slack, publish public updates, and generate postmortems using AI agents.
What the product does and how it is positioned
Openstatus Incident Management provides an end-to-end incident response workflow integrated with Slack, AI agents, and public status pages.
Responders can declare incidents, launch dedicated response channels, draft status updates with agent assistance, and generate blameless postmortems directly from channel history.
Source-supported ways to use the product
Teams can run the entire incident lifecycle directly in Slack, from declaring incidents and opening incident channels to publishing status reports and mitigating issues.
The company presents this as a customer use case for maintaining timestamped incident records and exportable audit logs to support SOC 2, ISO 27001, NIS2, and DORA standards.
The documented workflow, where available
Global uptime monitors detect service degradation and dispatch failure alerts with diagnostic details to Slack, PagerDuty, email, or webhooks.
A team member declares an incident with a title and severity using a Slack slash command, which creates a dedicated channel and pins the incident card.
The openstatus AI agent drafts an external status message in the incident thread, which a responder reviews and approves to notify subscribers.
Responders issue a slash command to mark the incident mitigated, automatically moving the linked public status report to monitoring status.
Once resolved, the agent compiles a draft postmortem containing a summary, impact duration, timeline, root cause, and action items for final approval.
Openstatus integrates AI agent workflows directly into operational response channels. Rather than requiring responders to navigate a separate web interface during critical events, the platform enables engineers to interact with the assistant inside Slack threads or through AI environments like Claude, ChatGPT, and Cursor via Model Context Protocol (MCP).
During an incident, the agent translates informal technical updates into public status announcements that can be reviewed and approved before broadcasting to subscribers. Following resolution, the agent aggregates timestamps, status transitions, and discussion history to produce a structured postmortem draft containing timelines, root causes, and follow-up action items.
Checks to run with your own material and workflow
What was checked and when
Answers based on the source-checked product record
Openstatus can be managed through Slack slash commands, an AI agent via Model Context Protocol (MCP), a web dashboard, a CLI, a typed API with a Node SDK, and Terraform.
Openstatus maintains timestamped incident updates and logs all mutations, actors, and event sources in an exportable audit log to satisfy external communication criteria like SOC 2 CC2.3.
Openstatus can be self-hosted using Docker. Users can run the full stack, host the status page separately, or operate private monitoring locations behind a firewall.
The AI agent drafts external status announcements from channel input during active incidents and compiles blameless postmortem summaries from chat timelines once resolved.
Openstatus supports alerting and update distribution across Slack, PagerDuty, email, RSS feeds, and webhooks.
