Compare · v2.0.0 · as of 2 Oct 2026
OpsKnight vs Splunk On-Call
Formerly VictorOps. Vendor-hosted on-call with phone/SMS/push and Slack/Teams apps. OpsKnight v2.0.0 is a separate AGPL-3.0-only self-hosted stack, not a Splunk add-on.
Side by side
| Capability | OpsKnight | Splunk On-Call |
|---|---|---|
| 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 (Splunk Observability) |
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 | Commercial Splunk On-Call plans |
Incident data location | Your Postgres / VPC for Community self-hosting | Splunk 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, ack, snooze, reroute, resolve |
On-call schedules OpsKnight layers/overrides. Others: documented schedule products. | Layers, rotations, overrides, timezones | Teams, rotations, paging policies |
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, SMS, phone, email; WhatsApp available in paging policy |
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 paging |
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: cards to ack/reroute/resolve/snooze; channel mapping |
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) | VictorOps Teams app: bi-directional ack/resolve/snooze |
Video bridge on incident OpsKnight: Jitsi generator + Zoom/Meet URL templates. Vendor collaboration docs. | Jitsi; Zoom/Meet via URL template | War-room automation (bring your conference tool) |
Postmortems + action items OpsKnight Postmortem + ActionItem models. Vendor PIR docs. | Timeline-based postmortems and action items | Post-incident reviews in the product |
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 | No first-party customer status page; use a third-party page |
MTTA / MTTR / SLA OpsKnight SLA definitions/analytics. Other vendors: reporting products. | MTTA/MTTR and SLA definitions in-app | MTTA/MTTR reports in product |
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 | REST + third-party integrations |
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 | Own REST / integrations |
Jira Cloud OpsKnight published integration and vendor Jira integration guides. | Bi-directional issue sync | Jira add-ons and webhooks |
REST API keys | API ID + API key | |
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 and SCIM 2.0 |
RBAC + audit log OpsKnight roles + AuditLog. Other vendors: documented admin controls. | Roles + audit log; advanced governance can be packaged separately | Team admin roles + org SSO |
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.
- PagerDuty notification rules
- PagerDuty contact methods
- PagerDuty Microsoft Teams
- PagerDuty Slack
- PagerDuty Status Pages
- PagerDuty Jira Cloud
- PagerDuty SSO (SAML 2.0)
- incident.io pricing
- incident.io on-call notifications
- incident.io SAML SSO
- incident.io status pages
- incident.io Jira
- Atlassian Opsgenie migration / EOL
- Opsgenie Microsoft Teams
- Opsgenie + Statuspage
- Squadcast pricing
- Squadcast notifications
- Squadcast Slack
- Squadcast Microsoft Teams
- Squadcast Jira Cloud
- Splunk On-Call notifications
- Splunk On-Call Slack
- Splunk On-Call Microsoft Teams
- Grafana OnCall OSS archive
- Grafana Cloud IRM
- Grafana IRM notifications
- Grafana IRM Microsoft Teams
- Grafana IRM mobile app