Compare · v2.0.0 · as of 2 Oct 2026

OpsKnight vs Opsgenie

Atlassian's standalone Opsgenie is closed to new purchases. Support ends 5 April 2027; alerting/on-call is moving into Jira Service Management. OpsKnight is independent self-hosted software under AGPL-3.0-only.

Side by side

CapabilityOpsKnightOpsgenie
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 (Atlassian Cloud)

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 separatelyNo new sales; capabilities moving to Jira Service Management

Incident data location

Your Postgres / VPC for Community self-hostingAtlassian 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 releaseStandalone: no new purchases; EOL 5 Apr 2027 → Jira Service Management
Incident response

Incident lifecycle

OpsKnight Prisma IncidentStatus. Others: core incident/alert products.

Open, ack, snooze, suppress, resolveAlert ack / close / snooze; incident module on higher plans

On-call schedules

OpsKnight layers/overrides. Others: documented schedule products.

Layers, rotations, overrides, timezonesSchedules and routing rules

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, email, SMS, voice (plan caps); Slack and Teams apps

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 — voice on historical paid plans

Slack ChatOps war rooms

OpsKnight Slack OAuth war rooms from v1.2. Vendor Slack apps.

Channel per incident; ack/assign/resolve from SlackSlack app: bidirectional alert actions

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)Teams V2 integration: ack/close/snooze from channel

Video bridge on incident

OpsKnight: Jitsi generator + Zoom/Meet URL templates. Vendor collaboration docs.

Jitsi; Zoom/Meet via URL templateZoom / conference integrations in directory

Postmortems + action items

OpsKnight Postmortem + ActionItem models. Vendor PIR docs.

Timeline-based postmortems and action itemsIncident notes; typical PIR in Confluence / JSM

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 subscribersPair with Atlassian Statuspage (separate product)

MTTA / MTTR / SLA

OpsKnight SLA definitions/analytics. Other vendors: reporting products.

MTTA/MTTR and SLA definitions in-appReporting on paid plans

Mobile

OpsKnight: installable PWA. Vendor App Store / Play apps.

Installable PWA with push; no App Store listingiOS and Android apps
Integrations & platform

Inbound monitoring webhooks

OpsKnight published docs catalog: 28 native parsers. Other vendors: integration directories.

28 native parsers + generic JSONLarge historical 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 cloneOwn API / migrators

Jira Cloud

OpsKnight published integration and vendor Jira integration guides.

Bi-directional issue syncBuilt-in Jira / JSM ecosystem

REST API keys

REST 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)SSO/SAML on historical paid plans

RBAC + audit log

OpsKnight roles + AuditLog. Other vendors: documented admin controls.

Roles + audit log; advanced governance can be packaged separatelyRoles + audit on paid plans

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.

Opsgenie Sunset Migration Guide

Migrate your on-call rotations, multi-tier escalation policies, and alerting webhooks seamlessly to an actively maintained self-hosted platform.

Opsgenie Migration Blueprint

Self-Hosted Alternative

Migrate off deprecating SaaS tiers to an independent on-call stack you control.

Webhook documentation
alertmanager.ymlyaml
receivers:
  - name: 'opsknight-primary'
    webhook_configs:
      - url: 'https://opsknight.yourcompany.com/api/v1/webhooks/prometheus'
        send_resolved: true
        http_config:
          bearer_token: 'YOUR_OPSKNIGHT_SERVICE_INTEGRATION_KEY'

route:
  receiver: 'opsknight-primary'
  group_by: ['alertname', 'cluster', 'service']
  group_wait: 30s
  group_interval: 5m
  repeat_interval: 4h
  routes:
    - match:
        severity: critical
      receiver: 'opsknight-primary'

Replace opsgenie_configs in Alertmanager with OpsKnight's native Prometheus webhook receiver.

Trademark Notice: Opsgenie and Jira Service Management are registered trademarks of Atlassian Pty Ltd. OpsKnight is an independent open-source project and is not affiliated with, endorsed by, or sponsored by Atlassian.