Skip to content
Start with Identity
Report · 2026 · 12 min

Identity Developer Experience Benchmark 2026

SDKs, prebuilt passkey UI, quickstarts, OpenAPI specs, rate limits and MCP support across 28 auth platforms, scored on a published rubric

Key findings
  • 14 of 28 auth platforms (50.0%) publish an official MCP server that lets an AI agent work with your account, 7 more publish a documentation-only or limited one, and 17 (60.7%) document acting as the OAuth authorization server for your own MCP server, per vendor documentation checked November 5, 2026.
  • Only 9 of 28 auth platforms (32.1%) document OAuth 2.0 Token Exchange (RFC 8693), the standard way to let an agent or service act on behalf of a user, while 20 (71.4%) document machine-to-machine tokens.
  • 23 of 28 auth platforms (82.1%) support passkey sign-in, 17 (60.7%) ship a prebuilt passkey enrollment screen, and only 10 (35.7%) combine embeddable UI components with that screen: Auth0, Clerk, Descope, Frontegg, Ory, Stytch, SuperTokens, Hexclave, Hanko and Corbado.
  • 19 of 28 auth platforms (67.9%) publish an OpenAPI spec for their API; 9 do not, among them Amazon Cognito, Firebase Authentication, Stytch and Frontegg.
  • 18 of 28 auth platforms (64.3%) document API rate limits with numbers; among the 16 managed services, 4 (FusionAuth, PropelAuth, MojoAuth and Corbado) have no rate-limit page we could find, and 9 of 28 changelogs had no readable entry in the 90 days before the check.
  • Only 10 of 28 auth platforms (35.7%) document self-serve enterprise SSO (SAML and OIDC with a setup flow for the customer's IT admin), 15 (53.6%) document inbound SCIM, and just 2 of 28 put a time on their quickstart; counted steps range from 2 to 12, median 6.
Primary sources
  • Vendor documentation, GitHub organizations, npm and PyPI for 28 auth platforms and libraries, every record checked on 2026-11-05 (URLs per platform in the dataset)
  • GitHub REST API (stargazers_count) and npm downloads API (2026-10-29 to 2026-11-04), measured 2026-11-05
  • IETF RFC 8693, OAuth 2.0 Token Exchange: https://datatracker.ietf.org/doc/html/rfc8693
  • Model Context Protocol specification, Authorization: https://modelcontextprotocol.io/specification/2025-06-18/basic/authorization
  • llms.txt proposal: https://llmstxt.org/

Developer experience in identity now has two halves, and most platforms only finish one. The human half (SDKs, prebuilt sign-in screens, a short quickstart) is mature at the top of the market. The AI half is moving fast but unevenly: of 28 auth platforms in Start with Identity's Identity Developer Experience Benchmark, 14 (50%) publish an official MCP server that lets an AI coding agent work with your account and 17 document MCP authorization, yet only 9 document RFC 8693 token exchange, the standard that lets an agent act on a user's behalf with a narrower token. On the human side, 23 support passkey sign-in but only 10 ship embeddable components together with a prebuilt passkey enrollment screen, and 9 publish no OpenAPI spec.

This report covers what the benchmark measures, the score, six findings and what to check before you pick. Every value links to the vendor's own documentation, and the data is free to reuse under CC BY 4.0.

Methodology

Scope. 28 customer authentication platforms and libraries that a developer adds to their own product, each with an SWI vendor profile: managed services such as Auth0, Clerk, Stytch, WorkOS, Descope, Frontegg, FusionAuth, Kinde, Amazon Cognito, Firebase Authentication and Google Identity Platform, Microsoft Entra External ID, PropelAuth, Scalekit, MojoAuth, SSOJet and Corbado; open-source servers such as Keycloak, Ory, ZITADEL, authentik, Logto, SuperTokens, Authgear, Hanko, Supabase Auth and Hexclave, formerly Stack Auth; and two libraries, Better Auth and Auth.js. Two candidates are out: Passage by 1Password, whose GitHub organization says it was deprecated on January 16, 2026, and Okta's workforce product, since Okta's customer identity product is Auth0, an Okta subsidiary that is included.

Sources. Vendor documentation, the vendor's GitHub organization, npm and PyPI only, read on November 5, 2026. Every URL in the dataset returned a page when checked. We did not sign up or build with the products: a "yes" means the vendor documents it. "Not documented" means we could not find it on the vendor's own pages; it scores like "no" but is shown separately. GitHub stars come from the GitHub API and npm downloads from the npm downloads API for October 29 to November 4, 2026.

What we counted. Official SDKs are those published in the vendor's GitHub organization or listed as official in its docs; community SDKs are excluded, and a plain JavaScript SDK does not count for a framework. Quickstart steps are counted from the page as published: numbered steps where they exist, otherwise the headed procedure sections, without prerequisites or optional extras. Time claims appear only where the vendor states one. An MCP server counts as "yes" when it can act on your account (for the cloud providers, the general AWS API MCP server and the Microsoft MCP Server for Enterprise); a documentation-only server is "partial".

The score. 100 points, no opinions: SDKs 15, prebuilt UI 10, auth methods 20, quickstart 5, local development 10, APIs 20, AI era 15, open source 5. Yes earns full points, partial half, no and not documented zero. The full rubric is on the benchmark page, with every per-dimension number, and readers can reweight it there. Stars and downloads are not scored: popularity is not developer experience.

Limits. Step counts depend on how a vendor chunks its page, so the quickstart dimension rewards coarse pages. Libraries lose UI and API points by design. Plan gating (passkeys, SSO or SCIM on a paid plan) is in each row's notes, not the score. Some docs render only in a browser, which caused a few "not documented" values (Descope's changelog, for example).

