IAM Solutions Compared: Choosing a Platform in 2026

Guilliano MolaireGuilliano MolaireUpdated 19 min read

IAM solutions for a B2B SaaS product split into three delivery models. The first is the full customer identity (CIAM) platform, such as Auth0, Microsoft Entra External ID or Amazon Cognito, which runs sign-up, login, tokens and enterprise federation for you. The second is the developer auth layer, such as Clerk, Stytch and WorkOS, which gives you SDKs and hosted components that sit inside your app. The third is the open source identity server, such as Keycloak, which you run yourself or hand to a managed provider. Pick the model first, because it decides what you build, what you operate and what you can take with you when you leave. Then compare the vendors inside that model on the total cost at your real user count, not on the entry tier printed at the top of the pricing page.

This guide is written for engineering and product leads shortlisting a customer identity platform. We assume you already know OpenID Connect (OIDC) and SAML, so the comparison is about pricing shape, control, lock-in and operating cost. It prices every option at the same mark of 100,000 monthly active users, with each number linked to the vendor’s own pricing page as it read on 28 October 2026, and it names the switching cost of each option. There is a short section on workforce IAM tools near the end for readers who arrived looking for staff sign-in rather than customer sign-in. For the hosting view of the same decision (multi-tenant service, self-hosted or managed dedicated), see Cloud Identity Management: How to Choose a Cloud IAM Solution.

Key Takeaways

  • Full CIAM platforms (Auth0, Entra External ID, Cognito) bill per monthly active user above a free allowance, and Auth0’s published price list stops at 50,000 MAU on B2C plans and 20,000 MAU on B2B plans, so 100,000 users means a sales conversation.
  • Developer auth layers (Clerk, Stytch, WorkOS) are cheaper per user but add a per-connection fee for each enterprise customer’s SSO or SCIM link, which is the meter that grows for a B2B product.
  • Open source identity servers (Keycloak, FusionAuth Community) have no per-user fee, and managed Keycloak on Skycloak is a plan price per cluster with unlimited users, so the bill follows infrastructure rather than growth.
  • Switching cost is where the models differ most: a standards-based server exports a realm file with its users, while most hosted platforms make you ask for your password hashes.

What are the three delivery models for IAM solutions?

Identity and access management solutions, also sold as IAM tools or identity platforms, give verified users access to applications and data, as Microsoft’s IAM explainer (2026) puts it. That definition covers both staff signing in to company tools and customers signing in to the product you sell. This post is about the second case, customer identity, and for that case the useful first cut is not the vendor’s brand but how the product is delivered to you.

A few terms come up throughout. OIDC and SAML are the two open sign-in protocols every product in this post supports. SCIM, the System for Cross-domain Identity Management, is the standard for creating, updating and removing user accounts in another system automatically (RFC 7644), which matters the first time a customer asks for their directory to manage access to your product. MAU means monthly active users, and the exact definition varies: Auth0 counts any non-internal user who authenticated during the month, while Clerk bills on a monthly retained user, which it defines as a user who visits your app at least one day after signing up.

Delivery model What the vendor runs What you build and run Examples Usual pricing unit
Full CIAM platform Hosted login, sign-up, tokens, MFA, social and enterprise federation, user store Your app’s integration over OIDC or SAML, plus any vendor-specific extension code Auth0, Microsoft Entra External ID, Amazon Cognito Per MAU above a free allowance
Developer auth layer Hosted APIs and UI components for sign-in, organizations, enterprise SSO and SCIM The app itself, with the vendor’s SDK and components embedded in it Clerk, Stytch, WorkOS Per MAU or per retained user, plus a fee per enterprise connection
Open source identity server Nothing, unless you buy a managed service The server, its database, upgrades and on-call, or a managed plan that takes those over Keycloak (self-hosted or managed on Skycloak), FusionAuth Community No license; infrastructure and people, or a plan price per cluster when managed

The boundaries blur at the edges. Auth0 sells Organizations for B2B tenancy, WorkOS has a hosted login called AuthKit, and FusionAuth sells hosted plans on top of its free edition. The point of the grouping is that each model fixes a different answer to three questions: who operates the service, how much of the vendor’s code ends up inside your app, and what the meter counts. Those three answers decide the cost over three years far more than any feature matrix does.

