Openstatus icon

Openstatus

Openstatus is an incident management platform that connects uptime monitoring, Slack-based response, status-page updates, timelines, and postmortem drafting. It is designed for teams that want to coordinate incidents and preserve an operational record from a web dashboard or Slack.

Openstatus

Incident management alongside monitoring and status pages

Openstatus is an open-source incident management platform for teams that already use uptime monitoring and a status page. It connects incident declaration, Slack coordination, internal timelines, customer-facing status reports, and postmortem drafting in one workspace.

Teams can declare an incident from Slack or the dashboard, assign a severity and commander, and run the response in a dedicated or linked Slack channel. Notes and status changes build a timestamped record, while public updates remain separately reviewable. Once the incident is resolved, the Slack Agent can prepare a Markdown postmortem from the recorded activity for editing and approval.

Key features

Incident declaration

Declare an incident from Slack or the dashboard with a title, severity, commander, and optional past start time. Monitor downtime rows can prefill the incident start time.

Slack-based coordination

Create a dedicated Slack channel for each incident, or link an existing channel. The channel includes a pinned incident card and displays the current severity and status.

Shared incident timeline

Promote messages to timeline notes from Slack, add notes with a command, and record status transitions such as mitigation, resolution, cancellation, and reopening with accompanying notes.

Status page updates

Keep internal incident handling separate from the customer-facing status report. Draft or update a linked report, review its wording, and publish public updates from the workflow.

Postmortem drafting

After resolution, generate a draft postmortem from the timeline, public updates, and channel history. Teams can edit it in Markdown, approve it, and close the incident.

Incident records

Capture timestamped incident activity and retain the incident history for operational review and audit-oriented records. The product documentation also describes audit logs on paid plans, though detailed plan availability is not specified here.

Practical use cases

  • Responding to monitor-detected outages

    When a monitor detects downtime, responders can declare an incident with the impact start time already populated, coordinate investigation in Slack, and record mitigation and resolution without reconstructing the sequence later.

  • Managing customer-facing service disruptions

    Teams can keep operational discussion, commanders, severity, and timeline notes in a private incident channel while preparing a separate status report for customers and subscribers.

  • Running incidents in an existing channel

    A team already working in a Slack channel can link that channel to the incident instead of moving the response into a new one; the unused incident channel is archived.

  • Creating incident reviews and records

    After service recovery, responders can use the recorded timeline, public updates, and channel history as the basis for a reviewable Markdown postmortem and follow-up documentation.

Pros and Cons

Pros

  • Combines monitoring context, incident response, status-page communication, and postmortem preparation in one workspace.
  • Supports both Slack and dashboard workflows, including dedicated or existing incident channels.
  • Separates internal incident activity from public status updates while linking the two records.
  • Builds a timestamped timeline from notes, status changes, and selected Slack messages.

Cons

  • The Slack Agent is not available on the free Hobby plan.
  • Incident management is described as rolling out workspace by workspace, so availability may vary.
  • Because the Slack Agent uses an LLM, its responses and actions require human review, particularly before publishing or resolving incidents.

FAQ

Is there a free plan or trial?

Openstatus provides a free Hobby plan with one monitor and one status page with three components. Paid plans include the Slack Agent; the site also offers a 14-day Starter trial without a credit card.

How do teams set up the Slack Agent?

Install the Slack integration from Settings > Integrations, authorize the correct Slack workspace, then invite the bot to a channel or use /openstatus subscribe with a status-page URL. The setup guide lists a paid openstatus account and permission to install Slack apps as prerequisites.

Can an incident be run in an existing Slack channel?

Yes. Users can declare an incident from the dashboard or Slack, approve the declaration, and receive a dedicated incident channel. A team can instead link an existing channel, after which the newly created incident channel is archived.

What does the incident record contain?

Incident notes, status changes, public status reports, and channel history can feed the incident record. After resolution, the agent drafts a postmortem for review and approval; it does not publish changes without user confirmation in the documented workflow.

What should teams know about the Slack Agent's limitations?

The Slack Agent is AI-powered and may occasionally interpret messages incorrectly or produce incomplete or unexpected results. The documentation advises reviewing its output, especially before publishing updates, resolving incidents, or scheduling maintenance.

Quick Facts

Category
Incident management
Primary platform
Web dashboard with Slack Agent
Core workflow
Declare, coordinate, update, resolve, and document incidents
Related tools
Uptime monitoring and status pages
Pricing availability
Free Hobby plan; paid plans and a 14-day Starter trial are available
Source domain
openstatus.dev