Splunk On-Call is the VictorOps heritage product: on-call that lives inside the Splunk ecosystem, sold through Splunk sales, with pricing that is not published per-user. For shops standardized on Splunk, keeping on-call in the same console is a coherent choice. For everyone else it means buying an ecosystem to get a pager. OpsPing is tool-agnostic (webhooks, native mappers, Opsgenie-compatible API), publishes its pricing, and focuses on the one thing a pager must do: wake the right engineer through iOS Critical Alerts and Android DND-bypass alarms.
Side by side
| OpsPing | Splunk On-Call (VictorOps) | |
|---|---|---|
| Pricing model | Public: $8–$15/responder/month | Via Splunk sales (historically per-host era pricing; quote today) |
| Ecosystem | Tool-agnostic — any webhook, email, or API client | Splunk-centric workflows and dashboards |
| Alert API compatibility | Opsgenie v2-compatible (GenieKey scheme) | Splunk On-Call API (VictorOps heritage) |
| Mobile paging | iOS Critical Alerts, Android DND-bypass alarms — core | Mobile app with push |
| Status pages | Included | Not a Splunk On-Call feature |
| Postmortems | One-click from audit trail, MD/PDF | Timeline exports |
| Private deployment | Private single-tenant deployments available | No — SaaS |
| Free tier | Up to 5 responders, unlimited push | Trial via sales |
Splunk On-Call pricing is quoted through Splunk sales and was historically per-host — no public per-user list price as of October 16, 2026. Confirm current packaging with Splunk.
What moves over cleanly
Splunk stays your detector: forward notables/alerts to OpsPing via webhook (generic JSON or email-to-alert). Teams, rotations, and escalation policies rebuild via API or import. If you also run Opsgenie-era integrations, the GenieKey-compatible endpoint means most of them just change host and key. The Opsgenie migration guide covers the pattern.
Choose Splunk On-Call if…
- Your organization is standardized on Splunk and wants on-call inside the same console, procurement, and support relationship.
- VictorOps-era rotations and integrations are deeply embedded and the migration appetite is low.
Choose OpsPing if…
- You want a published per-responder price instead of a sales-quote line item.
- Mobile delivery reliability is the requirement — critical alerts and DND-bypass alarms are architecture here, not an app checkbox.
- You want status pages and postmortems included, and a private deployment option.
FAQ
How much does Splunk On-Call cost?
Splunk does not publish per-user list pricing; it is quoted through sales and was historically priced per host. OpsPing publishes its prices: free up to 5 responders, $8 and $15 per responder/month.
Do we have to give up Splunk to use OpsPing?
No — OpsPing is not an observability platform and does not replace Splunk. Splunk keeps detecting and notifying; OpsPing receives the webhook, manages rotations and escalations, and pages with mobile-first delivery. The two run side by side.
Is Splunk On-Call being retired?
No end-of-life announcement covers Splunk On-Call itself (distinct from other Splunk products that have been sunset). It remains a maintained Splunkbase-connected product — the honest comparison is ecosystem fit and pricing transparency, not discontinuation.