Openstatus Incident Management: Incident management for small teams

A responder can open an incident from a Slack slash command and label it critical, major or minor. Severity can be critical, major or minor. Each incident gets its own Slack channel, and that channel is archived when the incident closes. Status moves through open, mitigated, resolved or canceled, and the start time can be set to a past moment, so the record reflects when customer impact began. Once an incident is resolved, the team can draft a postmortem from the same record. An AI agent can also write the public status report, which waits for human approval before it goes live. The feature grew out of a workflow gap. Before it shipped, the two founders handled incidents in #general and found the Slack threads hard to follow. Openstatus already covered monitors and status pages, so the missing piece was the coordination layer between detection and customer messaging. Its comparison pages position it against incident.io, which lacks built-in uptime monitoring. Openstatus says Cal.com, WhiteBIT and Documenso use the product. For a small AI team, the appeal is fewer tools in the outage loop. Detection, status pages, Slack coordination and postmortems now sit in one open source project licensed under AGPL-3.0, and teams can self-host it. The MCP server lets assistants such as Claude or Cursor publish updates, which suits teams that already run agents in their workflow. Founders evaluating it should check the AGPL terms before modifying a hosted service, since that license reaches network use.