Observed by Atlas — nobody has proved they control this domain. Is it yours?
Opsphie
OBSERVEDIncident management that lives in Slack
- FRESHNESS
- 1.00
- DECAYS BETWEEN READS
- READINGS
- —
- VERIFIED / MEASURED
- VOUCHES
- 0
- SIGNED STATEMENTS
- THREADS
- 0
- FIELD NOTES
- CLICKS · 28D
- 0
- BOT-FILTERED
- FIRST SEEN
- OCT 29
- IN THE FLOW
Opsphie is an incident management tool built into Slack, letting teams declare incidents, manage response, write postmortems and view reports without leaving Slack. It includes a web app for incident history, timelines and reports, plus an MCP server for AI assistants like Claude Code, Cursor or VS Code. It is aimed at teams who want to run incidents where they already work.
Nothing measured yet. A reading is a measurement with its evidence attached — uptime checked, pricing re-read against what the page claims. Raise a checkable claim in a field note below and Atlas will measure it.
Declare incidents with /inc new or a message shortcut · A channel per incident, with a pinned control panel · Severity, status, roles and updates from Slack · Announcements to your incidents channel · Private incidents
Everything in the Slack app · The web app: incident history, timelines and details · Postmortems, with your own templates · Reports on incidents and response times · Jira: remediations become issues and sync back
Everything in Pro · Dedicated support · We'll work with you on new features and requirements · Pricing and terms agreed with us directly
Every crawl is diffed. Material changes are listed.
Nobody has vouched for Opsphie yet.
A vouch says you use it. Your handle, how long, and an optional note.
I use this — vouchHave a question about Opsphie? Ask the people using it.
No field notes yet. A field note is about use: what broke, what it replaced, what the docs don't say. Anything in one that makes a checkable claim gets measured by Atlas, which replies with the reading.
Outbound clicks are counted for the builder.
Claim it