Clerk or Supabase Auth?

Supabase Auth comes with your database and costs less per user at scale; Clerk adds ready-made screens and B2B features on top. Here’s what each costs at real user counts, how each works with row-level security, and how to choose.

By the NestedBit team · Updated

Clerk vs Supabase Auth in short

If your database is on Supabase, you already have Supabase Auth: it comes with every project. So the real question is whether Clerk is worth adding on top.

  • Supabase Auth keeps your users in your own Postgres database and works with row-level security out of the box, at no cost beyond the users your plan includes. You build most screens yourself, and there are no organizations.
  • Clerk gives you prebuilt sign-in, profile, MFA and organization components, plus invitations, SSO and directory sync. It plugs into Supabase as a third-party auth provider, so row-level security still works, reading Clerk’s token. Past 50,000 retained users it charges $0.02 each, against Supabase’s $0.00325 past 100,000.

The prices on this page come from each vendor’s pricing page, checked on 10 Nov 2026, through the same engine as the free Auth Provider Picker. Vendors change plans often, so confirm the plan you pick on their site before you commit.

Clerk vs Supabase Auth pricing

They count users differently. Supabase bills monthly active users. Clerk bills monthly retained users: people who visit in a month at least a day after signing up. With Clerk, Supabase still counts your users as third-party MAUs, with the same allowances and price as its own. The estimates below treat all these counts as equal.

Supabase Auth is free up to 50,000 users on the Free plan. Pro is $25 a month with 100,000 included, then $0.00325 a user, and that $25 also pays for your database. Clerk’s Hobby plan is free up to 50,000 retained users, without MFA, passkeys or SSO. Pro is $25 a month, or $20 billed yearly, with 50,000 included, then $0.02 a user, less in volume.

Monthly cost of auth and the Supabase project together, each vendor’s cheapest plan that covers the need. The Clerk column adds the Supabase plan your project needs for that many users:

ExampleSupabase AuthClerk + Supabase
Consumer app, password and social sign-in
10,000 users $0 Free $0 Clerk Hobby, Supabase Free
50,000 users $0 Free $0 Clerk Hobby, Supabase Free
100,000 users $25 Pro $1,050 Clerk Pro, Supabase Pro
250,000 users $512.50 Pro $4,237.50 Clerk Pro, Supabase Pro
Consumer app with authenticator-app MFA
1,000 users $0 Free $25 Clerk Pro, Supabase Free
10,000 users $0 Free $25 Clerk Pro, Supabase Free
100,000 users $25 Pro $1,050 Clerk Pro, Supabase Pro
B2B SaaS with organizations and SAML SSO
2,000 users (300 through SSO), 20 customers, 1 SSO connection $28.75 Pro $125 Clerk Pro, Supabase Free
5,000 users (2,000 through SSO), 50 customers, 5 SSO connections $54.25 Pro $425 Clerk Pro, Supabase Free
10,000 users (4,000 through SSO), 150 customers, 8 SSO connections, custom roles $84.25 Pro $700 Clerk Pro, Supabase Free

Where the gap comes from: Supabase includes authenticator-app MFA on every plan, while Clerk needs Pro for it, so MFA costs $25 a month with Clerk from the first user. Past 50,000 users, Clerk charges $0.02 each: 100,000 users come to $1,025 a month on Clerk alone, on top of the Supabase Pro plan they need either way.

For B2B the pricing shapes differ. Supabase prices SAML sign-in per user: Pro includes 50 SSO users, then $0.015 each, so 2,000 people signing in through SSO add $29.25. Clerk prices per connection: one on Pro, then $75 a month each. Each B2B row also includes Clerk’s $100 a month Enhanced B2B add-on, which links SSO connections to organizations. The Supabase figures leave out work: it has no organizations or invitations, which you build yourself, and no directory sync.

Supabase’s Free plan pauses a project after a week of inactivity, so most live apps pay for Pro whichever auth they use. None of this includes tax, database compute beyond Supabase’s included credit, SMS charges or yearly discounts. Put your own numbers into the picker, which also shows the line items behind each total and 11 other providers.

How each works with row-level security

If your data lives in Supabase, this matters most: row-level security decides what each request may read, based on the token it carries.

With Supabase Auth, sign-in gives the browser a Supabase token. In a policy, auth.uid() returns the user’s ID: a UUID that matches a row in auth.users, in your own database. Your tables can reference that row with a foreign key, and policies stay short:

-- Supabase Auth: the user's ID is a UUID from auth.users
create policy "Users read their own notes"
on public.notes for select
to authenticated
using ((select auth.uid()) = user_id);

With Clerk, Supabase trusts Clerk’s session tokens as a third-party auth provider. Setup takes three steps: activate the Supabase integration in Clerk’s dashboard, which adds the "role": "authenticated" claim Supabase needs; add Clerk as a provider in Supabase’s auth settings; and create the Supabase client with an accessToken function that returns Clerk’s session token.

Policies then read Clerk’s claims with auth.jwt(). Clerk user IDs look like user_123, and auth.uid() converts the token’s subject to a UUID, so it can’t read them. Instead, compare auth.jwt()->>'sub' with a text column, as Clerk’s Supabase guide does:

-- Clerk: the user's ID is text, such as user_123
create table public.notes (
  id bigint generated always as identity primary key,
  body text not null,
  user_id text not null default auth.jwt()->>'sub'
);
alter table public.notes enable row level security;

create policy "Users read their own notes"
on public.notes for select
to authenticated
using ((select auth.jwt()->>'sub') = user_id);

When a user has an active organization, Clerk’s session token carries its ID and the user’s role in an o claim, so a policy can scope rows to the organization without a membership table:

