Engineering · SCIM pricing
VictorOps / Splunk On-Call SCIM pricing
On call scheduling and incident alerting. SCIM costs extra: 5 times the price of the plan most teams buy.
SCIM pricing for every app →What Okta covers for VictorOps / Splunk On-Call, and what StitchOps adds.
Okta signs users in and manages accounts where the app supports it in the Okta Integration Network. StitchOps covers the rest of the VictorOps / Splunk On-Call account lifecycle.
In the OIN with SAML or OIDC sign in and provisioning.
StitchOps covers 2 of 8 capabilities for VictorOps / Splunk On-Call.
| Capability | Okta, from the OIN | StitchOps |
|---|---|---|
| Single sign on | SAML or OIDC from the OIN listing. | Not needed. |
| Shared accounts and MFA | Not part of the OIN listing. | Shares VictorOps / Splunk On-Call logins and their MFA across a team, with credentials kept in your vault. |
| Joiners | Creates accounts through the OIN connector. | Not needed. |
| Movers | No account updates in the OIN. | Changes VictorOps / Splunk On-Call roles and access when someone changes jobs, anywhere a person can log in and act. |
| Leavers | Deactivates accounts through the OIN connector. | Not needed. |
| Password rotation | Not needed for users who sign in with SAML or OIDC. | Rotates shared admin logins in VictorOps / Splunk On-Call on a schedule or after an offboarding. |
| Access reviews | The connector lets Okta read and remove VictorOps / Splunk On-Call accounts for reviews. | Not needed for reviews of assigned access. |
| Audit evidence | Okta logs the changes its connector makes. | Not needed. |
Single sign on
Okta, from the OIN
SAML or OIDC from the OIN listing.
StitchOps
Not needed.
Shared accounts and MFA
Okta, from the OIN
Not part of the OIN listing.
StitchOps
Shares VictorOps / Splunk On-Call logins and their MFA across a team, with credentials kept in your vault.
Joiners
Okta, from the OIN
Creates accounts through the OIN connector.
StitchOps
Not needed.
Movers
Okta, from the OIN
No account updates in the OIN.
StitchOps
Changes VictorOps / Splunk On-Call roles and access when someone changes jobs, anywhere a person can log in and act.
Leavers
Okta, from the OIN
Deactivates accounts through the OIN connector.
StitchOps
Not needed.
Password rotation
Okta, from the OIN
Not needed for users who sign in with SAML or OIDC.
StitchOps
Rotates shared admin logins in VictorOps / Splunk On-Call on a schedule or after an offboarding.
Access reviews
Okta, from the OIN
The connector lets Okta read and remove VictorOps / Splunk On-Call accounts for reviews.
StitchOps
Not needed for reviews of assigned access.
Audit evidence
Okta, from the OIN
Okta logs the changes its connector makes.
StitchOps
Not needed.
Okta coverage from the Okta Integration Network, read October 10, 2026. VictorOps on okta.com StitchOps for Okta →
SCIM and API tax
What VictorOps / Splunk On-Call charges to automate accounts.
VictorOps / Splunk On-Call includes SCIM provisioning only on Enterprise / Full-Stack, at $25 per user a month. That is 5 times the price of the plan most teams buy (Starter, $5 per user a month). For 100 users, the SCIM tax comes to about $24,000 a year.
SSO sits on the same plan as SCIM or above it. If you need SSO anyway, that upgrade is not avoidable, and the calculator counts it that way.
Pricing notes
Status moved from partial to gated: SSO/SCIM class features sit on Enterprise tier ($25 per user a month annual, $45 per user a month monthly). Starter $5 per user a month annual baseline.
Last verified 2026-06-12. Source · SCIM pricing for every app · Method
Pricing data includes the SCIM Tax Index (Iden), CC BY 4.0, https://scimtax.org/. Modified and extended by StitchOps.
Estimate VictorOps / Splunk On-Call and your other apps
Loading prices.
Expected scenario, list prices, SSO required, default department shares.
Automate VictorOps / Splunk On-Call accounts on the plan you have.
StitchOps carries what your identity provider decides into the app, through an API when one exists, and anywhere a person can log in and act when one does not.
Joiners
Create the VictorOps / Splunk On-Call account with the right role when your HR system or identity provider says someone starts.
Movers
Change VictorOps / Splunk On-Call roles, teams and access when someone changes department or manager.
Leavers
Remove VictorOps / Splunk On-Call access the same day someone leaves, and free the seat.
Access checks
List who can log in to VictorOps / Splunk On-Call on a schedule, with evidence for the audit.
Common questions.
Does VictorOps / Splunk On-Call support SCIM?
Yes, but only on Enterprise / Full-Stack, at $25 per user a month. On the plan most teams buy, SCIM is not available.
Which VictorOps / Splunk On-Call plan includes SCIM?
Enterprise / Full-Stack, at $25 per user a month, against Starter, $5 per user a month for the plan most teams buy. At 100 users the difference is about $24,000 a year.
Can VictorOps / Splunk On-Call accounts be automated without upgrading?
Yes. StitchOps creates, changes and removes VictorOps / Splunk On-Call accounts on the plan you already have, triggered by the events your identity provider already sends. It uses an API when one exists and works anywhere a person can log in and act when one does not.
Is VictorOps / Splunk On-Call in the Okta Integration Network?
Yes. As of October 10, 2026, the OIN lists VictorOps and Splunk On-Call with SAML, SWA sign in and provisioning to create and deactivate users.
Can Okta deprovision VictorOps / Splunk On-Call users?
Yes. The OIN connector deactivates VictorOps / Splunk On-Call accounts when a user is removed in Okta.
Last updated . Product names are trademarks of their respective owners. StitchOps is not affiliated with or endorsed by them.
Start with one workflow that never had an API.
Fifteen minutes on your top three manual processes. We tell you which one to run first.