OpsKnightTHE PROBLEM
SELF-HOSTED INCIDENT MANAGEMENT
Bring incident operations onto your infrastructure.
Keep operational data and deployment decisions under your control. Connect alerts to on-call, response, customer updates and postmortems.
A PRACTICAL START
Deploy an integrated runtime, connect an inbound provider, configure schedules and routing, then validate one synthetic incident end to end.
PRODUCT SURFACES
Assemble only what the workflow needs.
Incident command
Keep ownership, responders, timeline, notes and action items together from first alert to resolution.
On-call & escalation
Build rotations, schedule overrides and escalation policies around the people responsible for each service.
Paging
Route urgent pages through configured providers and inspect attempts, retries and terminal delivery outcomes.
IMPLEMENTATION CONTEXT
Turn the use case into an operating model.
The product workflow is only useful when deployment, integrations, access controls and validation are planned together.
How to run it
Start with integrated Docker Compose when a single application host is acceptable. Move to split runtime or Kubernetes when availability, workload isolation, or independent scaling requires it.
What to connect first
Connect one release-verified inbound provider first, map it to the owning service, then add ChatOps or issue-tracking only after the core alert-to-response path is proven.
What to decide up front
Set the public HTTPS origin, durable PostgreSQL and backups, production secrets, and the identity policy before exposing the installation to responders.
What to prove before production
Run a synthetic incident through ingestion, correlation, on-call resolution, paging, acknowledgement, customer communication, resolution, and follow-up.
IMPLEMENTATION PATH
Validate the whole journey before production.
Start with the deployment model, connect the required providers, configure identity and routing, then exercise a synthetic incident from signal to responder action and recovery.
Your incidents should belong to you.
Run OpsKnight on infrastructure you control.
v2.0.0 · AGPL-3.0-only · Self-hosted · 28 inbound integrations