Which IGA platforms handle apps without SCIM? One Identity, Omada, ObserveID, SailPoint, Okta, Saviynt and Iden compared

How 7 IGA platforms handle an app with no SCIM and no API: what their connector counts measure, who builds missing connectors, Workday and SAP depth, and price.

Pranay Yadav16 minmin readUpdated

One Identity, Omada and ObserveID can't be compared on connector counts, because each one counts something different: about 110 named targets, about 150 packages with community ones included, and anywhere from 100 to 500+ with no public catalogue. What decides the purchase is what happens to an app with no SCIM and no API. One Identity and Omada fall back to a ticket, a task or a CSV file unless you script the app yourself, and ObserveID runs RPA bots it publishes no conditions for. SailPoint, Okta and Saviynt, the platforms most buyers already know, are compared alongside them, with Iden.

Quick answer:

  • Connector counts: none compare cleanly. Count only connectors that provision and confirm each change, are built by the vendor and are included in the price.
  • One Identity: a ServiceNow ticket or a custom target system you script. It documents connectors for SAP and for the RACF, ACF2 and Top Secret mainframes.
  • Omada: an emailed manual task, a full-import CSV or a relayed ticket. It can run in your own Azure tenant.
  • ObserveID: RPA bots in the app's interface, with no published sign-in conditions and no public catalogue to check.
  • SailPoint, Okta and Saviynt: SailPoint records web steps for apps with a local login and no MFA. Okta and Saviynt lean on partner products such as Cerby.
  • Iden: every SCIM app by default, plus 220+ non-SCIM connectors, built and maintained by Iden and included in the price.

How do the 7 platforms compare on connectors?

PlatformPublished countApp with no SCIM or APISign-in needsCustom connectors built by
One IdentityAbout 110 named targetsServiceNow ticket or scripted custom targetNot publishedCustomer or integrator
OmadaAbout 150 packages, community ones includedManual task, CSV or relayed ticketNot applicable, a person actsCustomer or Omada services
ObserveIDNo public catalogue, claims 100 to 500+RPA botsNot publishedCustomer, on its API Framework
SailPoint546 listed, in 3 tiersTicket, recorded web steps or RPARecorded steps: local login, no MFA or SSOCustomer or SailPoint services
Okta Identity GovernanceAbout 970 for lifecycle managementCSV, ticket or separate Cerby productNone for CSV or tickets; Cerby unpublishedCustomer; Okta free for OpenAPI SaaS apps
Saviynt119 Saviynt-built and included, of 445Ticket, or paid partner connectorsNot publishedCustomer or partners
IdenEvery SCIM app by default, plus 220+ non-SCIMConnector drives the admin consoleYour admin credentials, encrypted; no MFA sharingIden: 12 hours API, 48 hours others

Published count is what each vendor's catalogue lists, and sign-in needs are the conditions it publishes for automating an app. Every entry comes from the vendor's own pages, checked 10 to 14 November 2026, with sources linked below.

What does each vendor's connector count measure?

Each count measures something different, so no two can be lined up:

  1. One Identity. Its datasheet promises "hundreds of cloud connectors". Its integrations page names about 70 Starling Connect cloud connectors and about 40 on-premises integrations, including the RACF, ACF2 and Top Secret mainframes.
  2. Omada. It claims "support for hundreds of connectors". Its public directory lists about 150 packages from "Omada and our community", and its documentation says those packages "require further customizations depending on your configuration and needs".
  3. ObserveID. Founded in 2021, it gives 4 different figures across its own pages: over 100 on its Microsoft Marketplace listing, 250+ on its platform page, "several hundred" in its FAQ and 500+ "one-click integrations" on its home page. There's no public catalogue to check them against.
  4. SailPoint. Its catalogue page opens with "hundreds of connectors and integrations" and lists 546, in 3 tiers: Discovery, Quick Compliance and Deep Governance. Only Deep Governance connectors provision changes. SailPoint's marketing still cites "over 1,100", from a June 2024 press release that counts enterprise applications, not connectors.
  5. Okta. It lists "more than 8,000" integrations, of which about 970 carry the Lifecycle Management tag. Most of the rest are sign-in integrations, which don't provision at all.
  6. Saviynt. Its Exchange listed 445 apps when checked in November 2026, 119 of them Saviynt-built. Saviynt-built connectors are included in the subscription, and partner-built ones "are sold separately in the Saviynt Exchange".

