Splunk On-Call vs Regen
FluidifyAI Regen Pro is a flat $100 a month with unlimited seats, a 30-day free trial and no credit card needed, with every limit and overage rate published on a pricing page that has stayed put. For a 50-seat team that is about $1,200 a year, against about $27,000 a year at Splunk On-Call's Enterprise tier pricing, which Splunk no longer publishes on its own site.
Splunk On-Call no longer has its own pricing page. The URL Splunk used to publish tier pricing at, splunk.com/en_us/products/pricing/oncall.html, now returns a 404. The only official pricing left is a single line buried in the general Splunk observability pricing page: up to 10 seats for $5 a user monthly, billed annually. The three-tier structure most sites still quote, Starter at $10 a user, Growth at $35, Enterprise at $45, now lives only on third-party aggregators like Capterra, not on Splunk's own site. Splunk On-Call still runs and still takes new customers, but it is not being sold or maintained the way it was as VictorOps. This is a comparison of Regen specifically, not the rest of the FluidifyAI suite.
What's actually included
VictorOps built a genuinely good oncall product before Splunk bought it in 2018: ChatOps-first incident collaboration, a rules engine for routing and enriching alerts, and machine-learning-based responder suggestions that were ahead of most of the category at the time. For a team already standardized on Splunk for logs and monitoring, the Splunk integration for Splunk On-Call is a real, still-supported advantage: alerts flow in without a third-party connector to maintain.
Regen covers the same core oncall mechanics without requiring a Splunk stack underneath it: an incident lifecycle with an immutable timeline, multi-tier escalation policies with repeat cycles, and alert ingestion from Prometheus Alertmanager, Grafana, AWS CloudWatch and any tool that can call a webhook, with chat integrations for Slack, Microsoft Teams (beta), Discord and Telegram. Oncall schedules support layers, rotations, overrides, holiday calendars and individual leave.
Product status: two acquisitions deep
Splunk bought VictorOps in 2018 and renamed it Splunk On-Call. Cisco then closed its roughly $28 billion acquisition of Splunk itself on March 18, 2024, so the oncall product now sits inside a company two ownership changes removed from the team that built it. Its documentation has been folded accordingly: the same integration pages now live under both Splunk Enterprise's "Alert and Respond" section and Splunk Observability Cloud's "On-Call" monitoring section, rather than a single standalone product tree.
That repositioning shows up in the numbers. PeerSpot's category tracking put Splunk On-Call's mindshare in IT alerting and incident management at 3.5% as of September 2026, down from 4.5% a year earlier, ranked ninth in the category. Complaints about slow feature development go back further than that: a 2021 Capterra review already described the product as "left to rot on the vine" since the Splunk acquisition, citing virtually no new features and an SSO setup that stayed awkward for years. Splunk On-Call is not shutting down. It is also clearly not the roadmap priority it once was as an independent company.
Pricing and ownership
Working from the tiers third-party aggregators still list, a 50-person team on Enterprise at $45 a seat monthly runs $2,250 a month, about $27,000 a year. Splunk's own site no longer confirms or denies that figure since the dedicated pricing page is gone; the one number it does publish, $5 a user monthly for up to 10 seats billed annually on the general observability pricing page, only covers a small team and doesn't say what happens past 10 seats without a sales call.
Regen's Pro plan is a flat $100 a month for a 50-person team, about $1,200 a year, with no per-seat multiplier, and the pricing page it's quoted from has not moved. Seats, teams, incidents, schedules and escalation policies are unlimited, and the usage allowances, such as 10 GB of storage, 10,000 emails and 25,000 AI credits a month, are published on the pricing page along with the overage rates.
Deployment, security and reliability
Splunk On-Call has always been SaaS-only. Comparitech's review confirms there is no on-premises version and never has been; it runs exclusively as a hosted service, sold in part through the AWS and Azure marketplaces. Regen's Pro plan runs as cloud SaaS; Enterprise adds on-prem, private cloud and air-gapped deployment, FDE-managed on the customer's own infrastructure.
SSO, AI and automation
SSO for Splunk On-Call is still explicitly labeled a beta. Splunk's own documentation on SCIM and Okta provisioning states plainly that setup "is currently not a self-service process and requires contacting the Support team," and warns the release "may contain defects or deficiencies." Regen ships SSO and SAML 2.0 for Okta, Azure AD, Google Workspace and any compliant identity provider, self-service.
Splunk On-Call's post-incident review feature generates a timeline and MTTA/MTTR metrics, but writing the actual post-mortem narrative is still a manual step: reconstructing what happened from that timeline, Slack messages and call notes. Regen generates the narrative itself. Incident summaries, post-mortems and handoff digests are written automatically and synced back to Slack and Teams, on 25,000 AI credits a month included in the Pro price, and it isn't a separate line item.
Migration
Regen's one-click migration list currently covers Grafana OnCall, Opsgenie and PagerDuty: schedules and escalation policies import directly, no dedicated Splunk On-Call importer yet. Moving off Splunk On-Call today means rebuilding schedules and escalation paths by hand or via Regen's API, not a one-click pull. Given how far Splunk On-Call has receded from active development, and how little of its own roadmap Splunk is publishing for it, teams evaluating a move are generally doing so because the tool has stopped moving, not because of a feature they'd be giving up.