What does each IAM solution cost at 100,000 monthly active users?

The table prices every option at 100,000 monthly active users for a product that signs in its own customers, using the public prices on the linked pages as they read on 28 October 2026. Where a vendor’s published list stops below that mark, the table says so rather than guessing. Add-ons, SMS, machine-to-machine tokens and support tiers are extra on every hosted product, so treat these as the shape of the bill rather than a quote.

Solution Model Published price at 100,000 MAU What else grows the bill Switching cost
Auth0 Full CIAM platform Not published: the B2C Essentials table stops at 50,000 MAU, $3,500 per month, the B2B Essentials table at 20,000 MAU, $3,800 per month, with “Contact us” above those Enterprise SSO connections beyond the 3 included on B2B Essentials at $100 per month each; machine-to-machine token packs Actions code written against Auth0’s APIs; password hashes leave only through a support case that Auth0 reviews for eligibility
Amazon Cognito Full CIAM platform Essentials: $1,350 per month (90,000 billable MAU at $0.015 after 10,000 free); Lite: $495 per month (90,000 at $0.0055) Users federated over SAML or OIDC at $0.015 per MAU after the first 50; Plus tier at $0.020 per MAU with no free tier Lambda triggers written for Cognito; users move out through a migrate-user trigger at sign-in rather than a hash export
Microsoft Entra External ID Full CIAM platform First 50,000 MAU free; the per-MAU rate for the remaining 50,000 is shown only through Microsoft’s pricing calculator or a quote, not as a list price Premium add-ons billed on top of MAU: machine-to-machine authentication, SMS, Go-Local data residency, governance for guests Custom authentication extensions tied to the Microsoft ecosystem; an external tenant is linked to an Azure subscription
Clerk Developer auth layer About $1,025 per month on Pro: $25 base plus 50,000 retained users above the 50,000 included at $0.02 each B2B authentication add-on at $100 per month; enterprise SSO connections at $75 per month each for connections 2 to 15 Clerk’s SDK and prebuilt components are the integration surface, so leaving means replacing them in the app
Stytch Developer auth layer 10,000 MAU free on pay as you go; the per-MAU rate above that is not printed on the pricing page, so ask for the figure 5 SSO or SCIM connections included, then $125 per connection Stytch SDKs and session model inside the app
WorkOS Developer auth layer $0 for users: AuthKit includes the first 1,000,000 MAU free, then $2,500 per month per additional million Single sign-on at $125 per connection and directory sync at $125 per connection for the first 15 of each, falling to $65 each above 50; audit log streaming at $125 per month per SIEM connection AuthKit sessions and the admin portal are WorkOS-specific; the connection count is the meter to model
FusionAuth Open source identity server Community edition is free and unlimited when you self-host; hosted Starter plans start at $162 per month billed annually, Essentials and Enterprise at $2,970 per month Premium features such as breached password detection and advanced MFA sit in the paid editions Standard OIDC and SAML; your own database when self-hosted
Keycloak, self-hosted Open source identity server No license fee; you pay for servers, a database and the engineers who run it Upgrades, patching, high availability and on-call, which we cost out in What Is the Cost of Self-Hosting Keycloak? Realm export to JSON with its users; OIDC, OAuth 2.0 and SAML endpoints that any other provider also speaks
Managed Keycloak on Skycloak Open source identity server, managed A plan price per cluster with unlimited users: Developer $29, Launch $149 or Business $599 per month, Enterprise per contract A second cluster for another region or environment; the user count never changes the bill Same as self-hosted Keycloak, since it is the same software with a full realm export

Two things stand out once everything is priced at the same mark. The first is that the full CIAM platforms do not publish a price at 100,000 users at all, except Cognito, so the sticker price you saw on the pricing page is not the one you will pay. Our post on how Auth0, Okta and B2C cost scales with per-MAU pricing walks through what that curve looks like over a few years. The second is that for a B2B product the developer auth layers move the cost from users to enterprise connections, and a product with 60 enterprise customers on WorkOS is paying for 60 SSO connections and, often, 60 directory sync connections on top. Which of the two meters hurts less depends on whether your growth shows up as more end users or more enterprise logos.