Which connector count should you ask for?

Ask for a narrower count. It covers only connectors that:

  • create, change and remove accounts and in-app permissions, and check the app afterwards to confirm each change took effect
  • are built and maintained by the vendor
  • are included in the price

Against that test:

  • One Identity, Omada, ObserveID and Okta: none of them publishes the count.
  • SailPoint: its catalogue can be filtered to the Deep Governance connectors, the ones that provision, but it doesn't say whether they're included in the price.
  • Saviynt: it lists 119 Saviynt-built connectors included in the subscription, but doesn't say whether they confirm changes in the app.
  • Iden: it supports every SCIM app by default, and its 220+ connectors for apps without SCIM meet all 3 tests: Iden-built and maintained, confirmed in the app, and included in the price.

The SCIM-only vs universal coverage post explains why the apps outside SCIM matter most.

What happens to an app with no SCIM and no API?

There are 3 routes. A person makes the change from a ticket, a task or a CSV file, and One Identity, Omada, SailPoint, Okta and Saviynt all document this one. A partner product makes it, as Cerby does for Okta and Cerby or Torch for Saviynt. Or the vendor's own software makes it in the app's interface, as SailPoint and ObserveID document. Ask which route a demo is showing you.

  1. One Identity. A request that needs "manual fulfillment" goes to ServiceNow as a ticket. To automate the app instead, you map a "custom target system" and script it with the PowerShell or CSV connector, and its own guide says "extensive customization is required".
  2. Omada. It creates a manual provisioning task and emails the person responsible, who confirms it in Omada when it's done. It also imports flat-file CSVs, with full imports only: each file replaces the last, and there are no deltas. Its relay connectors open a ServiceNow or generic REST ticket.
  3. ObserveID. It runs RPA bots that "login, and perform tasks" in legacy interfaces, through what it calls its Universal Connector Framework. It doesn't publish any conditions for them.
  4. SailPoint. It turns a provisioning action into a ServiceNow ticket through its Service Desk integration, which needs its own SailPoint licence. Its RPA connector runs create, update, delete, enable, disable and entitlement changes as workflows in your own UiPath or Automation Anywhere cloud account, licensed from those vendors, and SailPoint doesn't list a sign-in condition for it.
  5. Okta. It imports a CSV of users and entitlements for disconnected apps, again full imports only, and can hand an access request to Jira or ServiceNow through Workflows. Cerby, a separate product on the Okta Integration Network, imports users and entitlements from disconnected apps into Okta Identity Governance, provisions new users in them and removes access directly in the app.
  6. Saviynt. It lists a Saviynt-built ServiceNow ticketing integration on its Exchange. Partner connectors for disconnected apps come from Cerby and Torch, among others, priced on their own.

Which vendors automate the app's own interface, and how do they sign in?

SailPoint and ObserveID both document their own software making the change in the app's interface. Only SailPoint publishes what that software needs to sign in.

SailPoint's Disconnected Application Connector, on Identity Security Cloud:

ObserveID's bots log in to legacy interfaces, and ObserveID publishes no sign-in conditions for them. Saviynt says a "computer-user agent (CUA) that navigates application interfaces directly" can "accelerate integration", without saying whether the agent builds the integration or makes each change.

What does each route leave you to prove?

A ticket or a task leaves a person to make the change, and the record is that person's confirmation. Omada is careful here. After the provisioner confirms a manual task, it marks the assignment as unconfirmed, because "the system has not confirmed the actual state itself".

That separates "a person says so" from "the app says so", and it's the line an auditor will draw. A full-import CSV is only as current as the last file, so proof that a leaver is gone won't exist until the next one arrives.

Automation changes the account in the app itself, but it has to sign in to do that. Ask what it needs. Of SailPoint's recorded-steps connector and ObserveID's bots, only SailPoint publishes that condition.

Who builds a connector the catalogue doesn't have?

