Public docs
Platform Overview
How opSentry works end-to-end — the product loop, key concepts, and where everything lives.
What opSentry does
opSentry is a change intelligence platform. It connects your engineering team's releases to the people who manage customer and partner relationships — CS, support, partnerships, and account management.
When a change ships, opSentry identifies which partners it affects and surfaces that impact in your workspace before it reaches a support queue. For the product story and the reasoning behind it, see the How it works page.
---
The product loop
Every workflow in opSentry follows the same loop:
- A change comes in — either manually created by a team member, or ingested automatically from a changelog via the AI pipeline
- opSentry identifies risk — severity (High, Medium, Low), affected partners, alert type, and a plain-language summary
- An alert is created — it becomes Active and appears on the Dashboard and in the Alert Log
- Your team manages the lifecycle — assigns ownership, tracks the impacted partners, and resolves when the risk is cleared
- Partners move through onboarding — the Partner Onboarding board tracks each partner's journey from Outreach to Live, with health signals tied to the alert system
---
Key concepts
Alerts
An alert represents a single risk event. It has a severity (High, Medium, Low), a status (Active or Resolved), a list of affected partners, and an optional alert type and summary. Alerts can be created manually or via the AI ingest pipeline.
Status is derived — not stored:
- No
resolved_attimestamp → Active resolved_atis set → Resolved
Severity is independent of status. A High severity alert stays High when resolved — only the status changes.
Partner Map
Your partner map is a spreadsheet-style table of all your partners — their names, API scopes, product area, and lifecycle status. opSentry uses this to cross-reference which partners are affected by each incoming alert. You upload it once and maintain it from the Partners section.
Partner statuses (Active, Onboarding, At Risk, Triaging, Inactive) are configurable in Settings. Partners marked Inactive are excluded from alert auto-matching.
Partner Onboarding Pipeline
A shared Kanban board that tracks partners as they move through your onboarding process — from first outreach through to live. Columns represent stages (configurable in Settings). Cards show real-time health signals: active alert severity, days in the current stage, and a warning if the partner has been stuck too long.
Personal Boards
In addition to the shared pipeline, each team member can maintain personal boards with their own stage configuration. These are independent — a partner can be on the shared board and a personal board simultaneously.
Workspace
Everything in opSentry is workspace-scoped. Your alerts, partners, team members, boards, and apps all belong to a single workspace. The workspace ID is established at signup and is required on every API call.
---
Navigation
- Dashboard — real-time overview of impacted partners, alert stats, stuck onboarding partners, and recent activity
- Alerts — full alert log with filtering, lifecycle management, and detail view
- Partners — partner map table, Partner Onboarding board, Company Overview, and personal boards
- Settings — pipeline configuration, team management, partner statuses, and threshold controls