Model one: full CIAM platforms

A full CIAM platform runs the whole customer login for you: the hosted sign-up and sign-in pages, social and enterprise federation, multi-factor authentication, token issuance and the user store. Your application integrates over OIDC or SAML and, in most cases, through the vendor’s extension layer for anything custom. This is the model with the least to operate and the most vendor-specific code, because the hooks that make the platform fit your product (Auth0 Actions, Cognito Lambda triggers, Entra custom authentication extensions) are written against that vendor’s API.

Auth0 publishes the clearest per-MAU curve of the three hosted platforms, and it also stops publishing earliest: the B2C Essentials table stops at 50,000 MAU, priced at $3,500 per month, and the B2B Essentials table stops at 20,000 MAU, priced at $3,800 per month (Auth0 pricing, 28 October 2026), with “Contact us” above those. B2B plans include unlimited Organizations and 3 enterprise SSO connections, with further connections at $100 per month each. On the way out, Auth0’s bulk export does not include password hashes; those come through a support case that Auth0 reviews for eligibility and that needs a signed acknowledgment form which, in the words of that page, “must be signed by a CISO, CSO, or executive-level representative (VP or above)”. Related reading: Keycloak vs Auth0: The Definitive Comparison for Developers and Top Auth0 Alternatives in 2026: Open Source and Managed Options.

Amazon Cognito is the one hosted platform with a published price at 100,000 users, and it is the cheapest of the three: $0.015 per MAU on Essentials after 10,000 free, which is $1,350 per month at 100,000 (Amazon Cognito pricing, 28 October 2026). The catch for a B2B product is that users who sign in through a customer’s directory over SAML or OIDC are billed at $0.015 per MAU after the first 50, on every tier. Cognito has no password export; the documented path for moving users is a migrate-user Lambda trigger that captures each password at sign-in, which works in reverse too and means a migration off Cognito runs for as long as it takes every user to sign in once. Related reading: Keycloak vs AWS Cognito: Which Should You Choose?.

Microsoft Entra External ID is Microsoft’s customer identity product and the successor to Azure AD B2C, which stopped being sold to new customers on 1 May 2025; our end-of-sale timeline and migration page have the detail. The first 50,000 MAU are free, which covers a lot of early-stage products, and Microsoft’s External ID pricing documentation (2026) lists premium add-ons billed on top of the basic MAU charge: machine-to-machine authentication, SMS phone authentication, Go-Local data residency, governance for guests and Global Secure Access for guests. The per-MAU rate above 50,000 is not shown as a list price on the public page; you get it from the pricing calculator or a quote.

Model two: developer auth layers

Clerk, Stytch and WorkOS sell identity as SDKs, APIs and hosted components that live inside your application rather than in front of it. That is a good fit when you want sign-in to look like part of your product and your team is comfortable owning the integration, and it is the model with the lowest entry price per user. It is also the model where enterprise readiness is sold by the connection: each business customer that brings its own identity provider is a line on the bill.

Clerk prices on monthly retained users, counting only people who come back at least one day after signing up, which flatters products with a lot of one-visit sign-ups. At 100,000 retained users on Pro the bill is about $1,025 per month, from a $25 base plus 50,000 users above the included 50,000 at $0.02 each (Clerk pricing, 28 October 2026). B2B features cost more: the enhanced B2B authentication add-on is $100 per month and enterprise SSO connections are $75 per month each for connections 2 to 15, with one included.

Stytch publishes a pay-as-you-go plan with 10,000 monthly active users free and 5 SSO or SCIM connections included, then $125 per connection (Stytch pricing, 28 October 2026). The per-MAU rate above the free allowance is not printed on the pricing page we checked, so ask for it in writing before you model a year of growth.