Usually you, a partner or the vendor's paid services. Of the 6 vendors compared with Iden, only Okta builds one free.

  1. One Identity. The customer or an integrator. Its guide says provisioning to a custom target system "must be customized because each custom target system maps the data differently", using its Synchronization Editor and its PowerShell, CSV and database connectors.
  2. Omada. The customer or Omada's services team, configuring its generic REST, SQL, LDAP, SOAP, SSH and PowerShell connectors. Its Connectivity SDK "should not be used for new implementations" because it's being deprecated.
  3. ObserveID. The customer, on an API Framework that "uses .Net, C#, API, and SCIM methodology".
  4. SailPoint. The customer on its connector framework, or SailPoint's professional services for application onboarding. Its cloud runtime for custom connectors can't reach intranet-only services, JDBC or mainframes, which go through its virtual-appliance connectors instead.
  5. Okta. The customer, or Okta at no extra cost, starting November 2026. The offer covers new SaaS integrations for Okta's commercial customers, built from an OpenAPI specification that's publicly available or that the customer shares with Okta. The connector is ready for sandbox testing "in as little as 48 hours".
  6. Saviynt. The customer, on its generic REST, SOAP, database, LDAP and PowerShell connectors, or a partner's connector, paid for on top.

Which vendor goes deepest on Workday and SAP?

Workday and SAP aren't disconnected apps, so the difference here is depth: which objects each vendor can read, write and govern. SailPoint documents Workday in the most detail, and One Identity, Omada, SailPoint and Saviynt all document SAP role assignment.

VendorWrites back to WorkdayGoverns Workday security groupsAssigns and removes SAP roles
One IdentityPhone, mobile and default emailNot documentedYes, SAP-certified connector
OmadaIDs and contacts via SOAP; REST read-onlyNot documentedYes, SAP-certified connector
ObserveIDNot documentedNot documentedNot documented
SailPointContact fields, custom attributes, IDs, usernameYes, via Workday Accounts connectorYes, plus profiles and user groups
OktaEmail and phoneNo; imports provisioning groups onlyRoles on SAP NetWeaver ABAP
SaviyntNot public; docs need customer loginYes, per its solution briefYes
IdenOn requestOn request, as deep as Workday allowsOn request, as deep as SAP allows

Sources by vendor:

What do the platforms cost, and how long do they take to deploy?

Of the 6 other vendors, only Okta publishes a per-user price, and One Identity and SailPoint publish neither a price nor a timeline.

VendorPublished pricePublished timelineRuns on
One IdentityNoneNoneSelf-managed, or On Demand SaaS
OmadaNone12-week Accelerator packageSaaS, or Private in your Azure
ObserveID5-5-5 offer, price stated two ways5 prebuilt apps in 5 weeksAzure SaaS or private cloud
SailPointNoneNoneSaaS, or IdentityIQ on-premises
Okta$17 per user per month, $1,500 minimumAbout 25% deployed within 30 daysSaaS
SaviyntNoneValue in under 12 weeksSaviynt Identity Cloud
IdenFrom $7.50 per user per month, volume discountsDeploys in daysFully self-hosted, or SaaS with EU hosting

Sources by vendor:

For the full cost picture, including services and connector fees, see IGA pricing in 2026.

What changed at One Identity, Omada and SailPoint in 2026?

Which platform fits which situation?

  • Mainframe targets (RACF, ACF2, Top Secret): One Identity and SailPoint both document connectors for all 3 (RACF, ACF2, Top Secret). Iden builds custom mainframe connectors on request.
  • The platform has to run in your own Azure tenant: Omada Identity Cloud Private.
  • Deep Workday governance, security groups included: SailPoint, through its Workday and Workday Accounts connectors.
  • Already on Okta: Okta Identity Governance, with Cerby for disconnected apps. Or Iden, which provisions the Okta account and its groups as one of its targets and covers disconnected apps with its own connectors, so there's no second product to buy.
  • Many apps without SCIM or an API, and no one to build connectors: Iden builds the ones it doesn't have, at no extra cost.
  • A stack that's already mostly SCIM: any of the vendors above will cover it.

How does Iden handle apps without SCIM?

