⌘K

v1.3

OpsKnight · v1.3

Documentation

How to run OpsKnight, page the right person, and keep a record of the night. Written for this version — switch in the sidebar for older releases.

Install on your machines

Compose, Helm, and the secrets first boot needs.

Who gets paged

Email, SMS, push, Slack, WhatsApp, webhooks — not voice.

When something breaks

Incidents, acknowledge, assign, and write what happened.

Slack rooms

A channel for the incident, if this version includes ChatOps.

Status page

Tell customers what is down. One page per install.

API

Events ingest and incident APIs for this version.

All sections

Getting Started Core Concepts Administration Integrations API Reference Deployment Security Internals Mobile Troubleshooting Guide

This version

OpsKnight is a self-hosted incident product: on-call, paging, incidents, status, and postmortems on your machines.

This tree is v1.3. Switch versions in the sidebar for older releases.

Start here

Installation — Compose or Helm. First boot needs NEXTAUTH_SECRET and ENCRYPTION_KEY.
Notifications — How someone actually gets paged (no voice).
Incidents
Escalation policies
On-call schedules
Slack ChatOps — war rooms in this version
PagerDuty Events API v2 ingest
Status page — one public/private page per install
OIDC SSO
Encryption
API

SSO is OIDC, not SAML. Microsoft Teams and Google Chat are webhook formats, not Slack-style rooms.