WorkOS is priced almost entirely on connections. AuthKit includes the first 1,000,000 MAU free, so at 100,000 users the user line is zero, while single sign-on and directory sync are each $125 per connection for the first 15, falling to $65 each above 50 (WorkOS pricing, 28 October 2026). A product with 40 enterprise customers that each want SSO and SCIM is paying for 80 connections. We compared this meter with Auth0’s in WorkOS vs Auth0: Per-Connection vs Per-MAU Pricing for B2B SaaS.

The switching cost in this model is in your codebase rather than in a data export. The vendor’s components, session handling and organization model are wired through the app, so leaving means replacing them screen by screen. That is not a reason to avoid the model, but it is a reason to keep the vendor’s SDK behind your own interface where you can.

Model three: open source identity servers, self-run or managed

Keycloak is an open source identity server that acts as an OIDC, OAuth 2.0 and SAML 2.0 identity provider, brokers logins from social and enterprise identity providers, federates LDAP and Active Directory, and, in recent releases, exposes a supported SCIM API. The Keycloak homepage (retrieved 28 October 2026) describes it as “a Cloud Native Computing Foundation incubation project” and listed 26.8.1 as the latest release on that date. It has no per-user fee, since the project README states it is licensed under the Apache License, Version 2.0, and the trade-off is that someone has to run it, which is the question our guide Is Keycloak Right for Your B2B SaaS? A Decision Guide is built around.

Four Keycloak features carry most of the B2B SaaS use case, with links to the official documentation.

Realms. The core concepts section of the Keycloak Server Administration Guide (retrieved 28 October 2026) says “a realm manages a set of users, credentials, roles, and groups” and that “realms are isolated from one another and can only manage and authenticate the users that they control”. One server can therefore hold a realm for your staff and a separate realm for your customers.

Organizations. The Organizations feature gives a realm a model for B2B tenancy, with organization domains, members, invitations and linked identity providers, so a business customer’s users can be tied to that customer’s own identity provider inside one realm. The release notes list “Organizations supported” among the Keycloak 26.0.0 highlights, and the Keycloak 26.8.0 notes say “identity providers can now be linked to multiple organizations”.

Identity brokering. The same core concepts section of the Server Administration Guide says Keycloak “can be configured to delegate authentication to one or more IDPs”, for example Google for social login or a customer’s own OIDC or SAML provider. Your applications talk to Keycloak, and a customer’s identity provider is added to the realm rather than to each application.

SCIM. The release notes describe the SCIM API as a preview feature in the Keycloak 26.7.0 highlights, and the Keycloak 26.8.0 notes say “the SCIM API is promoted from preview to supported”. The Keycloak features guide (retrieved 28 October 2026) lists scim-api in its table of supported features that are enabled by default. Comparisons written before those releases that list SCIM as a Keycloak gap are out of date.

The exit is the simplest of the three models because the server is the product. Keycloak’s import and export guide documents an export command that writes realms to JSON files, with the realm’s users written to their own files by default (the --users option controls this), and a realm exported from one Keycloak can be imported into another, self-hosted or managed. Applications written against its OIDC endpoints use a standard protocol that every other vendor in this post also speaks.

FusionAuth sits in the same model with a different licence shape: the Community edition is free and unlimited when you self-host, and the paid editions add premium features and hosting, with Starter from $162 per month billed annually and Essentials and Enterprise from $2,970 per month (FusionAuth pricing, 28 October 2026).

Managed Keycloak is for teams that want Keycloak itself, perhaps because they already run it, have extensions written for it, or need a dedicated cluster, but do not want the upgrades, patching and on-call. On Skycloak that is a dedicated Keycloak cluster per customer at a plan price per cluster, and the pricing page states that every plan includes unlimited users: Developer at $29, Launch at $149 and Business at $599 per month, with Enterprise per contract. At 100,000 users the bill is the same as at 10,000, and it grows when you add a cluster, for example for a second region, not when you add users. The pricing calculator lets you configure additional clusters, custom domains and security add-ons and see the resulting price, the managed Keycloak page covers what the service includes, and Managed Keycloak Providers Compared (2026) compares it with the other providers.

Open source, without the per-user bill