Iden takes joiners, movers and leavers from your HR system and changes access in every target app, Okta or Entra ID included.

  1. Joiner, mover and leaver. Iden recomputes each person's access whenever the HR record changes. An app with no SCIM and no API gets a connector that drives the admin console the way an administrator would, and the change goes into the same queue and audit record as a SCIM call.
  2. Access requests. Iden automates access requests across every app it governs, from the request through approval to the change in the app.
  3. Sign-in. You connect each app with your own admin credentials, which Iden keeps encrypted at rest with AES-256, in access-restricted systems, under your admin's control. Iden doesn't store your users' own login credentials and never asks you to share an MFA device or a one-time code, so ask it to connect one of your MFA-protected apps live in the demo.
  4. New connectors. Iden starts a new connector with a service account you create. Once it works, you can retire that account and connect the app under an admin identity you choose, secured the same way and yours to rotate or retire.
  5. Who builds and maintains it. Iden builds connectors it doesn't have yet at no extra cost: API connectors within 12 hours, from docs such as a Postman collection or an OpenAPI spec, and connectors for apps with no API within 48 hours. Every connector is fully managed. When an app's screens change, Iden repairs the connector, and there's no custom script on your side to maintain.
  6. Cost and count. Iden supports every SCIM app by default, plus 220+ non-SCIM connectors, all of them meeting the 3 tests above, from $7.50 per user per month with volume discounts. Iden provisions any app that supports SCIM out of the box.

Iden is SOC 2 Type II and ISO 27001 certified and GDPR compliant, with no FedRAMP yet. It's built for companies of 50 to 2,000 people and fits 500 to 5,000 well. Before the 2-week trial, check your app list against Iden's connector catalogue.

What should you ask in every demo?

Bring 3 apps from your own stack:

  1. One with SCIM on your plan.
  2. One with an API but no SCIM.
  3. One with neither, behind your SSO and MFA.

Then ask each vendor to:

  1. Show a joiner, a role change and a leaver on all 3, and show the app's own record afterwards.
  2. Show whether it reconciles after a manual task, checking the app itself rather than trusting the task's confirmation.
  3. Say what the automation needs to sign in to the third app.
  4. Say who built each connector, and who maintains it when the app changes.
  5. Say what each connector costs, and whether it's in the subscription.
  6. Give the count of connectors that provision, are vendor-built and are included in the price, against your own app list.

Questions teams ask

No IGA vendor's connector count compares cleanly with another's. SailPoint's catalogue lists 546 entries across 3 tiers, and only one tier provisions. Okta lists more than 8,000 integrations, about 970 of them for lifecycle management. Count only connectors that provision, are vendor-maintained and are included in the price.

SailPoint has the most routes: a ServiceNow ticket, recorded web steps for apps with a local login and no MFA or SSO and RPA in your own UiPath or Automation Anywhere account. One Identity sends those apps to a ServiceNow ticket or a custom target system you script. Okta imports a CSV, hands off to a ticket, or uses Cerby.

Omada falls back to a manual task, a CSV import or a relayed ticket. The manual task is emailed to the person responsible, and after they confirm it, Omada still marks the access as unconfirmed, because it hasn't checked the app itself.

No. ObserveID gives 4 different figures across its own pages, from over 100 on its Microsoft Marketplace listing to 500+ one-click integrations on its home page, and there's no public catalogue to check them against. Ask it for the connectors that provision your own apps, and what its RPA bots need to sign in.

SailPoint documents more Workday depth than Saviynt. It reads pre-hire and rescinded hire records, writes back contact fields, custom attributes and IDs, and manages security groups through a separate Workday Accounts connector. Saviynt's Workday brief lists security group provisioning, but its connector documentation needs a customer login.

Custom IGA connectors are usually built by the customer, a partner or the vendor's paid services. Okta builds new SaaS connectors free for its commercial customers, from an OpenAPI spec that's public or shared by the customer. Iden builds connectors it doesn't have yet at no extra cost, within 12 hours for an API and 48 hours otherwise.

One Identity and SailPoint both document connectors for all 3 mainframe security systems: RACF, ACF2 and Top Secret. Iden builds custom mainframe connectors on request. For any other vendor, ask for the connector documentation before the demo rather than relying on a catalogue entry.

Of the platforms compared here, Okta and Iden publish a per-user price. Okta's Essentials suite is $17 per user per month, billed annually with a $1,500 minimum. Iden starts from $7.50 per user per month, with volume discounts and every connector included. ObserveID publishes a 5-5-5 offer, and the others publish no price.

See Iden on your own stack.

In 25 minutes, on your own apps and identity provider, we’ll show which ones Iden governs end to end, including the ones without SCIM.

Read next