Run incidents where your team already is.
Opsphie is incident management that lives in Slack. One command opens a channel with everything pinned at the top, and you walk away with a timeline and a postmortem draft.
OpsphieAPP
INC-42: Checkout returning 500s
- Severity
- P1 — High
- Status
- Identified
- Commander
- @ana
Summary
Payments fail after this morning's deploy. Rolling back.
Edit details in the web app
Declare
From “is something broken?” to a war room in seconds
Declare from wherever the alarm went off. Opsphie sets up the incident so the first few minutes go on the problem, not on admin.
/inc newfrom any channel, with a title or without- A dedicated channel, with the commander invited
- A control panel pinned at the top for severity, status, commander and summary
lee09:11
ana09:12
Respond
A timeline that writes itself
Every change is recorded as it happens, so nobody has to take notes mid-incident and the story is ready when you need it.
- Severity, status and commander changes, updates and summaries, captured automatically
- React with 📌 or use Add to timeline to keep any message
/inc postmortemdrafts a postmortem from the timeline
INC-42 · Timeline
- 09:12@ana declared the incident P2
- 09:15@ana changed severity from P2 to P1
- 09:21@lee: Errors started right after the 09:05 deploy
- 09:24@ana changed status from Investigating to Identified
- 09:31@ana posted an update: Rolling back the deploy.
- 09:48@ana changed status from Monitoring to Resolved
Communicate
Everyone stays in the loop
Stakeholders see what matters without joining the incident channel or asking for updates.
- New incidents, severity changes, resolutions and cancellations posted to an announcement channel you choose
- Anyone who joins the incident channel is tracked as a responder
- Test incidents (
/inc test) to rehearse: never announced, kept out of reports - A web dashboard with incident history and full timelines, with Sign in with Slack
OpsphieAPP09:12
OpsphieAPP09:15
OpsphieAPP09:48
Learn
See whether you're getting better
Reports in the web app show how many incidents you had, how severe they were and how long they took, for any date range.
- Incidents by severity, per day, week or month
- Time to resolve (median and p90) for each severity, and time to detect and mitigate wherever those times were recorded
- Time spent investigating, identified and monitoring
- The incidents behind the numbers, one click away; test and canceled incidents are left out
- Filter the incident list by severity, status, commander and date, and share the link
Reports · Last 90 days
Time to resolve (median)
1h 12m
p90 4h 30m
Time to detect (median)
9m
From 18 incidents of 26
Commands
One command to remember
Everything starts with /inc. In an incident channel, a bare /inc opens a menu of the actions for where the incident is at.
/inc new
Declare an incident
/inc sev P1
Change severity
/inc status
Move it along
/inc ic me
Take command
/inc update
Post an update
/inc summary
Keep the summary current
/inc resolve
Resolve it
/inc postmortem
Draft the postmortem
/inc test
Rehearse safely
/inc list
See what's in progress
On the roadmap
What we're building next
Planned, not shipped yet.
Linear
Remediations become Linear issues, with status kept in sync.
Automation
Rules like “a P0 pages the on-call channel and invites the team”.
Postmortems on the web
Edit and keep postmortems next to their incident.
Bring Opsphie to your workspace.
Add it to Slack, then start your first incident with /inc new.