Most identity platforms charge per monthly active user and gate enterprise SSO behind an upgrade. Skycloak bills for infrastructure instead, so every plan carries unlimited users and unlimited applications, on real upstream Keycloak you can export at any time.

What about workforce IAM tools such as Okta and Entra ID?

Everything above is about customer identity: the people who use the product you sell. If you searched for IAM tools because your staff need one login for their SaaS tools, a directory and offboarding that removes access, you are shopping for workforce IAM, which is a different product with a different meter. Okta Workforce Identity is priced per user per month, at $6 for Starter, $14 for Core Essentials and $17 for Essentials, with higher suites priced on inquiry and a $1,500 annual contract minimum (Okta pricing, 28 October 2026). Microsoft Entra ID is $7 per user per month for P1, $10 for P2 and $12 for the Entra Suite, paid yearly, with a Free tier that comes with an Azure subscription (Microsoft Entra pricing, 28 October 2026). Okta also sells customer identity separately, with an Enterprise base platform at $3,000 per month billed annually.

Two things are worth knowing if you are in that aisle. A B2B SaaS company that needs both staff and customer sign-in may end up buying a workforce product and a CIAM product, since Okta and Microsoft price them separately, which is one reason teams look at a Keycloak server that holds both in separate realms. And if your real question is about administrators and service accounts rather than everyday staff, that is privileged access management, which we untangle in IAM vs PAM: Differences, Overlap and Which You Need First. For a workforce comparison with Keycloak see Keycloak vs Okta: An Honest Workforce IAM Comparison.

How do you compare vendors inside a model?

Once you have picked a model the products inside it look alike on a feature matrix, and three questions separate them.

Does the pricing unit match how you grow? A product billed per MAU charges you more as your product succeeds. A product billed per enterprise connection charges you more as you close enterprise deals. A product billed per cluster charges you more as you add environments and regions. None of these is wrong, but one of them matches your revenue model better than the others, and the IAM ROI calculator lets you put your own user count, provider and team cost side by side.

Are the standards real, and do they cover what your customers will ask for? Ask for OIDC and SAML on both sides (as the identity provider your apps trust, and as a broker that accepts a customer’s identity provider), SCIM for provisioning, and passkeys, which the final NIST SP 800-63-4 (July 2025) lists among its changes as integrating “syncable authenticators (e.g., synced passkeys)”. Asking a vendor which authentication assurance level its default configuration meets under that guideline is a quick way to find out how seriously it takes the standard.

What does leaving cost? Ask for a user export that includes password hashes, ask which of your integrations would survive a change of provider unchanged, and count the places you have written vendor-specific logic. For Keycloak the answer is a realm export and standard endpoints on the other side. For hosted platforms the answer varies, and getting it in writing before you sign is the cheapest insurance in this project. We walk through the budget lines of that exercise in What Does It Cost to Move Off Your Identity Provider?.

What should total cost of ownership include?

When you build the business case, cost out five things for each option on the shortlist over three years.

  1. Licensing or subscription. Per MAU, per connection, per cluster or per contract. Model it at today’s user count and at double, because that is the question finance will ask, and model the enterprise connection count separately if you are on a developer auth layer.
  2. Implementation and migration. Developer time for the first integration, moving existing users and their passwords, and rebuilding custom flows. Budget for porting vendor-specific code such as Actions, triggers or custom extensions.
  3. Operations. For a hosted product the vendor runs the service. For self-hosted Keycloak your team owns the upgrades, patching, database work, availability and on-call, which is the line that a managed plan takes over. Related reading: Build vs. Buy for Identity: What to Check Before You Decide.
  4. Training and change management. Who has to learn the new platform, from developers working with its APIs to support staff handling account recovery, including the people who join after launch.
  5. Opportunity cost and exit cost. Engineering hours spent on authentication are hours not spent on the product, and the vendor-specific logic you add is part of what you would have to rewrite to leave.

