Authentication for React: what 15 makers' products chose
Among 15 makers' products built with React that we know the authentication of, Clerk leads: 8 of them (53%). Next come Auth0 (3) and Supabase (2).
Hosted service or library in your own app. Hosted services give you UI, MFA and security updates for a monthly bill and some lock-in; libraries keep users in your own database for free, and you own the upkeep.
What makers on React chose
| Option | React products | All makers | Free for | At 10,000 users |
|---|---|---|---|---|
| 8 (53%) | 80% | ~50,000 users | $0/moHobby | |
| 3 (20%) | 5% | ~25,000 users | $0/moFree | |
| 2 (13%) | 3% | ~50,000 users | $0/moFree | |
| 1 (7%) | 2% | Any size | $0/moSelf-hosted (open source) | |
| 1 (7%) | 5% | ~1,000,000 users | $0/moAuthKit | |
| StytchHosted service | 1 (7%) | 1% | — | — |
Live makers' products with a source for both: that they're built with React, and what they use for authentication. A product using two options counts in both; not market share. "All makers" is the option's share among every maker's product that made this decision.
Costs are the cheapest plan that fits, from each vendor's pricing page, at the usage our stack planner assumes for a product with that many users. Free for: the users its cheapest plan a business can use stays free for; plans for personal use only, like a non-commercial hobby tier, don't count.
Which to pick, by situation
- You're on Next.js or React and want sign-in, profiles and teams working today
Clerk 8 here - Your data is already in Supabase or Firebase
Supabase 2 here - You want users in your own database and no per-user bill
Better Auth 1 here - You sell to companies whose IT team will ask for SAML SSO or SCIM
WorkOS 1 here
Auth0 3 here
Clerk
Hosted service8 React products here (53%). Free up to about 50,000 users. About $0 a month at 10,000 users (Hobby).
llms.txtMCPCLIIn ReplitBest forDropping prebuilt sign-in, profile and organization UI into a React or Next.js app.
Trade-offPer-user pricing grows with you; users live in Clerk, not your database.
- Sign-up, sign-in, sessions and social login get wired in an afternoon instead of a sprint. 2 sources
- Organizations, roles and billing come built in, covering multi-tenant B2B apps without custom identity work. 2 sources
- Outsourcing auth means a Clerk outage or account problem locks your users out, and the dependency is hard to reverse. 4 sources
- Costs climb with SSO, MFA, passkeys and branding removal, and some switched to cheaper open-source options. 4 sources
Which frameworks and languages does Clerk support? Clerk maintains SDKs for Next.js, React, Expo, Astro, Nuxt, Vue, React Router, TanStack Start, Chrome extensions, Electron, iOS and Android, plus backend SDKs for Express, Fastify, Go, Python, Ruby on Rails, Java, PHP and C#. SvelteKit, Angular, Hono and Flutter are covered by community-maintained SDKs. Clerk docs ↗
Status page: 9 incidents in the last 90 days (its own page, 2026-10-19).
Auth0
Hosted service3 React products here (20%). Free up to about 25,000 users. About $0 a month at 10,000 users (Free).
llms.txtMCPBest forComplex identity needs and enterprise compliance.
Trade-offHeavier to configure and pricier than newer options for a solo project.
“Listed in their tool stack on Starter Story (trello email)”
- Enterprise-grade login with SSO and modern standards, so teams avoid rolling their own auth. 2 sources
- Integrates across web and mobile app platforms, with well-regarded docs and responsive onboarding. 1 source
- Contracts are expensive with escalating prices and deep vendor lock-in. 3 sources
- Exporting users and password hashes requires a support ticket, which makes migrations painful. 3 sources
Which frameworks does Auth0 have quickstarts for? Web apps in Next.js, Nuxt, React Router, Express, Fastify, Hono, Django, FastAPI, Python, Rails, Laravel, PHP, Go, Java and ASP.NET; SPAs in React, Vue, Angular and Svelte; and native apps on iOS, Android, Flutter, React Native and Expo. Auth0 docs ↗
“Listed in their tool stack on Starter Story (trello email)”
AuthenticationMaker says so +1 · source ↗“Auth0 : user management and authentication.”
AuthenticationMaker says so · source ↗
Supabase
Bundled with your backend2 React products here (13%). Free up to about 50,000 users. About $0 a month at 10,000 users (Free).
llms.txtMCPCLIIn Bolt, Lovable, Rork, v0Best forApps already on Supabase — auth is part of the same project as the database.
Trade-offLess polished UI components than dedicated auth services.
“Our choice for enabling builders to add backend features like authentication, data persistence, AI functions, payment checkout to apps built in Lovable”
- One project covers Postgres, auth, storage and realtime, so a solo founder ships without stitching vendors or hiring a backend team. 4 sources
- It is real Postgres with SQL, row-level security and pgvector rather than a proprietary store. 4 sources
- Row-level security policies are hard to get right, so many apps end up exposing data publicly. 4 sources
- Reliability has been shaky for some, and it is not really built for self-hosting in practice. 1 source
Status page: 25+ incidents in the last 90 days, 6 major (its own page, 2026-10-19).
“Our choice for enabling builders to add backend features like authentication, data persistence, AI functions, payment checkout to apps built in Lovable”
AuthenticationDatabaseMaker says so +1 · source ↗“Helps power authentication and real-time data layers.”
AuthenticationDatabaseMaker says so · source ↗Also chosen, and not seen yet
Fewer React products here: Better Auth (1), WorkOS (1), Stytch (1).
Real options for authentication not seen among these React products yet: Firebase.
Who switches, and to what
Public GitHub pull requests whose title says "X to Y", by developers in general, not only on React.
- Supabase → Clerk 54 pull requests · how they moved
- Clerk → Supabase 53 pull requests · how they moved
- Clerk → Better Auth 33 pull requests · how they moved
- Supabase → Better Auth 19 pull requests
- Auth0 → Clerk 6 pull requests
- Auth0 → Supabase 6 pull requests
Getting authentication right
Start with email + one social login (Google or GitHub). Keep the user record in your own database even when a hosted service owns sign-in, so you can switch later. Add organizations and SSO only when a paying customer asks.
- Keeping users only inside the auth provider — with no row in your own database, every query that joins users goes through their API, and moving later means a password-reset email to everyone.
- Building organizations, roles and SSO before a paying customer asks for them.
- Comparing only free tiers; per-monthly-active-user pricing is what you pay once a free product gets traffic.
The rest of the React stack
What makers' React products chose for their other decisions, the most common pick for each:
- Hosting: Vercel 68 of 147
- Transactional Email: SendGrid 64 of 109
- Payments: Stripe 76 of 87
- Database: PostgreSQL 32 of 73
- Web Analytics: Google Analytics 54 of 66
- LLM API: OpenAI API 23 of 38
- Product Analytics: PostHog 17 of 37
- Lifecycle Email: Loops 10 of 19
Questions
What do most React apps use for authentication?
Among 15 makers' products built with React that we know the authentication of, Clerk leads: 8 of them (53%). Next come Auth0 (3) and Supabase (2).
What does authentication cost for a React app with 10,000 users?
On our usage model at 10,000 users, Clerk (Hobby), Auth0 (Free), Supabase (Free), Better Auth (Self-hosted (open source)) all still cost nothing a month. Prices are from each vendor's pricing page.
Which authentication option stays free longest for a React app?
Better Auth: on our usage model it stays free even at 10 million users.
How this is counted: a product is on React when a live-product source says so (the maker, its website, a customer story or a subprocessor list), and the same for its authentication. How evidence is collected.