Compare · v2.0.0 · as of 2 Oct 2026

OpsKnight vs PagerDuty

Vendor-hosted incident and on-call with commercial plans and add-ons. Native voice, Slack/Teams apps, Status Pages, and Events API v2. OpsKnight Community is self-hosted and supports the Events API v2 payload shape at your URL; commercial OpsKnight capabilities can be packaged separately.

Side by side

Capability	OpsKnight	PagerDuty
How you run it
Deployment OpsKnight: Compose, Swarm, Helm, Kustomize. Others: vendor product model as of Oct 2026.	Self-hosted: Compose, Swarm, Helm, Kustomize (your VPC)	Vendor SaaS
Software license OpsKnight v2.0.0: AGPL-3.0-only. Published v1.4.0 and earlier retain the licenses shipped with those artifacts, including Apache-2.0 where applicable. Grafana OnCall OSS was AGPLv3; that repo is archived.	AGPL-3.0-only (v2.0.0)	Proprietary
Commercial model OpsKnight Community and commercial offerings have separate licensing boundaries. Vendor pricing references should be confirmed on vendor sites.	Self-hosted Community; Enterprise/hosted capabilities may be packaged separately	Professional $25/user/mo or $21 annual; Business/Enterprise and add-ons vary
Incident data location	Your Postgres / VPC for Community self-hosting	PagerDuty cloud
Product standing (Oct 2026) OpsKnight v2.0.0 is the active stable release (AGPL-3.0-only); v1.4.0 remains historical Apache-era stable. Atlassian Opsgenie and Grafana status from their public migration/archive pages.	v2.0.0 stable; v1.4.0 historical Apache release	Actively sold
Incident response
Incident lifecycle OpsKnight Prisma IncidentStatus. Others: core incident/alert products.	Open, ack, snooze, suppress, resolve	Triggered, acknowledged, resolved (plus snooze / reassign)
On-call schedules OpsKnight layers/overrides. Others: documented schedule products.	Layers, rotations, overrides, timezones	Schedules, layers, overrides
Escalation policies	Steps: user, schedule, or team
Outbound paging channels OpsKnight NotificationChannel enum + docs. Vendor contact-method docs.	Email, SMS (Twilio/SNS), push, Slack, Teams, WhatsApp, voice paging (Twilio), webhook (v2.0.0)	Push, phone, SMS, email, Slack; WhatsApp in Early Access
Native voice / phone calls OpsKnight v2.0.0 adds Twilio VOICE channel for triggered-incident paging with responder ack input. Others: notification/contact docs.	Twilio voice paging on incident trigger with responder ack input (v2.0.0)	Yes — phone contact method
Slack ChatOps war rooms OpsKnight Slack OAuth war rooms from v1.2. Vendor Slack apps.	Channel per incident; ack/assign/resolve from Slack	Slack app: dedicated incident channels, ack/resolve, conference bridge
Microsoft Teams ChatOps OpsKnight v2.0.0: native Teams app via Entra + Azure Bot — war rooms, Adaptive Cards, ack/resolve from channel, identity linking, meeting collaboration. Others: published Teams apps.	Native Teams app: war rooms, Adaptive Cards, ack/resolve, identity linking (v2.0.0)	Native Teams app: channel cards, ack/resolve, service mapping
Video bridge on incident OpsKnight: Jitsi generator + Zoom/Meet URL templates. Vendor collaboration docs.	Jitsi; Zoom/Meet via URL template	Zoom integration + stored conference bridges from Slack
Postmortems + action items OpsKnight Postmortem + ActionItem models. Vendor PIR docs.	Timeline-based postmortems and action items	Post-incident review / timeline tools (plus add-on AI products)
Status page OpsKnight published Community baseline: one page per install. Other vendors: status-page product docs.	Community baseline: one public/private page with custom domain and subscribers	Internal / external / private Status Pages (plan-gated; custom domain on external)
MTTA / MTTR / SLA OpsKnight SLA definitions/analytics. Other vendors: reporting products.	MTTA/MTTR and SLA definitions in-app	Analytics API and Insights
Mobile OpsKnight: installable PWA. Vendor App Store / Play apps.	Installable PWA with push; no App Store listing	iOS and Android apps
Integrations & platform
Inbound monitoring webhooks OpsKnight published docs catalog: 28 native parsers. Other vendors: integration directories.	28 native parsers + generic JSON	Events API v2 + large integration directory
PagerDuty Events API v2 ingest OpsKnight docs: POST /api/integrations/pagerduty/v2/enqueue. PagerDuty: events.pagerduty.com/v2/enqueue.	Yes — ingest adapter (routing_key payload). Not a PagerDuty clone	Native Events API v2
Jira Cloud OpsKnight published integration and vendor Jira integration guides.	Bi-directional issue sync	Bidirectional Jira Cloud extension
REST API keys		REST API + Events API keys
SSO OpsKnight v2.0.0: OIDC with PKCE, JIT provisioning, claim-to-role mapping, and SCIM 2.0 user provisioning. Vendor SSO docs for other products.	OIDC (PKCE, JIT, claim-to-role) + SCIM 2.0 provisioning (v2.0.0)	SAML 2.0 IdP; Google OAuth; OIDC for private status pages
RBAC + audit log OpsKnight roles + AuditLog. Other vendors: documented admin controls.	Roles + audit log; advanced governance can be packaged separately	Roles + audit / analytics (plan-dependent)

As of 2 Oct 2026. OpsKnight feature cells reflect the v2.0.0 stable release (AGPL-3.0-only); v1.4.0 and earlier artifacts retain their historical Apache-2.0 terms. Vendor columns summarize public documentation and packaging, not a contract. Confirm current vendor pricing before making a purchasing decision.

Zero-Code Drop-In Ingest Adapter

Already sending alerts to Events API v2? OpsKnight provides a native ingest adapter so you can point Alertmanager, Terraform, and Datadog webhooks directly to OpsKnight without rewriting alert rules.

Zero-Code Migration: Events API v2 Ingest Adapter

Drop-in Endpoint

Keep your existing alert payloads. Just change the destination URL to OpsKnight.

Ingest adapter docs

Select Your Source Stack

Why zero-code migration?

Point your existing Alertmanager pagerduty_configs receiver directly to your self-hosted OpsKnight instance.

Standard routing_key & dedup_key support

Automatic trigger / resolve lifecycle

alertmanager.yml

receivers:
  - name: 'opsknight-oncall'
    webhook_configs:
      # Swap endpoint to your self-hosted OpsKnight instance
      - url: 'https://opsknight.yourcompany.com/api/integrations/pagerduty/v2/enqueue'
        send_resolved: true
        http_config:
          authorization:
            # Your OpsKnight integration routing key
            credentials: 'YOUR_OPSKNIGHT_ROUTING_KEY'

route:
  receiver: 'opsknight-oncall'
  routes:
    - match:
        severity: critical
      receiver: 'opsknight-oncall'

Endpoint: POST /api/integrations/pagerduty/v2/enqueue

Trademark & Compatibility Notice: PagerDuty® is a registered trademark of PagerDuty, Inc. OpsKnight Community is an independent open-source project licensed under AGPL-3.0-only and is not affiliated with, endorsed by, or sponsored by PagerDuty, Inc. Compatibility refers solely to an ingest adapter supporting the public Events API v2 JSON payload schema.

Full matrix and cost sketch Install docs