The scores

Platform Score SDKs /15 UI /10 Methods /20 Quickstart /5 Local dev /10 APIs /20 AI /15 Open source /5
Auth0 89.5 14 10 20 3 7.5 20 15 0
Clerk 89 12 10 20 4 10 20 13 0
Logto 86 15 6 14 4 10 17 15 5
WorkOS 86 10 8 18 5 10 20 15 0
Descope 85.5 14 10 20 4 7.5 15 15 0
Frontegg 85 12 10 20 5 10 13 15 0
FusionAuth 82 11 5 18 3 10 17 15 3
Scalekit 82 9 5 20 5 10 20 13 0
Ory 81 8 10 16 4 10 17 11 5
Stytch 79 10 7 20 2 10 16 14 0
Kinde 76 13 6 14 2 10 20 11 0
ZITADEL 74 8 6 16 3 10 20 6 5
SuperTokens 72 9 7 14 4 10 14 11 3
Authgear 71 6 6 14 5 10 16 9 5
Amazon Cognito 70 14 7 12 5 10 14 8 0
Supabase Auth 70 5 4 12 5 10 18 11 5
Better Auth 69 6 0 20 3 10 14 11 5
Hexclave (formerly Stack Auth) 65 3 10 14 4 10 17 4 3
PropelAuth 62.5 7 3 16 2 10 13 10 1.5
SSOJet 61.5 2 5 18 5 7.5 13 11 0
authentik 61 3 6 14 4 10 15 6 3
Hanko 56 0 7 12 3 10 17 2 5
Keycloak 56 2 6 14 4 10 11 4 5
Firebase Authentication / Identity Platform 55 9 4 10 5 10 11 6 0
Microsoft Entra External ID 53 9 3 8 5 5 17 6 0
MojoAuth 45.5 7 3 14 3 5 10 2 1.5
Auth.js 38 3 3 12 5 10 0 0 5
Corbado 35.5 4 7 4 5 0 10 4 1.5

The median is 70.5. The spread at the top is narrow: six platforms sit within 4.5 points of each other, and a single reweighting (doubling open source, or ignoring SDK breadth) reorders them. Read the score as a checklist of documented capabilities, not a verdict. Corbado scores low because it now sells a passkey layer on top of an existing identity provider, so magic links, social login and SSO stay with that provider; for a passkey add-on, its embeddable components and enrollment screen are the relevant part.

Finding 1: MCP support is mainstream, agent delegation is not

AI-era capability Platforms (of 28) Share
llms.txt on the docs site 24 85.7%
Machine-to-machine tokens 20 71.4%
Documents acting as authorization server for MCP 17 60.7%
Docs specifically for authenticating AI agents 17 60.7%
Official MCP server that works with your account 14 50.0%
Documentation-only or limited MCP server 7 25.0%
RFC 8693 token exchange 9 32.1%

The fastest-moving part of identity developer tooling is the part aimed at AI coding agents. Clerk, WorkOS, Descope, Kinde, Logto, Scalekit and Frontegg all document MCP servers that read or change your project, from creating applications to managing organizations and users; Kinde's can read and create but not modify or delete. On the other side of the protocol, 17 platforms document how to act as the OAuth authorization server for a remote MCP server, the role the MCP authorization spec assigns to your identity provider.

Delegation lags. Token exchange under RFC 8693 is how a service or agent swaps a user's token for a narrower one to call a downstream API as that user. Only Auth0, Logto, WorkOS, Descope, Frontegg, FusionAuth, ZITADEL, authentik and Keycloak document it, and Auth0 limits Custom Token Exchange to its Professional and Enterprise plans. Without it, teams fall back to client credentials or long-lived API keys, which lose the user context an audit needs. Our guide to securing AI agent identities covers the patterns.