A short checklist to take into vendor calls:

  • The published price at your current user count and at twice that, with every add-on you expect to need, and the per-connection price if there is one.
  • The contract minimum, the billing term and the notice period.
  • OIDC, SAML and SCIM support on both the inbound and outbound side.
  • Where user data is stored, and whether you can choose the region.
  • Audit logs you can export to your own tooling (on Skycloak, see the audit logs feature, which lists SIEM export).
  • The export format for users, including password hashes, and for configuration.
  • Who is on call when it breaks, and what the response time commitment is.

Frequently asked questions

What are IAM solutions?

IAM solutions are the products that give verified people access to an organization’s applications and data (Microsoft, What is IAM, 2026). For customer identity, the products you would shortlist fall into three delivery models: full CIAM platforms, developer auth layers and open source identity servers.

Is there a difference between IAM tools and IAM solutions?

This guide treats them as the same thing. Whether a page says IAM tools, IAM solutions or identity and access management solutions, the three delivery models and the workforce section above apply.

What is the difference between workforce IAM and CIAM?

Workforce IAM manages a company’s own employees and contractors, and the workforce products in this post are priced per user per month (Okta, Microsoft). Customer identity and access management (CIAM) manages the people who use the product the company sells, and the hosted CIAM products here charge per monthly active user above a free allowance (Auth0, Cognito, Entra External ID).

Is Keycloak an IAM solution?

Yes. Keycloak is an open source identity and access management server that acts as an OpenID Connect, OAuth 2.0 and SAML 2.0 identity provider, brokers logins from external identity providers, federates LDAP and Active Directory, and, in recent releases, exposes a supported SCIM API (see the SCIM section above for the release notes). It can serve workforce and customer use cases from separate realms on one server, and you can run it yourself or use a managed Keycloak service.

Which IAM solution is cheapest at 100,000 users?

Of the options with a published price at that mark on 28 October 2026, WorkOS charges nothing for the users themselves because AuthKit includes the first million MAU, Clerk comes to about $1,025 per month on Pro, and Cognito Essentials comes to $1,350 per month. Managed Keycloak on Skycloak is a flat $149 per month on Launch or $599 on Business regardless of user count; the plan price covers one cluster on Launch and two on Business, and whether a given cluster size carries your login rate is a sizing question, which our Keycloak production sizing guide walks through. Those numbers exclude enterprise SSO and SCIM connections, which is where the developer auth layers add most of their cost for a B2B product, so the cheapest option depends on how many enterprise customers you have as much as on how many users.

How much do IAM solutions cost in general?

Published workforce list prices on 28 October 2026 run from $6 to $17 per user per month at Okta and $7 to $12 at Microsoft, billed annually. The hosted CIAM products are free up to a published limit (25,000 MAU at Auth0, 10,000 at Cognito, 50,000 at Entra External ID) and then bill on monthly active users. Self-hosted Keycloak and FusionAuth Community have no license fee but need infrastructure and people. Managed Keycloak on Skycloak is a plan price per cluster from $29 to $599 per month with no per-user fee.

What to do next

Decide which delivery model you are in, using the first table in this post, and shortlist two or three products inside it. For each one write down the price at today’s user count and at double, the per-connection price if there is one, the contract terms, the standards it supports in both directions and what an export looks like. Then put your numbers into the IAM ROI calculator, which shows annual and five-year costs for building in-house, an Auth0 or Okta estimate and a Skycloak plan.

For managed Keycloak, the managed Keycloak page and the pricing page show the plans and what each includes.

Sources

All retrieved 28 October 2026.

Open source, without the per-user bill

Most identity platforms charge per monthly active user and gate enterprise SSO behind an upgrade. Skycloak bills for infrastructure instead, so every plan carries unlimited users and unlimited applications, on real upstream Keycloak you can export at any time.

Guilliano Molaire
Written by
Founder, Skycloak

Guilliano is the founder of Skycloak and a cloud infrastructure specialist with deep expertise in product development and scaling SaaS products. He discovered Keycloak while consulting on enterprise IAM and built Skycloak to make managed Keycloak accessible to teams of every size.

© 2026 Skycloak. All Rights Reserved. Design by Yasser SolimanKeycloak™ is a trademark of the Linux Foundation. Skycloak is not affiliated with the Keycloak project.