Authentication for Next.js: what 211 makers' products chose
Among 211 makers' products built with Next.js that we know the authentication of, Clerk leads: 176 of them (83%). Next come WorkOS (11) and Auth0 (6).
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 Next.js chose
| Option | Next.js products | All makers | 2026 launches | Free for | At 10,000 users |
|---|---|---|---|---|---|
| 176 (83%) | 80% | 82% | ~50,000 users | $0/moHobby | |
| 11 (5%) | 5% | 9% | ~1,000,000 users | $0/moAuthKit | |
| 6 (3%) | 5% | 4% | ~25,000 users | $0/moFree | |
| 5 (2%) | 3% | 2% | ~50,000 users | $0/moFree | |
| 5 (2%) | 2% | 0% | Any size | $0/moSelf-hosted (open source) | |
| 3 (1%) | 1% | 0% | ~10,000 users | — | |
| 2 (1%) | 2% | 0% | ~10,000 users | — | |
| 1 (0%) | 1% | 2% | ~50,000 users | $0/moBlaze (pay as you go) | |
| 1 (0%) | 0% | 0% | ~10,000 users | — | |
| StytchHosted service | 1 (0%) | 1% | 2% | — | — |
| LogtoOpen-source service | 1 (0%) | 0% | 2% | — | — |
Live makers' products with a source for both: that they're built with Next.js, 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. "2026 launches" is its share among the 57 Next.js products launched that year: a tool that came first has products from every year since, so its total runs ahead.
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 176 here - Your data is already in Supabase or Firebase
Supabase 5 here
Firebase 1 here - You want users in your own database and no per-user bill
Better Auth 5 here - You sell to companies whose IT team will ask for SAML SSO or SCIM
WorkOS 11 here
Auth0 6 here
Clerk
Hosted service176 Next.js products here (83%), against 80% of all makers' products. 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.
“Login had to work on the website and in the mobile app with the same account. Clerk just did it. The account deletion webhook was also less painful than I expected.”
- 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).
“We needed production-ready authentication without slowing the team down. Clerk let us ship securely from day one and stay focused on core product work. Setup was fast, UX is polished out of the box, and it scales cleanly without us constantly revisiting edge cases.”
AuthenticationMaker says so +2 · source ↗“Auth done right. Drop it in, configure, move on. We never think about login flows.”
AuthenticationMaker says so +2 · source ↗“Clerk makes it super easy to handle auth state in our app, handle user roles and permissions, and add the latest sign-in methods.”
AuthenticationMaker says so +2 · source ↗“We needed auth that handles both individual users and multi-tenant organizations out of the box. Clerk gave us JWT-based auth, org management, RBAC, and webhook sync — all with a clean React SDK and middleware for Next.js. We evaluated Auth0 (too complex for our stage), Supabase Auth (no native org support), and NextAuth (too much DIY). Clerk let us ship secure multi-tenant auth in days instead of weeks, so we could focus on the RAG pipeline instead of reinventing session management.”
AuthenticationMaker says so +2 · source ↗“Has made our ability to manage onboarding super seamless - good out of the box functionality and ecosystem of integrations.”
AuthenticationMaker says so +1 · source ↗“I needed sign-in that worked and looked good without me building it from scratch. Clerk gave me Google auth, user management, and a polished UI out of the box. Took maybe an afternoon to integrate”
AuthenticationMaker says so +1 · source ↗“Clerk makes authentication a breeze and would recommend for all SaaS.”
AuthenticationMaker says so +1 · source ↗“Used Clerk for authentication. It was seamless.”
AuthenticationMaker says so +1 · source ↗“Clerk makes auth integration super simple. From magic links to social logins, it just works out of the box, saving us tons of time.”
AuthenticationMaker says so +1 · source ↗“Saved us weeks of work supporting teams and orgs.”
AuthenticationMaker says so +1 · source ↗
WorkOS
Hosted service11 Next.js products here (5%), against 5% of all makers' products. Free up to about 1,000,000 users. About $0 a month at 10,000 users (AuthKit).
llms.txtMCPBest forB2B SaaS that will need enterprise SSO and directory sync.
Trade-offIts free tier covers basic sign-in, but enterprise SSO and directory sync are priced per connection — worth it once a customer pays for them.
“We chose WorkOS because it's straightforward to integrate and easy to work with. It let us add the features we needed without unnecessary complexity.”
- Enterprise SSO, SAML and SCIM directory sync arrive ready-made, integrated in weeks instead of months, so teams can close enterprise deals. 2 sources
- Organization separation and B2B features come built in alongside standard social login. 1 source
- When WorkOS has an outage, logins fail for every app that depends on it. 2 sources
- SCIM integrations have broken for customers, and it withholds SAML and SCIM configs and password hashes, creating hard lock-in. 1 source
Which languages and frameworks have SDKs? Official SDKs cover Node, Python, Go, Ruby, PHP, Java, .NET, Elixir and Rust, with AuthKit packages for Next.js, React, React Router, Remix, Astro, TanStack Start, Laravel, iOS and Android. WorkOS docs ↗
Status page: 24 incidents in the last 90 days, 10 major (its own page, 2026-10-19).
“Really simplified integration of auth”
AuthenticationMaker says so · source ↗“We chose WorkOS because it's straightforward to integrate and easy to work with. It let us add the features we needed without unnecessary complexity.”
AuthenticationMaker says so · source ↗“A lot of auth features came out of the box and we didn't have to stress about setting them up.”
AuthenticationMaker says so · source ↗“WorkOS made it dead simple to add authentication to Flipt Cloud. Integrating with WorkOS allows us to have social authentication like GitHub and Google out of the box, along with enterprise-ready features like Single Sign On, SAML, and SCIM Directory Sync. WorkOS handles the auth, allowing us to focus on building a great product.”
AuthenticationMaker says so · source ↗“WorkOS gives Almanac secure authentication and organization management that works from day one.”
AuthenticationMaker says so · source ↗“WorkOS made it extremely easy for us to add auth to our ActionKit playground - we also use them for SSO for our core product as well.”
AuthenticationMaker says so · source ↗“WorkOS handles all authentication needs for our Tella users and teams, ensuring enterprise-level security and readiness. This is a recent switch, the migration also went very smooth.”
AuthenticationMaker says so · source ↗“Most secure way for users while making it easy to implement! Thanks!”
AuthenticationMaker says so · source ↗“Not only has WorkOS built in all the standard expectations you'd have for an Auth provider, they go beyond by making b2b features like organization separation, vault storage with BYOK, and go above and beyond with their customer support model. Really enjoy working with them.”
AuthenticationMaker says so · source ↗
Auth0
Hosted service6 Next.js products here (3%), against 5% of all makers' products. 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.
“You really don't want to mess with security and authentication yourself. Auth0 is great for B2C apps.”
- 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 ↗“You really don't want to mess with security and authentication yourself. Auth0 is great for B2C apps.”
AuthenticationMaker says so · source ↗“Served us well for both dashboard and app user access management”
AuthenticationMaker says so · source ↗“When your AI agents are browsing your store backend, updating SKUs, and emailing customers on your behalf — identity boundaries matter a lot. Auth0's M2M token model gave us exactly the permission control we needed for safe, scoped agent actions. 👉 ClawTeams — AI agent teams built for ecommerce, with security taken seriously.”
AuthenticationMaker says so · source ↗“For handling our user authentication with enterprise-grade security, so our users can log in instantly and focus on their data.”
AuthenticationMaker says so · source ↗
Supabase
Bundled with your backend5 Next.js products here (2%), against 3% of all makers' products. 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.
“Supabase is CatDoes' backend. We use their database, auth, storage, and real-time features. A platform like CatDoes requires a stable and scalable backend, and Supabase is providing that!”
- 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
Does it work with Next.js server-side rendering? Yes. Server-rendered apps keep the session in cookies, and the @supabase/ssr package together with supabase-js handles this for Next.js and other JavaScript frameworks. Supabase docs ↗
Status page: 25+ incidents in the last 90 days, 6 major (its own page, 2026-10-19).
“Supabase powers our entire backend infrastructure — from seamless user authentication to reliable file storage and secure secrets management with Vault. Supabase Storage was a game-changer for our AI workflow engine's reliability. Thank you for building such a developer-friendly platform!”
AuthenticationFile StorageMaker says so +1 · source ↗“Supabase powers our app with reliable authentication, database, and storage solutions. Its robust infrastructure keeps our application running smoothly and securely, letting us focus on user experience.”
AuthenticationDatabaseFile StorageMaker says so · source ↗“I wanted real Postgres, not a proprietary store I'd be locked into. Supabase bundles the database, auth, and storage, it's open source, and I can self-host if I ever outgrow it. Firebase felt like a cage by comparison.”
DatabaseAuthenticationMaker says so · source ↗“Supabase is CatDoes' backend. We use their database, auth, storage, and real-time features. A platform like CatDoes requires a stable and scalable backend, and Supabase is providing that!”
DatabaseAuthenticationMaker says so · source ↗“Helps power authentication and real-time data layers.”
AuthenticationDatabaseMaker says so · source ↗
Better Auth
Library in your app5 Next.js products here (2%), against 2% of all makers' products. Free at any size on our usage model. About $0 a month at 10,000 users (Self-hosted (open source)).
llms.txtBest forTypeScript apps that want users and sessions in their own database, at no cost.
Trade-offYou host it and keep it patched; UI is yours to build.
“Authentication is always a time sink, but not with better_auth. Simple, secure, and extendable. Got magic links and login flow done in under an hour.”
- A library that keeps users and sessions in your own database, with no vendor dependency and no per-user fees. 4 sources
- Plugins cover OAuth providers, magic links, RBAC, SSO and SAML, going well beyond Auth.js. 4 sources
- Built-in assumptions force hacks, such as OIDC providers without email or request-header-based admin scripts. 2 sources
- Code quality felt rushed, with few tests and little logging, and audit logs need the managed service. 2 sources
Which frameworks does Better Auth work with? It is framework-agnostic TypeScript with documented integrations for Next.js, Nuxt, SvelteKit, Astro, React Router v7, TanStack Start, SolidStart, Hono, Express, Fastify, NestJS, Elysia, Convex, Electron and Expo. Better Auth docs ↗
“We love open source auth, tackling a really old problem in a clean, nice way.”
AuthenticationMaker says so · source ↗“It came out of nowhere and became popular for a good reason - it's really good!”
AuthenticationMaker says so · source ↗“beautiful abstractions, great support from the team”
AuthenticationMaker says so · source ↗“Authentication is always a time sink, but not with better_auth. Simple, secure, and extendable. Got magic links and login flow done in under an hour.”
AuthenticationMaker says so · source ↗“saved us laborious work.”
AuthenticationMaker says so · source ↗
PropelAuth
Hosted service3 Next.js products here (1%), against 1% of all makers' products. Free up to about 10,000 users.
llms.txtCLIBest forB2B products where every customer is an organization with members, roles, invites and SAML.
Trade-offPaid plans start well above hobby budgets once you pass the free tier; users live in PropelAuth, not your database.
“Since we migrated to PropelAuth our overhead of managing organizations and users has dropped 10x - so easy to get started and yet comes with lots of features.”
“They saved us a good few weeks of dev effort on building auth and admin. Also, an amazing team and support.”
AuthenticationMaker says so · source ↗“Great documentation and support to get started!”
AuthenticationMaker says so · source ↗“Since we migrated to PropelAuth our overhead of managing organizations and users has dropped 10x - so easy to get started and yet comes with lots of features.”
AuthenticationMaker says so · source ↗Also chosen, and not seen yet
Fewer Next.js products here: Kinde (2), Firebase (1), Hexclave (Stack Auth) (1), Stytch (1), Logto (1).
Who switches, and to what
Public GitHub pull requests whose title says "X to Y", by developers in general, not only on Next.js.
- Firebase → Supabase 297 pull requests · how they moved
- Supabase → Firebase 113 pull requests · how they moved
- 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
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 Next.js stack
What makers' Next.js products chose for their other decisions, the most common pick for each:
- Hosting: Vercel 1,078 of 1,312
- Transactional Email: Resend 493 of 830
- Database: Supabase 171 of 382
- Payments: Stripe 288 of 359
- LLM API: OpenAI API 222 of 301
- Web Analytics: Google Analytics 105 of 197
- Product Analytics: PostHog 123 of 168
- Lifecycle Email: Loops 87 of 108
Questions
What do most Next.js apps use for authentication?
Among 211 makers' products built with Next.js that we know the authentication of, Clerk leads: 176 of them (83%). Next come WorkOS (11) and Auth0 (6).
What does authentication cost for a Next.js app with 10,000 users?
On our usage model at 10,000 users, Clerk (Hobby), WorkOS (AuthKit), Auth0 (Free), Supabase (Free) all still cost nothing a month. Prices are from each vendor's pricing page.
Which authentication option stays free longest for a Next.js app?
Better Auth: on our usage model it stays free even at 10 million users.
How this is counted: a product is on Next.js 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.