SSO is the easy half. Provisioning is where the paywall is.
Our research on the Okta Integration Network shows three times as many apps support federated sign in as support provisioning. Why that gap exists, what it costs, and how to close it.
Thomas Bieser, Cofounder and CEO ·
For years the complaint was the SSO tax: vendors charging extra to let you sign in through your identity provider. It is still real. But when we looked at what the Okta Integration Network actually supports, a bigger gap showed up somewhere else.
What the catalog shows
In our November 2026 research on all 8,430 Okta Integration Network listings:
- 2,789 listings (33%) support federated sign in with SAML, OIDC or WS Fed.
- 837 listings (about 10%) can both create and deactivate users.
- 4,999 listings (59%) offer password fill only, with no federation at all.
So for every app that can be told to remove a user, more than three can be signed into through Okta. Sign in is the easy half. Provisioning is the half most apps never ship, and the half vendors most often charge for when they do.
Why vendors treat them differently
- SSO is cheap to build. SAML and OIDC are a login page change. Many vendors now include them on mid tier plans because buyers insist.
- Provisioning is real work. A SCIM server has to create, update, deactivate and reconcile users, and it has to keep doing it reliably. Vendors that build it recover the cost on their top plan.
- Buyers notice SSO first. People see the login screen every day. Nobody sees the account that should have been removed.
The result is a market where sign in got easier while the SCIM tax stayed where it was.
Why provisioning is the half that matters
Single sign on decides how someone gets in. Provisioning decides whether the account exists at all. When someone leaves, turning off their user in the identity provider ends sign in through it. The account inside an app without provisioning stays live, with its local password, API tokens and shared logins. That is how orphaned accounts happen.
An auditor asking how fast a leaver lost access is asking about provisioning, not SSO.
How to close the gap
- Sort your apps into three groups. Provisioning on your current plan, provisioning only on a higher plan, and no provisioning at any price.
- Use what you already pay for. Turn on SCIM wherever your plan includes it.
- Price the upgrades honestly. The SCIM tax calculator shows the cost for your headcount, including where SSO and SCIM sit on the same plan.
- Automate the rest on the plans you have. StitchOps carries your identity provider's joiner, mover and leaver events into apps where SCIM costs extra or does not exist, anywhere a person can log in and act. Every change is logged.
See pricing for what that costs per app.
Frequently asked questions
- What is the difference between the SSO tax and the SCIM tax?
- The SSO tax is the extra a vendor charges to let people sign in through your identity provider. The SCIM tax is the extra charged for automated provisioning, so accounts are created and removed when your identity provider says so.
- Which one matters more for security?
- Provisioning. Single sign on controls how people get in. Provisioning controls whether the account exists at all after someone leaves.
- How common is provisioning support compared with SSO?
- In our November 2026 research on 8,430 Okta Integration Network listings, 2,789 (33%) support SAML, OIDC or WS Fed sign in, and 837 (about 10%) can both create and deactivate users.
- How do I get provisioning without paying the upgrade?
- StitchOps carries your identity provider's lifecycle events into apps where SCIM costs extra or does not exist, anywhere a person can log in and act, on the plan you already have.
Okta is a trademark of Okta, Inc. Counts are from StitchOps' review of the public Okta Integration Network catalog on November 17, 2026.