Why developers leave Clerk: enterprise SAML/SCIM is on higher tiers (pricing jumps), customizing UI past CSS variables requires more work, and self-host isn't available. Teams that hit enterprise procurement requirements or need on-prem deployment evaluate Auth0 or hybrid stacks.
Auth0 wins on enterprise IdP catalog and procurement maturity. SAML federation, mature compliance certifications. The trade-off: pricing opaque and steep, DX trails Clerk.
WorkOS pairs with Clerk for the enterprise-readiness layer Clerk's lower tiers don't cover. SSO + SCIM + audit logs as APIs. Free SSO with per-active-org pricing.
When customer pipeline becomes heavily enterprise (>50% Fortune 1000), when FedRAMP is required, or when complex IdP federation patterns Clerk doesn't cover are needed. For most B2C/B2B SaaS Clerk is the better fit.
Yes — common pattern. Start with Clerk for full auth. Add WorkOS for SSO/SCIM when enterprise customers request it. The architecture is well-documented; both companies' DX makes the integration clean.
Not at writing. Clerk has been clear about cloud-only positioning. Teams requiring self-host should evaluate Supabase Auth, Auth0's on-prem option, or SuperTokens.
