About · v2.0.0 · AGPL-3.0-only

About OpsKnight

OpsKnight is a self-hosted incident command center and on-call platform for teams that want control of their incident data, deployment model, and operational workflow.

OpsKnight provides end-to-end alerting, voice & mobile paging, escalation policies, Slack & Microsoft Teams 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 want a self-hosted Community foundation with a clear path for separately licensed Enterprise capabilities. The Community application includes 28 inbound parsers, Slack and Microsoft Teams war room bots, status pages, local accounts, and supported SSO capabilities according to the release documentation.

Who it is not for

Anyone who needs a fully managed hosted service today or capabilities not listed in the current release documentation.

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

Mission

Make modern on-call, paging, war rooms, status pages, and postmortems available to engineering teams that can run Docker Compose or Helm while keeping Community licensing, commercial boundaries, and deployment ownership explicit.

License & Open Source

The active v2.0.0 Community development line is licensed under AGPL-3.0-only. Source code for the Community application is openly available on GitHub, and the license shipped with each artifact controls that artifact.

Published v1.4.0 and earlier releases keep the Apache-2.0 terms that accompanied them. The v2.0.0 transition does not retroactively remove those rights.

Separately licensed Enterprise modules, hosted services, support, or other commercial offerings may be introduced without changing the license of already published Community artifacts. See the license transition notice for the exact boundary.

Maintainer & Contact

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