OpsKnight
opsknight.com
- Free plan
- Web
- iPhone and iPad
- Android
- API
- Self-hosted
What OpsKnight is
OpsKnight is a self-hosted incident command and on-call platform for alerting, paging, escalation policies, war rooms, status pages, and incident timelines. Monitoring webhooks can create incidents for responders to acknowledge, assign, or resolve, and fingerprint grouping can reduce duplicate paging. Schedules support rotations, time zones, and swaps. Pages can go through SMS, push, Slack, Microsoft Teams, WhatsApp, or automated voice calls; a responder can acknowledge a voice page by pressing 1, while unanswered or unacknowledged calls move to the next escalation tier. Community includes one public, restricted, or private status page per install, plus SLA policies, support-hours rules, and MTTA/MTTR analytics. The integrations page lists 27 native integrations, including Datadog, Sentry, Prometheus Alertmanager, Grafana Alerting, AWS CloudWatch, GitHub Actions, Slack, and Jira Cloud. Community is self-hosted and licensed under AGPL-3.0-only. It requires PostgreSQL 14+ and configured secrets. The maker says there is no hosted cloud, external telemetry, or vendor phone-home; OpsKnight is not intended for teams seeking a fully managed hosted service today.
Who it suits
OpsKnight is aimed at SRE, DevOps, and platform teams already able to run Postgres, Docker, or Kubernetes. It may also suit teams with strict compliance requirements that want the Community data plane in their own environment.
Good to know, and what to watch
- Supports on-call rotations, time zones, and swaps.
- Pages through SMS, push, chat, and voice.
- Includes 27 listed native integrations.
- Community includes one status page per install.
- Maker states there is no external telemetry.
- Requires PostgreSQL 14+ and configured secrets.
- Community is self-hosted.
- Community includes one status page per install.
- Not intended for users needing managed hosting today.
Plans
Every plan and priceCommunity
Free plan
Getting started
- Open https://opsknight.com/
- Prepare PostgreSQL 14+ and configured secrets
- Choose Docker Compose, Docker Swarm, Helm, or Kustomize
- Use Docker Engine 20+ with Compose 2+ or Kubernetes 1.24+ as recommended
- Deploy the Community edition in your environment
- Configure local accounts or OIDC single sign-on
Limits to check
The free Community plan includes one public, restricted, or private status page per installation. It is self-hosted under AGPL-3.0-only, while separately licensed Enterprise modules, support, or hosted offerings may be offered independently.
The verdict
OpsKnight provides incident response, paging, and status-page functions for teams prepared to host and operate it themselves. Its deployment requirements and lack of a fully managed service today are central selection considerations.
Questions people ask
How much does OpsKnight Community cost?
The Community plan is free and is self-hosted under AGPL-3.0-only.
Which deployment methods are supported?
Community can be deployed with Docker Compose, Docker Swarm, Helm, or Kustomize. PostgreSQL 14+ and configured secrets are required.
Which paging channels are available?
Pages can use SMS, push, Slack, Microsoft Teams, WhatsApp, and automated voice calls. Voice pages can be acknowledged by pressing 1.
Does OpsKnight provide a status page?
Community includes one public, restricted, or private status page per installation, with an optional custom domain.
Can teams use single sign-on?
Yes. OpsKnight supports local accounts and OIDC single sign-on with Google Workspace, Okta, Azure AD, Keycloak, and Authentik.
Is there a separate mobile app?
Responders can acknowledge incidents through an installable PWA using the same login as desktop; the site describes it as not a separate app-store product.
What the maker publishes
- Audience
- The maker describes it as intended for SRE, DevOps, and platform teams already running Postgres, Docker, or Kubernetes, including teams with strict compliance requirements. source
- Commercial boundary
- The Community application is licensed under AGPL-3.0-only, while separately licensed Enterprise modules, support, or hosted offerings may be offered independently. source
- Custom ingestion
- Generic JSON webhooks are supported, with SHA-256 fingerprint deduplication for custom monitoring tools and scripts. source
- Custom ingestion
- Generic JSON webhooks are supported for internal tools, Kubernetes operators, cron jobs, and custom monitoring scripts. source
- Deployment
- Community is self-hosted and can be deployed with Docker Compose, Docker Swarm, Helm, or Kustomize. source
- Deployment requirements
- The install page lists Docker Engine 20+ with Compose 2+ or Kubernetes 1.24+, PostgreSQL 14+, and configured secrets as prerequisites. source
- Identity
- OpsKnight supports local accounts and OIDC single sign-on with Google Workspace, Okta, Azure AD, Keycloak, and Authentik. source
- Identity controls
- OpsKnight supports local accounts and OIDC single sign-on with Google Workspace, Okta, Azure AD, Keycloak, and Authentik, along with workspace and team roles. source
- Incident workflow
- It turns monitoring webhooks into incidents that responders can acknowledge, assign, resolve, and group by fingerprint to reduce duplicate paging. source
- Incident workflow
- It groups related alerts into incidents that responders can acknowledge, assign, resolve, and document from a timeline. source
- Integrations
- The integrations page lists 27 native integrations, including Datadog, Sentry, Prometheus Alertmanager, Grafana Alerting, AWS CloudWatch, GitHub Actions, Slack, and Jira Cloud. source
- Integrations
- The integrations page lists 27 integrations, including Datadog, New Relic, Prometheus Alertmanager, Grafana, AWS CloudWatch, Slack, and Jira Cloud. source
- Intended users and limitation
- OpsKnight describes itself as intended for SRE, DevOps, and platform teams that can run Postgres, Docker, or Kubernetes, and says it is not for users who need a fully managed hosted service today. source
- On-call and paging
- It supports rotations, time zones, swaps, and paging through SMS, push, Slack, Microsoft Teams, WhatsApp, and automated voice calls with keypad acknowledgment. source
- On-call and paging
- It supports rotations and escalation, with voice calls, SMS, push, Slack, Microsoft Teams, and WhatsApp notifications. source
- Phone access
- Responders can acknowledge incidents from an installable PWA that uses the same login as desktop; the site says it is not a separate app-store product. source
- Purpose
- OpsKnight is a self-hosted incident command and on-call platform for alerting, paging, escalation, war rooms, status pages, and postmortem timelines. source
- Requirements
- OpsKnight requires PostgreSQL 14+ and configured secrets; the install page recommends Docker Engine 20+ with Compose 2+ or Kubernetes 1.24+. source
- Security
- The security page says credentials are encrypted at rest in PostgreSQL using AES-256-CBC envelope encryption, and inbound webhooks use cryptographic verification. source
- Security
- The security page says stored credentials use AES-256-CBC envelope encryption and inbound webhook signatures are checked with constant-time verification. source
- Status and reporting
- The Community edition includes one public, restricted, or private status page per install, plus SLA policies, support-hours rules, and MTTA/MTTR analytics. source
- Status page limit
- The Community edition includes one public, restricted, or private status page per install, with an optional custom domain. source
- Support and hosting
- The maker says OpsKnight is not for users who need a fully managed hosted service today; separately licensed support or hosted offerings may be offered independently. source
- Telemetry
- The maker states there is no external telemetry, no vendor phone-home, and no hosted cloud holding encryption keys. source
Checked against the maker's pages on 5 Oct 2026.