Auth that scales for AI agents
Reed McGinley-Stempel, CEO of Stytch, on authentication for AI agents
Clerk’s early advantage comes from collapsing auth into a few ready made UI blocks, but that same abstraction becomes a constraint once a company needs custom enterprise workflows. It works best when a startup wants sign up, sign in, org switching, and billing to appear quickly inside a React or Next.js app. It gets harder when buyers need deeper identity plumbing, like custom SSO setups, directory sync, complex roles, and admin controlled rollout.
-
Clerk was built around React components like SignIn, SignUp, UserProfile, and OrganizationSwitcher. That product shape makes first launch fast, especially for self serve startups and framework native teams, which is why it shows up often in startup evaluations and much less in enterprise sales cycles.
-
WorkOS took the opposite path. It started with SSO and SCIM APIs for teams that already had auth and only needed enterprise requirements added on. That fits companies selling upmarket, where the blocker is often getting Okta, Azure AD, audit logs, and admin setup working without rebuilding the whole login stack.
-
The market is converging toward broader platforms. Clerk is adding billing and more B2B controls, while WorkOS has expanded from enterprise add ons into full auth, fraud, authorization, and integrations. The simple widget versus enterprise API split is giving way to vendors trying to cover more of the identity surface area.
Going forward, the winning auth vendors will be the ones that let a team start in an afternoon and still support enterprise complexity years later. As AI apps, B2B SaaS, and agent based workflows force more products to become full identity systems, shallow convenience will matter less than whether the starter product can stretch into serious infrastructure.