Skip to content
StitchOps

Blog

The SCIM tax, measured: what we found in nine real company app stacks

We analyzed 335 apps across nine companies we worked with in 2026. One in five includes provisioning on the plan most teams buy. The rest charge more for it or never offer it.

, Cofounder and CEO ·

Most writing about the SCIM tax looks at vendor price lists. We wanted to know what it looks like inside real companies, so we went back to the application lists we analyzed with customers and prospects this year and counted.

The study

Between September and November 2026 we analyzed the application lists of nine companies: a consumer brand, two software companies, a security software company, a healthcare provider, two manufacturers, a construction holding company and an automotive parts maker. They range from about 50 to about 250 people.

Across them we counted 335 software apps. For each one we recorded two things, from vendor documentation and the Okta Integration Network:

  • SSO: does any plan support SAML or OIDC sign in.
  • SCIM: is automated provisioning included on the plan most teams buy, gated to a higher paid plan, or not offered at any price.

We counted only real software. Agencies, services, fee lines, browser extensions and the HR systems that act as identity sources were left out.

What we found

Of the apps whose SCIM status we could confirm:

  • 20% include SCIM on the plan most teams buy.
  • 35% offer SCIM only on a higher paid plan. That is the SCIM tax in its classic form.
  • 45% do not offer SCIM at any price.

So four in five apps cannot be provisioned automatically on the plan a team would normally buy.

SSO tells a different story. 83% of apps with a confirmed status support SAML or OIDC sign in on some plan. Sign in is widely available. Provisioning is not. Our research on the Okta Integration Network shows the same gap across the whole catalog: 33% of listings support federated sign in, and about 10% can both create and remove users.

The apps that show up everywhere

Some apps appeared in almost every stack. Microsoft 365, Google Workspace and Dropbox included provisioning on the plans these companies used. GitHub, ChatGPT, Slack, 1Password, Atlassian, Cloudflare and monday.com each required a higher plan for SCIM in every stack where we confirmed it.

Those are not niche tools. They are the core of a modern company, which is why the SCIM tax shows up on almost every renewal calendar.

Where "no SCIM at all" comes from

The 45% with no SCIM at any price are mostly the systems that run the business: warehouse and manufacturing software, dealer and lender portals, clinical and practice management systems, marketing tools and vendor portals. No plan upgrade fixes them. Their accounts are created and removed by hand, or not removed at all. See orphaned accounts.

How to read these numbers

  • Stacks differ. One consumer brand contributed 99 apps, many of them marketing tools without SSO or SCIM. Without it, the split of confirmed apps is 21% included, 42% gated and 38% none. The gated share rises, and the conclusion stays the same.
  • Some statuses are unknown. We could not confirm SCIM status for 54 apps, mostly thick clients and vendor portals, and left them out of the percentages.
  • Plans change. Vendors move features between plans. Statuses reflect our review at the time.

What to do with it

  1. Sort your own apps into included, gated and none.
  2. Use SCIM wherever your plan includes it.
  3. Price the gated apps. The SCIM tax calculator shows the upgrade cost for your headcount, and our renewal playbook shows when to stay and when to move down.
  4. Automate the rest on the plans you have. StitchOps carries your identity provider's joiner, mover and leaver events, from Okta, Microsoft Entra ID or Google Workspace, into apps where SCIM costs extra or does not exist, anywhere a person can log in and act. Every change is logged.

Want this analysis for your own stack? Send us your application list and we will return it app by app.

Pay for the plan you use, not for the protocol.

Frequently asked questions

What is the SCIM tax?
The extra a vendor charges for automated user provisioning, usually by putting SCIM only on its top plan and charging it on every seat, or the manual work you take on when no plan offers it.
How was this study done?
StitchOps analyzed the application lists of nine companies we worked with in 2026, 335 software apps in total, and recorded whether each supports SSO and whether SCIM is included on the base plan, gated to a higher plan, or not offered. Each company is anonymous.
How many apps include SCIM on the base plan?
Of the apps whose status we could confirm, 20% include SCIM on the plan most teams buy, 35% only on a higher paid plan, and 45% do not offer it at any price.
Is SSO easier to get than SCIM?
Yes. 83% of the apps with a confirmed status offer SAML or OIDC sign in on some plan, compared with 20% that include SCIM on the base plan.
How do I avoid the SCIM tax?
Keep SCIM where your plan includes it. For the rest, StitchOps carries your identity provider's joiner, mover and leaver events into the app on the plan you already have, anywhere a person can log in and act.

Study by StitchOps from application lists of nine companies, analyzed between September and November 2026. Companies are anonymous. Vendor plans change often; statuses reflect our review at the time. Trademarks belong to their owners.

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.