FINDING 01·Developers running production apps dependent on Auth0 as a single point of failure·2 sources
Auth0 reliability / outages undermine production applications
As of 2021, developers reported repeated Auth0 outages (four in two months) that knocked out their apps and triggered customer complaints. Auth0's own status page showed 99.87% availability, which users found inconsistent with their lived experience. This pain is from 2021 and may have improved since, but it was a significant driver of alternative-seeking at the time.
Source
“After the fourth Auth0 outage in the last two months has knocked out my app, I'm somewhat at a loss of what to do.”
Source
“Through some downtime accounting magic, they are reporting 99.87% availability, but my stress levels from responding to customer emails on Friday and this morning say otherwise.”
FINDING 02·Indie developers and small-team builders using vanilla JS / Hapi.js stacks·2 sources
Auth0 quick-start guides produce authentication errors with no clear resolution
Multiple developers across 2023–2024 report that following Auth0's official documentation step-by-step still results in authentication errors, with no actionable guidance on how to fix them. This is a recurring onboarding failure that pushes developers to seek alternatives.
Source
“Even exactly following Auth0's quick start guides leads to authentication errors with no clear answers why.”
Source
“Even followed Auth0's guides to the letter, still getting authentication errors with no clear fixes. And the internet's usual helpfulness is MIA. Probably messing something up, but I'm 4 days behind schedule now.”
FINDING 03·B2C SaaS founders and startups with high monthly active user counts·2 sources
Auth0 pricing became prohibitively expensive after Okta acquisition, especially for B2C / high-MAU products
Since Okta acquired Auth0, users report aggressive pricing changes that make the service unaffordable for startups with large user bases. The removal of MFA from lower tiers is a specific flashpoint. Vendor lock-in compounds the problem, making migration costly even when pricing becomes untenable. This pain is well-documented from 2023 and remains a dominant reason developers seek alternatives.
Source
“Since Okta acquired them they changed their pricing aggressively, which makes it very costly, especially for B2C that have many MAU. Furthermore, they removed MFA from their 'cheapest' tier, which I find very unconsumery.”
Source
“our code is deeply integrated with Auth0 and shifting away will take plenty of time and be very costly as well.”
FINDING 04·Privacy-conscious developers, self-hosters, and startups wary of vendor dependency·2 sources
Vendor lock-in and lack of open-source / self-hostable options across major auth providers
A persistent theme across 2020–2025 is that both Auth0 and Clerk are entirely proprietary, creating strong vendor lock-in. Developers want open-source, self-hostable alternatives that give them control over user data and infrastructure without sacrificing the convenience of a managed service. This is a structural gap, not a bug.
Source
“User data is quite critical, and you generally don't want to get locked into a specific vendor. On the other hand, building and maintaining auth infrastructure on-top of existing libraries is tedious work as you grow.”
Source
“The dominant player in this space is Auth0, who appeals to enterprises but lags behind in developer-friendliness and has strong vendor lock-in. A newer one is Clerk, which markets directly to devs, but is still entirely proprietary.”
FINDING 05·Full-stack developers building Next.js apps with Auth0·1 source
Difficulty protecting APIs and passing access tokens correctly in Auth0 + Next.js setups
Developers integrating Auth0 with Next.js find it unclear how to protect API routes and pass access tokens for both client-side and server-side calls, with documentation focused on machine-to-machine flows rather than user-context API protection.
Source
“I want to protect an api and use the access token for connecting to auth0 in clientside and serverside api calls... I can only find documentation on client credentials flow / machine to machine.... How can i specify the audience in my nextjs app?”
FINDING 06·Frontend/full-stack developers integrating Auth0 React SDK with third-party OIDC identity servers·2 sources
Auth0 client libraries use hardcoded URLs instead of respecting OpenID Connect discovery
Developers integrating Auth0 with non-Auth0 identity servers (e.g. Duende) find that auth0-spa-js hardcodes token endpoint URLs rather than fetching them from the standard .well-known/openid-configuration discovery document. This breaks compatibility with any identity server that uses a non-default token path, forcing developers to seek alternative client libraries.
Source
“auth0/auth0-react is using under the hood auth0-spa-js which is using hardcoded url to fetch bearer tokens: like POST to /connect/oauth/token. But in my case it should go to /connect/token instead as it is configured on my identity server (duende) here: .well-known/openid-configuration”
Source
“As I understand problem is well-known but strange thing that it is not solved yet.”
FINDING 07·B2B SaaS developers using React-based frameworks (Next.js, Remix)·2 sources
Managed auth services (Clerk, Kinde) have frustrating bugs for B2B / React framework integrations
Developers building B2B SaaS on React frameworks (Next.js, Remix) report encountering frustrating bugs in YC-backed auth providers like Clerk and Kinde, and struggle to find well-integrated alternatives. Clerk is also flagged as expensive for serverless web apps.
Source
“I keep encountering frustrating bugs using YC-backed Auth Providers like Kinde and Clerk Auth... What alternatives are there that integrate nicely with React frameworks (Next / Remix), especially for B2B authentication”
Source
“I was recommended clerk, but later noticed that it's quite expensive.”