About · 1.4.0 · Apache-2.0

About OpsKnight

OpsKnight is a self-hosted incident command center and on-call platform. It exists because per-seat on-call SaaS gets prohibitively expensive as engineering teams scale, and because incident data belongs on the infrastructure you operate.

OpsKnight provides end-to-end alerting, paging, escalation policies, Slack ChatOps war rooms, public status pages, and postmortem incident timelines without third-party vendor lock-in.

OpsKnight is purpose-built self-hosted incident command. It is not a clone of anyone else’s proprietary cloud product.

Who it is for

SRE, DevOps, and platform teams that already run Postgres, Docker, or Kubernetes. Teams with strict compliance requirements (HIPAA, SOC 2, GDPR, Financial) that cannot place real-time incident timelines and architecture metadata in a multi-tenant vendor cloud.

Teams that would rather operate a resilient on-call pager than meter developer seats. Includes 27 inbound parsers, Slack war room bots, status pages, local accounts, and OIDC enterprise SSO.

Who it is not for

Anyone who needs a hosted SaaS cloud, native voice phone calls, or SAML in this release (local accounts and OIDC single sign-on are supported).

Anyone looking for a PagerDuty or Opsgenie clone — our Events API v2 is an inbound ingest adapter designed to make migration seamless. Change your webhook destination URL and test immediately.

Mission

Make modern on-call, paging, war rooms, status pages, and postmortems freely available to any engineering team that can run Docker Compose or Helm — without a SaaS subscription tax.

License & Open Source

OpsKnight is licensed under Apache-2.0. Source code is openly available on GitHub. There is no hidden enterprise tier or artificial seat metering.

Maintainer & Contact

Created and maintained by Dushyant Rahangdale. For security disclosures, press, or partnership inquiries: [email protected].