Skip to content
StitchOps

Security · SCIM pricing

Splunk SCIM pricing

Log search, security monitoring and observability. SCIM costs extra.

SCIM pricing for every app →

What Okta covers for Splunk, 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 Splunk account lifecycle.

In the OIN with SAML or OIDC sign in and provisioning.

StitchOps covers 1 of 8 capabilities for Splunk.

  • 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 Splunk 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

    Updates accounts through the OIN connector.

    StitchOps

    Not needed.

  • 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 Splunk on a schedule or after an offboarding.

  • Access reviews

    Okta, from the OIN

    The connector lets Okta read and remove Splunk 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. Splunk Enterprise on okta.com StitchOps for Okta →

SCIM and API tax

What Splunk charges to automate accounts.

Splunk includes SCIM provisioning only on Enterprise (Splunk Cloud 9.1+). That plan is sold by quote, so the price jump is not published.

Pricing notes

Splunk Cloud SCIM is deprovision only (no create/update) and requires Enterprise tier with SAML SSO. Pricing not publicly disclosed.

Last verified 2026-06-12 (estimate). 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 Splunk and your other apps

Loading prices.

Tune it in the full calculator

Expected scenario, list prices, SSO required, default department shares.

Automate Splunk 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 Splunk account with the right role when your HR system or identity provider says someone starts.

Movers

Change Splunk roles, teams and access when someone changes department or manager.

Leavers

Remove Splunk access the same day someone leaves, and free the seat.

Access checks

List who can log in to Splunk on a schedule, with evidence for the audit.

Common questions.

Does Splunk support SCIM?

Yes, but only on Enterprise (Splunk Cloud 9.1+), sold by quote. On the plan most teams buy, SCIM is not available.

Which Splunk plan includes SCIM?

Enterprise (Splunk Cloud 9.1+). It is sold by quote.

Can Splunk accounts be automated without upgrading?

Yes. StitchOps creates, changes and removes Splunk 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 Splunk in the Okta Integration Network?

Yes. As of October 10, 2026, the OIN lists Splunk Enterprise and Splunk Cloud and Splunk Cloud with SAML, SWA sign in and provisioning to create, update and deactivate users.

Can Okta deprovision Splunk users?

Yes. The OIN connector deactivates Splunk 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.