FINDING 01·Developers running production apps dependent on Auth0·1 source
Auth0 reliability / outages undermine production apps
As of 2021, users reported repeated Auth0 outages (four in two months) knocking out their apps, with official uptime figures not matching real-world experience. This drove users to seek alternatives or multi-region resilience strategies.
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. 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 teams using vanilla JS or non-standard stacks·2 sources
Auth0 onboarding and quick-start guides fail in practice
Developers across multiple discussions report that even following Auth0's official quick-start guides step-by-step results in authentication errors with no clear resolution. This is a recurring complaint from vanilla JS / non-framework users and causes significant schedule delays.
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 MAU·2 sources
Auth0 pricing became prohibitively expensive post-Okta acquisition
Multiple discussions highlight that Auth0's pricing shifted aggressively after Okta acquired them, making it especially painful for B2C startups with large MAU counts. MFA was also removed from lower tiers, compounding the frustration. Deep integration makes switching costly even when users want to leave.
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·SaaS founders and developers prioritising data ownership·2 sources
Vendor lock-in from proprietary auth providers is a strategic risk
Developers express concern about being locked into proprietary platforms (Auth0, Clerk) for critical user data, driving strong demand for open-source, self-hostable alternatives that allow data portability and infrastructure control.
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.”
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.”
FINDING 05·Full-stack developers using Auth0 with Next.js·1 source
Poor documentation for protecting APIs and advanced token flows in Auth0 + Next.js
Developers struggle to find clear documentation on how to use Auth0 access tokens for both client-side and server-side API calls in Next.js, particularly around specifying the audience and protecting custom API routes — resorting to asking for alternative solutions entirely.
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? Alternatively can anyone reccomend an alternative solution?”
FINDING 06·Frontend developers integrating Auth0 with custom or third-party identity servers·1 source
Auth0 SDK has hardcoded URLs that break non-standard OIDC configurations
A 2024 complaint highlights that auth0-spa-js (used under the hood by auth0-react) hardcodes the token endpoint URL instead of dynamically reading it from the .well-known/openid-configuration discovery document, breaking integrations with identity servers that use non-default URL paths.
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. If it's not solvable problem - what alternative auth0 client library I can use instead?”
FINDING 07·B2B SaaS developers using React-based frameworks·1 source
Bugs and instability in YC-backed auth providers (Kinde, Clerk) frustrate React/B2B developers
As of early 2024, developers building B2B SaaS on React frameworks (Next.js, Remix) report encountering frustrating bugs in newer YC-backed auth providers like Kinde and Clerk, leaving them without a clearly reliable alternative.
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?”