Finding 2: a third of platforms publish no OpenAPI spec

19 of 28 (67.9%) publish an OpenAPI or Swagger file for their API. The nine that do not include two of the largest clouds, Amazon Cognito and Firebase Authentication (AWS and Google publish their own service-description formats instead), plus Stytch, Frontegg, PropelAuth, SSOJet and MojoAuth. Authgear's Admin API is GraphQL, so OpenAPI does not apply, and Auth.js has no management API at all. Some specs carry caveats: Auth0 labels its Management API OpenAPI 3.1 schema beta, and Ory and SuperTokens publish theirs in GitHub repositories rather than on the docs site.

A published spec matters more in 2026 than it did: it is what code generators, API clients and AI agents read to call the API correctly. Where a vendor publishes none, expect to hand-write client code or lean on its SDKs.

Finding 3: passkeys are everywhere, prebuilt enrollment is not

Passkey support Platforms (of 28) Share
Passkey sign-in documented 23 82.1%
Experimental or limited (Supabase Auth, Auth.js) 2 7.1%
Not documented (PropelAuth, Firebase, Entra External ID) 3 10.7%
Prebuilt passkey enrollment screen 17 60.7%
Embeddable components plus prebuilt enrollment 10 35.7%

Supporting passkeys at the API level is now table stakes. Getting users to enroll one is the hard part, and that is UI work: an enrollment prompt after sign-in, a place to manage passkeys, and a fallback (magic link, code or password) when a device has none. Only 10 platforms document both embeddable components and a prebuilt enrollment screen: Auth0, Clerk, Descope, Frontegg, Ory, Stytch, SuperTokens, Hexclave, Hanko and Corbado. Seven more (Logto, WorkOS, Kinde, ZITADEL, Authgear, authentik and Keycloak) ship the enrollment screen without fully embeddable sign-in components: users enroll on a hosted or server-rendered page, or in WorkOS's case through an embeddable security widget next to a hosted sign-in page.

Six platforms support passkey sign-in without documenting prebuilt enrollment UI: FusionAuth, Scalekit, Amazon Cognito, Better Auth, SSOJet and MojoAuth. With those, you build the enrollment screen, which is where most rollouts stall. The passkeys guide and the WebAuthn standard page cover what that screen has to handle. Plan gating applies here too: Clerk requires a paid plan for passkeys in production, and FusionAuth needs at least a Licensed Community plan.

Finding 4: rate limits and changelogs are the quiet documentation gaps

18 of 28 (64.3%) document API rate limits with numbers. For self-hosted servers such as Keycloak, authentik and Hanko the limit is your own infrastructure, so the gap that matters is among managed services: of 16, 12 publish a rate-limit page and 4 (FusionAuth, PropelAuth, MojoAuth and Corbado) have none we could find. An undocumented limit surfaces as a 429 in production, usually during a migration or a sign-up spike.

