Clerk vs Supabase
Of the 422 makers' products we know the authentication of, 336 chose Clerk (80%) and 13 Supabase (3%); 1 uses both. Among the 98 launched in 2026, Clerk is in 84% and Supabase in 2%, against 76% and 3% of those launched in 2024 or earlier. They're different kinds of tool, hosted service and bundled with your backend, so the counts don't measure the same choice. On GitHub, 53 public pull requests moved projects from Clerk to Supabase, and 54 the other way.
Two sides of the authentication decision: hosted service and bundled with your backend. When each fits, what it costs, who moves from one to the other, and what makers who chose it say.
ClerkHosted servicellms.txtMCPCLIIn Replit
SupabaseBundled with your backendllms.txtMCPCLIIn Bolt, Lovable, Rork, v0Which fits you
- You're on Next.js or React and want sign-in, profiles and teams working today
Use it whenYou want prebuilt components, user profiles and organizations out of the box.
Trade-offPer-user pricing grows with you; users live in Clerk, not your database.
- Your data is already in Supabase or Firebase
Use it whenYou want row-level security in Postgres tied directly to the signed-in user.
Trade-offLess polished UI components than dedicated auth services.
At a glance
| Used by | 336 makers' products · 14 open-source projects | 13 makers' products |
|---|---|---|
| Cost at default usagemonthly active users 10k MAU | $0/mo Hobby | $0/mo Free |
| Moved to it on GitHubpull requests since Oct 2024 | 54 from Supabase | 53 from Clerk |
| Downloads | 2.3M/wk+53% vs npm | 25.4M/wk+91% vs npm |
| Pricing | Free tier by monthly active users; paid plans add features and seats. · paid from $25/mo | Free tier (inactive projects pause); paid plans per project plus usage. · paid from $25/mo |
| Free tier | Yes | Yes |
| Open source | No | Yes · self-hostable |
| Incidents, 90 daysfrom its status page | 9 | 25+ (6 major) |
Which makers on your framework pick
Makers' products built with each framework that chose either one, for authentication.
| Framework | |||
|---|---|---|---|
| 176 | 5 | All 211 Next.js products' picks → | |
| 8 | 2 | All 15 React products' picks → | |
| 8 | 1 | All 12 Astro products' picks → |
New launches vs older products
A tool that came first has products from every year since, so its total runs ahead. Here is what products launched each year chose, as a share of those that made the authentication decision (by the year they launched on Product Hunt).
| Launched | Products | ||
|---|---|---|---|
| 2024 | 76% 68 | 3% 3 | 89 |
| 2025 | 79% 83 | 4% 4 | 105 |
| 2026 | 84% 82 | 2% 2 | 98 |
Cost as you grow
Both cost $0 up to 50k MAU; from 100k MAU Supabase costs less ($25 vs $1,025); and still does at 1M MAU ($2,950 vs $17,225). They're different kinds of tool — hosted service and bundled with your backend — so the prices don't buy the same thing.
The numbers, plan by plan
| Monthly active users | Clerk | Supabase |
|---|---|---|
| 100 | $0 Hobby | $0 Free |
| 1,000 | $0 Hobby | $0 Free |
| 5,000 | $0 Hobby | $0 Free |
| 10,000 | $0 Hobby | $0 Free |
| 25,000 | $0 Hobby | $0 Free |
| 50,000 | $0 Hobby | $0 Free |
| 100,000 | $1,025 Pro | $25 Pro |
| 250,000 | $3,725 Pro | $513 Pro |
| 1,000,000 | $17,225 Pro | $2,950 Pro |
Who moves from one to the other
Public pull requests on GitHub since Oct 2024 whose title says "Clerk to Supabase" or the reverse — real code changes, by developers in general rather than makers only.
- Migrate SpendWise from Supabase to Neon and Clerkderlinromero/SpendWise · 2026-09-28
- feat: migrate authentication from Supabase Auth to Clerkfreathedge/operationshub · 2026-09-25
- Migrate Supabase Auth to Clerk AuthenticationArxov/farmer-procurement · 2026-09-19
- Switch auth from Supabase to Clerkjefebcn/hyroxsetup · 2026-09-10
- Migrate authentication from Supabase to Clerk with email OTPzarintasnimfema7/Campus_Path · 2026-09-03
- Migrate authentication from Supabase to Clerk with email OTPzarintasnimfema7/Campus_Path · 2026-09-03
- Migrate web auth from Supabase Auth to Clerk (keep Supabase DB)noahpeden/halteres.ai · 2026-08-30
- Migrate authentication from Supabase to ClerkSchroederNathan/Medley · 2026-08-07
- feat: migrate auth from Supabase Auth to Clerkvidhyaranganathan/myedbc-course-explorer · 2026-07-30
- Migrate authentication from Supabase Auth to Clerk (Phases 1-5)azhar-zuberi/digital-hangar-mobile · 2026-07-29
- Migrate customer web auth from Clerk to Supabaseevery1hatestaha-png/busniessOS · 2026-09-27
- Connect Clerk users to Supabase profileshimavolt3569-design/goreto · 2026-09-25
- Migrate from Clerk to Supabase AuthDRG-X/Vaulto · 2026-09-20
- Connect Clerk to Supabase via third-party auth and link profilesAadvait-Hirde/KTP-Indiana · 2026-09-09
- feat: migrate from Clerk+NeoDB to Supabase Auth+DBcrewcircle/crewRoster · 2026-07-23
- Migrate portal authentication from Clerk to Supabase Authtoddkidneyjourney1/lab-test · 2026-07-06
- Migrate auth from Clerk to native Supabase Authjonasbager/applicator-hub · 2026-06-18
- Migrate from Clerk to Supabase AuthMasterSoler/mcp-chat · 2026-06-11
- SCRUM-21 Sync Clerk Users to Supabase DatabaseAAK-Developers/centraleats-backend · 2026-06-08
- test(e2e): migrate auth mock from Clerk to Supabase AuthBonham-Technologies/ESCAPESUITE · 2026-06-08
What makers say
Makers on using it for authentication, from Product Hunt and Starter Story interviews, each linked to the source. Products with a page of their own and fuller notes first.
I would ship as fast if I wasnt using Clerk. I use it for all my products, has a good free tier and it's customisation is so advanced as you want it to be, su all scenario's are achievable. Su
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
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.
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!
Supabase makes backend work a breeze with instant APIs and real-time sync. We skip building auth and complex DB setups, letting us launch features faster and focus on what really matters.
Supabase helped us set up our backend, database, auth, and edge functions in minutes. It’s the easiest way to power a real product without the usual backend headache.
Loved and watch-outs
Themes that recur in makers' words and Hacker News comments, each linked to what it summarises.
- Sign-up, sign-in, sessions and social login get wired in an afternoon instead of a sprint. PHPH 2
- Organizations, roles and billing come built in, covering multi-tenant B2B apps without custom identity work. PHPH 2
- Prebuilt UI components, including profile and settings pages, look polished out of the box. PH
- One project covers Postgres, auth, storage and realtime, so a solo founder ships without stitching vendors or hiring a backend team. PHPH 2PH 3PH 4
- It is real Postgres with SQL, row-level security and pgvector rather than a proprietary store. PHPH 2PH 3PH 4
- Open source and self-hostable, which reduces vendor lock-in. PHPH 2HNPH 3
Who uses each
What makers pair each with
Neither quite right?
See the whole authentication decision →Questions
Clerk or Supabase: which do makers choose?
Of the 422 makers' products we know the authentication of, 336 chose Clerk (80%) and 13 Supabase (3%); 1 uses both. Among the 98 launched in 2026, Clerk is in 84% and Supabase in 2%, against 76% and 3% of those launched in 2024 or earlier. They're different kinds of tool, hosted service and bundled with your backend, so the counts don't measure the same choice. On GitHub, 53 public pull requests moved projects from Clerk to Supabase, and 54 the other way. Choose Clerk if you're on Next.js or React and want sign-in, profiles and teams working today; choose Supabase if your data is already in Supabase or Firebase.
When should I pick Clerk over Supabase?
Pick Clerk if: You're on Next.js or React and want sign-in, profiles and teams working today.
When should I pick Supabase over Clerk?
Pick Supabase if: Your data is already in Supabase or Firebase.
Which is cheaper, Clerk or Supabase?
At monthly active users 10k MAU: Clerk $0/mo (Hobby), Supabase $0/mo (Free), at list prices.
How do Clerk and Supabase compare in cost as you grow?
Both cost $0 up to 50k MAU; from 100k MAU Supabase costs less ($25 vs $1,025); and still does at 1M MAU ($2,950 vs $17,225). Cheapest usable plan at each scale, at list prices.
Are people switching from Clerk to Supabase?
Public GitHub pull requests since 2024-10-02: 53 from Clerk to Supabase, 54 from Supabase to Clerk.