-- Clerk: members read their active organization's projects
create policy "Members read their organization's projects"
on public.projects for select
to authenticated
using (organization_id = (select auth.jwt()->'o'->>'id'));

Three things catch people out with Clerk:

  • No users in auth.users. The integration doesn’t copy users into Supabase; fill a users table from Clerk’s webhooks if you need one.
  • The old setup is deprecated. Clerk’s JWT template, which shared your Supabase JWT secret, was deprecated on 1 April 2025, but older tutorials still show it.
  • Supabase Auth stays on. It can’t be disabled, so if everyone signs in with Clerk, turn off “Allow new users to sign up” in Supabase. Otherwise a Supabase account’s token also passes policies that only check for a signed-in user.

Whichever you choose, the Supabase RLS Generator checks your migrations or a live project for tables with RLS off and policies that let everyone in, and writes auth.uid() policies for Supabase Auth. New to RLS? Start with how to enable it.

Sign-in screens and components

  • Clerk renders components such as <SignIn />, <UserButton />, <UserProfile /> and <OrganizationSwitcher /> inside your own pages, styled through its appearance settings and themes. They handle MFA enrollment too, backup codes included. On Hobby they show “Secured by Clerk”; Pro and Business let you remove it.
  • Supabase Auth gives you sign-in APIs, and its UI Library has sign-up, login, password-reset and social sign-in blocks for Next.js, React, React Router, TanStack Start, Nuxt and Vue, which the shadcn CLI copies into your project. Nothing ready-made covers MFA, profiles or teams: its MFA docs have you build those screens. The older Auth UI package for React is archived.

Clerk is quicker to ship; with Supabase, every screen past sign-in is yours to build. The Clerk vs Auth0 guide lists the frameworks Clerk covers.

MFA and passkeys

  • Supabase Auth includes authenticator-app (TOTP) MFA free on every project. Phone MFA is $75 a month for the first project on Pro and Team, with codes sent through your own SMS provider. Passkeys are experimental, and Supabase says the API may change without notice.
  • Clerk has SMS codes, authenticator apps and backup codes on Pro and Business (free to try in development), and can require MFA for every user. SMS is $0.01 a message in the US and Canada. Passkeys are on Pro and Business too.

Both put MFA status in the token, so your policies can insist on it. Supabase’s aal claim reads aal2 after a second factor; the second number in Clerk’s fva claim stays -1 until one is verified:

-- Supabase Auth: only sessions that passed a second factor
create policy "Require MFA"
on public.invoices
as restrictive
to authenticated
using ((select auth.jwt()->>'aal') = 'aal2');

-- Clerk: fva's second number is -1 until a second factor is verified
create policy "Require MFA"
on public.invoices
as restrictive
to authenticated
using ((select auth.jwt()->'fva'->>1) != '-1');

Organizations and B2B

  • Supabase Auth has no organizations: you model customers in your own tables and RLS, and the RLS Generator can write the membership table and policies. Roles come from your tables or from claims a Custom Access Token hook adds, from the Free plan up. SAML 2.0 SSO is on Pro and above, with connections added through the Supabase CLI. We found no SCIM directory sync in Supabase’s docs.
  • Clerk includes organizations with Admin and Member roles, custom permissions and invitations, free up to 100 active organizations of up to 20 members each. The Enhanced B2B add-on, $100 a month, adds unlimited members, custom roles, verified domains with automatic invitations, and SSO connections linked to organizations; past 100 organizations, each costs $1 a month, less in volume. Pro includes one SSO connection (SAML or OIDC) and one Directory Sync connection (SCIM or Google Workspace); Clerk starts billing extra Directory Sync connections on 1 January 2027.

Clerk’s pricing page lists unlimited custom roles with the add-on, but its docs cap them at 10 per instance unless support raises it. Lay out the roles your product needs in the RBAC Matrix Builder first, then check each vendor can carry them.

Lock-in and moving later

  • Supabase Auth is open source (MIT) and can be self-hosted with the rest of Supabase. Your users are rows in auth.users: you can query them, with auth.identities, and export the result as CSV.
  • Clerk holds your users, and your database holds their Clerk IDs. You can export users to CSV from Clerk’s dashboard, hashed passwords included, or list them through its Backend API.

Moving from Supabase Auth to Clerk is mostly a database job. Clerk’s open-source migration tool reads a Supabase export, bcrypt password hashes included. But your rows point at UUIDs in auth.users and your policies call auth.uid(), and both must change for Clerk’s text IDs. Clerk suggests a custom session claim that returns an imported user’s old ID, which policies can read instead.

Either way, put the “who is this user?” check in one SQL function your policies call. A move then changes that function and your ID columns, not every policy.

Which one to choose

  • Choose Supabase Auth for a consumer app, especially past 50,000 users, or when you want users in your own database and the option to self-host.
  • Choose Clerk when you want sign-in, profile, MFA and team screens ready-made in React or Next.js, or business customers will soon ask for organizations, SSO and SCIM.
  • Look at both again as you pass 50,000 users, when Clerk’s per-user price starts, and before you sign a yearly contract.

Supabase also accepts Auth0, Firebase Authentication, Cognito, WorkOS and other OpenID Connect providers as third-party auth, and they price very differently. The Auth Provider Picker compares 13 providers on the features you tick and your own user numbers, in your browser.

Free tool · No sign-up

Auth0 Alternatives: Auth Provider Picker

Compare Auth0 alternatives on the features you need and see what each would cost a month at your number of users.

Starts with a free 30-minute intro call, or email hello@nestedbit.com.