Skip to content

Chapter 6 of 715 min readBy Deepak GuptaUpdated

Passkey Solutions Compared: The 2026 Vendor Landscape

Viable passwordless platforms are no longer scarce. The harder question is which one fits your architecture, compliance posture and user base. Chapter 5 laid out an eight-dimension evaluation framework. This chapter applies it to the vendor landscape as of November 2026. It profiles the leading options, compares them side by side, and walks through selection logic for different organizations.

Every vendor fact here was checked against the vendor's own pricing page or documentation in early November 2026. Pricing in this market changes often, so confirm current terms before you sign. For side-by-side profiles that are kept up to date, use the CIAM Compass vendor directory. If your problem is customer login rather than workforce sign-in, also read the vendor chapter of my 2026 Passwordless Playbook for Brands.

The 2026 Market Reality

MarketsandMarkets sizes the CIAM market at $14.12 billion in 2025, and passwordless has moved from an emerging capability to a core requirement. Three forces are shaping vendor strategies:

NIST now accepts synced passkeys. The final NIST SP 800-63B-4, published in 2025, allows syncable authenticators up to AAL2 (NIST's multi-factor assurance level), provided the sync account is itself protected by MFA. Regulated industries that hesitated over synced passkeys now have a clear federal reference point.

Platforms are making passkeys the default. Microsoft Entra ID began auto-enabling passkeys for users who rely on SMS or voice on September 1, 2026. It retires Microsoft-provided SMS and voice MFA for most users on February 1, 2027. On the consumer side, the FIDO Passkey Index found that 36% of successful sign-ins at 15 large services now use a passkey.

Post-quantum planning has started. NIST finalized ML-DSA, its main post-quantum signature standard, in August 2024. No major platform ships post-quantum passkeys yet, so the practical question for buyers is crypto-agility: can the vendor swap algorithms without forcing users to re-enroll? Chapter 7 covers the timeline.

Solution Profiles

MojoAuth: Passwordless-First CIAM

MojoAuth is a passwordless-first CIAM platform built for consumer apps. Its documentation lists magic links, email OTP, SMS OTP, passkeys, WebAuthn and social login through one API. It can act as an OIDC or SAML identity provider for your apps, and as a service provider to enterprise IdPs such as Okta and Microsoft Entra ID.

Passkeys and adaptive MFA. Passkeys are a primary factor, not a second step bolted onto a password. The FAQ also describes step-up authentication with risk-based, transaction-based, time-based and location-based triggers.

Pricing. Per MAU, per its pricing page. The Free plan covers core passwordless methods (magic links and email OTP) for up to 25,000 MAU. Passkeys, phone OTP and authenticator-app TOTP start on Business Pro, which ranges from $150 a month at 2,500 MAU to $4,800 at 100,000 MAU. Adaptive MFA and WhatsApp OTP are on Enterprise.

Data minimization. On Enterprise, MojoShield Zero-Store is an opt-in, per-project setting that keeps users' personal data off MojoAuth's servers. Enterprise also lists SOC 2 Type II, ISO 27001 and a HIPAA BAA.

Where it falls short. It has a smaller ecosystem than the largest platforms, and B2B features such as organization hierarchies and delegated administration are less mature than Auth0's.

Tip

If you are building a new consumer application and want passkeys from day one with predictable pricing, MojoAuth belongs on your shortlist. Price your 36-month MAU forecast on Business Pro, since that is where passkeys start.

For head-to-heads, see MojoAuth vs Auth0 and MojoAuth vs Stytch.

Auth0 (Okta): The Ecosystem Leader

Okta completed its acquisition of Auth0 in May 2021, and has also sold the product as Okta Customer Identity Cloud since 2022. It has the broadest ecosystem in customer identity: Actions for custom logic, Universal Login, enterprise SSO and a large integration marketplace.

Passkeys. The pricing page marks passkeys as included on the B2C Free plan, so you can test the full flow before paying.

Pricing. Free covers 25,000 MAU on both B2C and B2B. Paid B2C plans start at $35 a month (Essentials) and $240 a month (Professional). Enterprise pricing is custom. Enterprise connections and B2B features climb with the tier, so a B2B product that needs many SSO connections can see costs rise quickly.

Where it falls short. Cost rises steeply past the free tier, and many enterprise features sit on higher tiers. Like every WebAuthn deployment, changing your relying party domain after enrollment invalidates existing passkeys.

Warning

Passkeys are bound to your relying party ID, usually your domain. If you change domains after users have enrolled, those passkeys stop working. This is how WebAuthn works, not a vendor limitation. Settle your domain strategy before you enroll your first passkey, and never let a vendor's hosted domain become the relying party.

See Auth0 vs Stytch and Auth0 vs Entra External ID for comparisons.

Stytch (Twilio): Developer-First CIAM

Stytch is a developer-first CIAM API with separate Consumer and B2B products covering passkeys, magic links, OTP, organizations, SSO and SCIM. Twilio announced the acquisition on October 30, 2025, and Stytch's changelog confirms the deal closed on November 14, 2025. Evaluate it as a Twilio product, not a standalone startup.

Passkeys. Stytch implements passkeys on its WebAuthn endpoints, with device-bound and synced passkeys and cross-device sign-in by QR code. It also sells device fingerprinting for fraud and bot signals.

Pricing. The pricing page lists 10,000 monthly active users and AI agents free on both Consumer and B2B, with pay-as-you-go above that. Five SSO or SCIM connections are included, then $125 each.

Where it falls short. The roadmap and contract terms after the acquisition are the open question. The CIAM Compass changelog entry tracks what the deal means for buyers.

Microsoft Entra ID: Workforce Passkeys at Microsoft Scale

For workforce sign-in in a Microsoft environment, Entra ID is the default choice, and in 2026 it made passkeys the default too. It supports synced passkeys and device-bound passkeys, including passkeys in Microsoft Authenticator and FIDO2 security keys, alongside Windows Hello for Business.

Policy depth. Conditional Access can require phishing-resistant methods for specific apps, groups and risk levels. Microsoft publishes guidance on configuring Entra ID to meet FedRAMP High identification and authentication controls, where FIDO2 security keys serve AAL3 scenarios.

The 2026 to 2027 timeline. From September 1, 2026, users enabled for SMS or voice are auto-enabled for passkeys and nudged to register. From February 1, 2027, Microsoft-provided SMS and voice MFA is retired for most users, and anyone whose only method is SMS or voice must register a passkey to sign in. Global Administrators and external users follow on July 1, 2027. Organizations with a regulated need for SMS can contract a telephony provider through Microsoft Security Store.

Where it falls short. The value drops outside the Microsoft ecosystem, and the admin experience assumes Microsoft tooling expertise.

Microsoft Entra External ID: Microsoft's Customer Identity Service

Entra External ID is a separate product from workforce Entra ID. It is Microsoft's customer identity service and the successor for Azure AD B2C, which stopped selling to new customers on May 1, 2025. Do not assume workforce features carry over.

Passkeys. Passkeys work for passwordless sign-in and as MFA in external tenants, per Microsoft Learn, at no extra cost. The limits matter for a passwordless-first plan:

  • Only email and password, or username and password, accounts can register a passkey.
  • Users must complete MFA before registering one.
  • There is no built-in registration screen; you build one with the credential management API.
  • Passkeys cannot yet be required by policy, and are not supported in native authentication flows.
  • Passkeys are not available in Azure AD B2C.

The SMS and voice retirement above does not yet apply to External ID tenants. Microsoft's FAQ says that change comes next year, with a separate announcement, and that Azure AD B2C is out of scope.

Pricing. The Entra pricing page gives the first 50,000 MAU free, then pay-as-you-go through an Azure subscription.

For the cloud alternatives side by side, see Cognito vs Entra External ID.

HYPR: Workforce Passwordless and Identity Assurance

HYPR sells passwordless MFA for the workforce, combined with risk policy and identity verification. Its platform pages describe FIDO-certified components and integrations with Okta, Entra ID, Ping Identity and RADIUS infrastructure, so it usually works alongside your current identity provider rather than replacing it.

Target audience. Large regulated enterprises, financial services, healthcare and critical infrastructure organizations that want phishing-resistant sign-in across desktops, VPN and SSO.

Where it falls short. It is sold through an enterprise sales process with implementation support. That suits large organizations with security teams, not a startup adding passkeys to a product over a weekend.

Yubico YubiKey: The Hardware Standard

YubiKey is not a software platform. It is the reference hardware for phishing-resistant authentication. A YubiKey stores private keys in tamper-resistant hardware, and those keys cannot be exported or copied. That non-exportability is what lets a hardware key meet NIST AAL3, which synced passkeys cannot.

Protocol support. FIDO2/WebAuthn, FIDO U2F (legacy), PIV for enterprise PKI, OATH for TOTP and HOTP, and OpenPGP for email and code signing, all from one device.

Pricing. The Yubico US store lists the YubiKey 5 NFC and YubiKey 5C NFC at $58 each, with volume pricing for enterprises.

Where it falls short. Hardware distribution logistics are real, and lost-key replacement needs a defined process. YubiKeys are also impractical for consumer applications, where you cannot require users to buy a device. Recovery design becomes critical: if a user loses their only key, you need a secure fallback that does not undo the security you built.

Note

YubiKeys complement software passkeys rather than competing with them. Strong deployments pair synced passkeys for everyday sign-in with hardware keys for privileged access and recovery verification. Consider YubiKeys for your admin tier even if the general workforce uses synced passkeys.

Additional Players Worth Watching

Corbado is a passkey adoption layer that runs on top of your existing identity provider, with managed passkey journeys and analytics. It suits large consumer brands whose passkey enrollment has stalled. Its pricing is custom.

Hanko is an open-source, passkey-first authentication server; the backend is AGPL-3.0, per its GitHub repository. Hanko Cloud is free up to 10,000 MAU. See Hanko vs Corbado.

Clerk offers drop-in sign-in components for React and Next.js. Passkeys and MFA start on its Pro plan at $25 a month, per its pricing page.

Amazon Cognito includes passkey sign-in on its Essentials and Plus tiers, per the Cognito pricing page. Essentials is free to 10,000 MAU. See Auth0 vs Cognito.

Beyond Identity focuses on phishing-resistant workforce authentication tied to device security posture. Its CIAM Compass profile has the details.

Cisco Duo provides workforce MFA and passwordless sign-in with strong endpoint and VPN integration. It is a natural fit for organizations already on Cisco networking.

Head-to-Head Comparison

Dimension MojoAuth Auth0 (Okta) Stytch (Twilio) Entra ID (workforce) Entra External ID YubiKey
Primary use Customer Customer, B2B Customer, B2B Workforce Customer Hardware factor
Passkeys Primary factor, from Business Pro Included on Free Native Default from Sept 2026 Available, with limits Device-bound by design
Magic links / OTP Email, SMS, WhatsApp (Enterprise) Email, SMS Email, SMS SMS and voice retiring Feb 2027 Email OTP, SMS OATH TOTP
Can reach NIST AAL3 Not documented Not documented Not documented Yes, with FIDO2 security keys Not documented Yes
Free tier 25,000 MAU 25,000 MAU 10,000 MAU and agents Included with Entra ID licenses 50,000 MAU None (about $58 per key)
Pricing model MAU MAU Usage Per user license MAU via Azure Per unit

"Not documented" means the vendor's public documentation did not settle it when I checked. Ask in the demo.

Selection Criteria: Enterprise vs. Startup

The right solution depends less on feature count and more on which platform fits your organization. Here is a decision framework for common scenarios.

For Startups and Early-Stage SaaS

Priority: fast integration, low initial cost, developer experience and predictable pricing as you grow.

Suggested evaluation order: MojoAuth, Stytch, Clerk, Auth0 (free tier).

MojoAuth's free tier and unified API make it a fast path to production passwordless sign-in, though passkeys start on its paid plan. Stytch is a strong alternative if you also need B2B organizations, SSO or device fingerprinting. Clerk fits teams that want prebuilt React components. Auth0's free tier covers 25,000 MAU with passkeys included, but costs can climb quickly once you cross tier boundaries or need enterprise SSO.

For Mid-Market B2B SaaS

Priority: enterprise SSO support, organization management, compliance certifications and multi-tenant architecture.

Suggested evaluation order: Auth0, Stytch, MojoAuth (Enterprise).

At this stage, you likely need SAML SSO for enterprise customers, SCIM directory sync and organization-level policy. Auth0's ecosystem breadth is hard to match, but model the total cost carefully, because per-connection SSO pricing adds up when every enterprise customer needs one. Stytch's included connections and MojoAuth's Enterprise tier are alternatives if Auth0's pricing becomes a budget problem. An SSO layering tool such as SSOJet can also add enterprise SSO without replacing your core identity provider.

For Regulated Enterprises

Priority: compliance certifications, NIST assurance levels, zero-trust architecture and complete audit trails.

Suggested evaluation order: Microsoft Entra ID (if Microsoft-centric), HYPR (if vendor-agnostic), YubiKeys (for privileged access).

If you are a US government contractor, Entra ID's FedRAMP High guidance may settle the question. If you need phishing-resistant sign-in across a mixed estate, HYPR is built for that. Add YubiKeys for privileged access that requires AAL3.

For Consumer Applications

Priority: user experience, conversion, OTP channel coverage and cost per authentication.

Suggested evaluation order: MojoAuth, Auth0, Corbado (if you already have a CIAM and adoption has stalled).

Consumer applications need broad channel support because you cannot dictate your users' devices. MojoAuth's WhatsApp OTP, available on Enterprise, matters for apps serving markets where WhatsApp is the dominant messaging channel. Corbado is the option when the problem is adoption on an existing CIAM rather than the CIAM itself.

Tip

Do not select a vendor on feature count alone. The vendor with the most features is often the vendor with the most complexity. A focused platform that does exactly what you need will beat a feature-rich platform that takes six months to configure.

Integration Complexity and Migration Paths

Greenfield Integration

For a new application, integration effort depends mostly on SDK quality and documentation. MojoAuth and Stytch both offer unified APIs that put several authentication methods behind one interface. In my experience, basic passkey sign-in is a matter of days, and a production-ready deployment with fallback methods, account recovery and admin tooling takes a few weeks.

Migrating from Password-Based Authentication

Migration from an existing password-based system follows a predictable four-phase pattern, whichever vendor you choose. The timings below are my working estimates:

Phase 1, parallel deployment (weeks 1 to 4). Deploy the passwordless solution alongside your existing authentication. New registrations default to passkeys. Existing users keep their passwords but see prompts to enroll a passkey.

Phase 2, incentivized adoption (weeks 5 to 12). Increase enrollment through UX nudges, shorter sessions for password sign-ins and internal communication about the transition. Aim for a large share of active users with a passkey before moving to Phase 3.

Phase 3, password deprecation (weeks 13 to 20). Make passkeys the default. Password sign-in moves behind a "use another way" link. Watch support ticket volume for recovery problems.

Phase 4, password elimination (week 21 onward). Disable passwords for users who have enrolled passkeys. Keep a password fallback only for users who have not enrolled yet, with mandatory enrollment at next sign-in.

Warning

Never remove password authentication before you have a robust account recovery flow. The most common migration failure is removing passwords before users have enrolled a backup method, which creates a wave of locked-out accounts that swamps your support team.

Vendor Migration

Switching between passwordless vendors is harder than the first integration because of WebAuthn's relying party binding. Passkeys are bound to a relying party ID, usually your domain. If that ID stays the same and you can export the stored public keys and credential IDs, the new vendor can sometimes import them. If the relying party changes, or the old vendor cannot export credential data, users must re-enroll. Ask about credential export before you sign, plan a parallel-run period, and reuse the phased approach above.

The Bottom Line

The 2026 passwordless vendor landscape offers genuine choice across the full range of organizational needs. Accepting password fallbacks because passkey products were immature is no longer necessary. You can choose a passwordless-first CIAM (MojoAuth), the broadest ecosystem (Auth0), a developer-first API inside Twilio (Stytch), Microsoft's workforce default (Entra ID), an enterprise workforce specialist (HYPR) or hardware-bound AAL3 keys (YubiKey).

Competition between these vendors is driving rapid improvement. Passkeys that once sat on enterprise tiers now appear on free plans at some vendors. Integration is getting simpler. The best time to eliminate passwords was years ago. The second-best time is now, and the options have never been better.

For a broader comparison, see my enterprise comparison of passwordless solutions, and check current pricing in CIAM Compass before you shortlist.