Updated

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.

Ask your AI about this, with this page as the source:ChatGPT ↗Claude ↗Perplexity ↗

Which fits you

Choose Clerk if
  • 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.

Choose Supabase if
  • 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

ClerkSupabase
Used by336 makers' products · 14 open-source projects13 makers' products
Cost at default usagemonthly active users 10k MAU$0/mo Hobby$0/mo Free
Moved to it on GitHubpull requests since Oct 202454 from Supabase53 from Clerk
Downloads2.3M/wk+53% vs npm25.4M/wk+91% vs npm
PricingFree tier by monthly active users; paid plans add features and seats. · paid from $25/moFree tier (inactive projects pause); paid plans per project plus usage. · paid from $25/mo
Free tierYesYes
Open sourceNoYes · self-hostable
Incidents, 90 daysfrom its status page925+ (6 major)

Which makers on your framework pick

Makers' products built with each framework that chose either one, for authentication.

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).

LaunchedClerkSupabaseProducts
202476% 683% 389
202579% 834% 4105
202684% 822% 298

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.

$0$500$2,000$5,000$10,0001001k5k10k25k50k100k250k1M
SupabaseClerkx: monthly active users (MAU) · cheapest usable plan at each point, list prices · try your own numbers
The numbers, plan by plan
Monthly active usersClerkSupabase
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

From each vendor's pricing page: Clerk, Supabase.

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.

Supabase → Clerk54 PRs
When and what they move →
Clerk → Supabase53 PRs
When and what they move →

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.

On Clerk
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
Indie Hacker Stacks, the makerSep 2026 ↗
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
Roll, the makerSep 2026 ↗
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.
WaseiGo, the makerSep 2026 ↗
74 more on the Clerk page →
On Supabase
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!
CatDoes, the makerSep 2026 ↗
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.
Lamatic.ai, the makerSep 2026 ↗
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.
Zivy, the makerSep 2026 ↗
9 more on the Supabase page →

Loved and watch-outs

Themes that recur in makers' words and Hacker News comments, each linked to what it summarises.

Clerk
Most loved
  • 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
Watch-outs
  • Outsourcing auth means a Clerk outage or account problem locks your users out, and the dependency is hard to reverse. HNHN 2HN 3HN 4
  • Costs climb with SSO, MFA, passkeys and branding removal, and some switched to cheaper open-source options. HNHN 2HN 3HN 4
On Product Hunt: 5.0★, 115 reviews · mentioned most: easy integration, comprehensive solution, free tier
Supabase
Most loved
  • 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
Watch-outs
  • Row-level security policies are hard to get right, so many apps end up exposing data publicly. HNHN 2HN 3HN 4
  • Reliability has been shaky for some, and it is not really built for self-hosting in practice. HN
  • Per-project billing adds up for developers running many small side projects. HN
On Product Hunt: 5.0★, 916 reviews · mentioned most: authentication features, easy setup, PostgreSQL integration · complaints: documentation gaps

Who uses each

Used by both — often one replacing the other, or each for a different part of the product

What makers pair each with

With Clerk
With Supabase
FirebaseBundled with your backendMobile and client-heavy apps already using Firebase.vs Supabase →
Better AuthLibrary in your appTypeScript apps that want users and sessions in their own database, at no cost.vs Clerk →vs Supabase →
WorkOSHosted serviceB2B SaaS that will need enterprise SSO and directory sync.vs Clerk →vs Supabase →
Auth0Hosted serviceComplex identity needs and enterprise compliance.vs Clerk →vs Supabase →

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.