Changelogs tell the same story. 19 of 28 had a changelog or release entry in the 90 days before November 5, 2026. Of the other nine, four publish no changelog we could read (Descope's renders only in a browser; MojoAuth, SSOJet and Corbado have none in their docs), and five are older: Frontegg's docs changelog ends in December 2024, Google Identity Platform's release notes in December 2024, Microsoft's External ID docs what's-new page in January 2026, Ory Kratos's last release in March 2026 and next-auth's in July 2026. 22 of 28 publish a status page.

Finding 5: self-serve enterprise SSO is still a minority feature

B2B capability Platforms (of 28) Share
SAML and OIDC with a self-serve setup flow for the customer's IT admin 10 35.7%
SAML or OIDC configured by the developer only, or one protocol 17 60.7%
Inbound SCIM provisioning 15 53.6%

Self-serve SSO (an admin portal or setup link where the customer's IT team configures its own SAML or OIDC connection) is what keeps enterprise onboarding from becoming a support ticket. Auth0, Clerk, WorkOS, Descope, Frontegg, Scalekit, Stytch, Kinde, PropelAuth and Better Auth document it; Better Auth's needs its paid Infrastructure service, and Kinde's self-serve flow covers SAML, with OIDC added as custom connections. The other platforms with SSO make the developer configure each connection. Our SSO and SCIM rankings for B2B SaaS compare the B2B side in more depth.

Finding 6: nobody times their quickstart, and step counts vary sixfold

Only WorkOS ("Integrating AuthKit into your app can be done in less than ten minutes") and Stytch ("Get up and running with Stytch in minutes") put a time on their quickstart. Counted from the pages, official quickstarts run from 2 steps (WorkOS, whose two steps each contain several sub-steps) to 12 (MojoAuth's Next.js guide), median 6; Kinde's Next.js page is an SDK guide and Stytch's quickstart is a chooser, so neither has a countable procedure. Several "Next.js quickstarts" are not SDK quickstarts at all: ZITADEL, MojoAuth and SSOJet document Next.js through Auth.js or a generic OIDC client.

17 of 28 ship an official Next.js integration, and 22 of 28 document a development environment, emulator or one-command local run. Among the cloud-only services, only Firebase documents a local emulator; the rest offer a development instance, test environment or separate tenant instead.

What to check before you pick

  1. Filter for your stack first. An SDK you have to wrap yourself costs more than any score difference. The benchmark's framework filter shows official SDKs only.
  2. Ask for the enrollment screen, not the passkey API. If the vendor has no prebuilt passkey enrollment, budget the UI work, the fallback and the account recovery flow.
  3. Read the plan page for SSO, SCIM and passkeys. Several platforms move one of the three to a paid tier; the notes on each row say which.
  4. For AI features, check token exchange and MCP authorization separately from the MCP server. An MCP server helps your developers; MCP authorization and RFC 8693 are what your product's own agents and integrations need.
  5. Look for the OpenAPI spec and the rate-limit page. Both are quick to verify and both predict how much undocumented behavior you will meet later.

The CIAM buyer's guide and the startup CIAM rankings cover price, scale and compliance, which this benchmark leaves out. For phishing-resistant MFA in the SaaS apps your team signs in to, see the MFA support matrix.

Frequently asked questions

Which identity platform is better for developers?
On SWI's published 100-point rubric, the top five of 28 auth platforms checked November 5, 2026 are Auth0 (89.5), Clerk (89), Logto (86), WorkOS (86) and Descope (85.5); the median is 70.5. The score counts documented facts only: official SDKs, prebuilt UI, auth methods, quickstart length, local development, APIs, AI-era features and open source. Filter the benchmark for your framework and must-haves, or reweight the dimensions, and the order changes.
Which auth provider has prebuilt UI components for passkey enrollment and fallback flows?
10 of 28 platforms document both embeddable UI components and a prebuilt screen where users enroll a passkey: Auth0, Clerk, Descope, Frontegg, Ory, Stytch, SuperTokens, Hexclave (formerly Stack Auth), Hanko and Corbado. Seven more (Logto, WorkOS, Kinde, ZITADEL, Authgear, authentik and Keycloak) ship the enrollment screen without fully embeddable sign-in components, mostly on a hosted or server-rendered page.
How many auth platforms have an official MCP server?
14 of 28 publish an official MCP server that lets an AI agent work with your account: Auth0, Clerk, Logto, WorkOS, Descope, Frontegg, FusionAuth, Scalekit, Stytch, Kinde, Amazon Cognito (through the general AWS API MCP server), Supabase, Firebase and Microsoft Entra (through the Microsoft MCP Server for Enterprise). Ory, SuperTokens, Better Auth, Hexclave, PropelAuth and SSOJet publish documentation-only or integration-helper MCP servers, and Corbado's is in closed beta.
Do auth providers support RFC 8693 token exchange for AI agents?
Only 9 of 28 document OAuth 2.0 Token Exchange (RFC 8693): Auth0, Logto, WorkOS, Descope, Frontegg, FusionAuth, ZITADEL, authentik and Keycloak. Stytch documents RFC 8693 requests only toward a workforce identity provider in its cross-app flow. Token exchange is how an agent or downstream service swaps a user's token for a narrower one, so its absence pushes teams toward long-lived API keys.
Is Auth.js still maintained?
The Auth.js README says Auth.js is now part of Better Auth and recommends that new projects start with Better Auth. The latest next-auth release we found was dated July 20, 2026, its WebAuthn (passkeys) provider is labelled experimental, and it has no user-management API. Auth.js scores 38 on the benchmark against 69 for Better Auth.
How is the developer experience score calculated?
100 points over eight dimensions: SDKs 15, prebuilt UI 10, auth methods 20, quickstart 5, local development 10, APIs 20, AI era 15 and open source 5. A documented yes earns full points, partial half, and no or not documented zero. GitHub stars and npm downloads are published but not scored. Every value links to the vendor's own documentation.

Cite this report

Free to quote and reuse under CC BY 4.0 with a link back. Each key finding has its own anchor (for example #finding-1) so you can link the exact figure you cite. Published November 20, 2026, last updated November 20, 2026.

SWI Community Team. (2026). Identity Developer Experience Benchmark 2026. Start with Identity. https://startwithidentity.com/reports/identity-developer-experience-2026/

Free to read and cite with attribution. Independent and community-driven, no sponsorship. See the live data in the research hub.