Skip to content
StitchOps

Blog

We counted every app in the Okta Integration Network. 90% can't provision users.

StitchOps research on all 8,430 Okta Integration Network listings, November 2026: how many support federated sign in, how many can create and remove users, and how many HR sources exist.

, Cofounder and CEO · ·

Most identity projects start with a simple promise. Okta decides who should have access, and every app makes that true on day one and on the last day. We wanted to know how often the apps can actually keep that promise. So we counted.

On November 17, 2026 we reviewed the public Okta Integration Network catalog and recorded what every one of its 8,430 integrations says it supports.

What we found

  • About 10% of integrations can create and remove users. 837 of 8,430 support both. The other 7,593 cannot complete a joiner and a leaver through the catalog integration.
  • 68 integrations can create a user but cannot remove one. 905 support create, 837 support deactivate. Those 68 automate the hire and leave the termination to a ticket.
  • 59% offer password vaulting only. 4,999 integrations use Secure Web Authentication, where Okta stores a password and fills it in. Only 2,789, or 33%, federate sign in with SAML or OIDC.
  • About 1% are HR sources. 92 integrations can act as the system of record that tells Okta who was hired, moved or let go.

Why provisioning is the number that matters

Sign in gets the attention, because people see it every day. Provisioning is where risk hides. When an app cannot deactivate a user automatically, a termination in HR becomes a ticket, then a task for an app owner, then a hope that nobody missed one. The account stays live until someone finds it.

Our count says that for nine in ten catalog integrations, that manual step is the default. For business systems with no listing at all, there is no catalog integration to start from.

Why so few apps support SCIM

SCIM is an open standard, and it is not hard to describe. The gap comes from two places.

  1. Vendors sell it as a premium feature. Many apps include SCIM only on their top plan, charged on every seat. We call that the SCIM tax. It turns a security control into an upsell.
  2. Many apps were never built for it. Desktop clients, vendor portals and older platforms have no API to build SCIM on. Their vendors have no plan to add one.

Neither reason is going away soon. Waiting for every vendor to ship SCIM is not a plan.

What this means for your stack

Start with three questions about each app you use.

  1. Does its catalog integration support both create and deactivate on the plan you have today?
  2. If not, does the vendor sell SCIM on a higher plan, and what would that upgrade cost across your seats?
  3. If no plan offers it, who removes access today, and how would you prove it to an auditor?

The SCIM tax calculator answers the second question for your headcount. Our provisioning guide walks through all three.

How StitchOps closes the gap

StitchOps carries the joiner, mover and leaver events your identity provider already sends, whether that is Okta, Microsoft Entra ID or Google Workspace, into the apps that cannot receive them, anywhere a person can log in and act. We use the app's API when it has one and its own interface when it does not. Every change is logged with evidence. Your identity provider stays the source of truth for who has access.

That works for the HR system too. HR Source connects any HR system to Okta, with or without an API, so hires, moves and terminations start the lifecycle automatically.

Method

  • Catalog. We reviewed the public catalog at okta.com/integrations on November 17, 2026 and recorded the capabilities each listing declares: SAML or OIDC, Secure Web Authentication, provisioning create, provisioning deactivate, and HR source.
  • Coverage. New listings appear every week, and any single review can miss a listing or two. Check the live catalog for any one app before you decide.
  • Limits. A listing describes what an integration supports, not which plan of the app includes it. An app can list SCIM and still charge for it. Counts change as Okta adds listings, so we repeat the review every month and update this page.

Want these numbers for your own app list? Send it to us and we will return your coverage, app by app.

Frequently asked questions

How many integrations are in the Okta Integration Network?
Our review of the public catalog on November 17, 2026 counted 8,430 integrations in the Okta Integration Network catalog.
How many Okta integrations support automated provisioning?
837 of 8,430, or about 10%, support both creating and deactivating users. The other 90% cannot complete a joiner and a leaver automatically through the catalog integration.
How many Okta integrations support SAML or OIDC sign in?
2,789, or 33%. Another 4,999, or 59%, offer only Secure Web Authentication, where Okta stores and fills in a password instead of federating the sign in.
How many HR systems can act as a source for Okta?
92 integrations in the catalog are HR sources, about 1% of the catalog. Many HR and payroll systems used by mid market companies are not among them.
How was this data collected?
StitchOps reviewed the public Okta Integration Network catalog on November 17, 2026 and counted the capabilities each listing declares. We repeat the review monthly. Listings describe what the integration supports, not what a given plan of the app includes.
What can I do about apps that cannot provision users?
StitchOps carries your identity provider's joiner, mover and leaver events into apps without SCIM or an API, anywhere a person can log in and act, on the plan you already have.

Okta and the Okta Integration Network are trademarks of Okta, Inc. Counts come from StitchOps' review of the public catalog at okta.com/integrations on November 17, 2026. This study is independent and does not imply endorsement by Okta.

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.