# Clerk vs Supabase Auth: pricing metric, SSO cost and what each one is

> Clerk bills Monthly Retained Users (a narrower metric than MAU); Supabase Auth bills plain MAU and ships inside a Postgres backend. Pricing, SSO cost and the real difference compared.

Source: https://scribase.com/clerk-vs-supabase-auth

Clerk is a standalone auth product with its own UI components and dashboard; Supabase Auth is one feature of a Postgres backend. They answer different questions, and they bill on different metrics — Clerk's Monthly Retained Users versus Supabase's plain Monthly Active Users — so a straight per-user price comparison is misleading without saying which metric each number is.

## What each one actually is

Clerk is a dedicated authentication and user-management product: pre-built sign-in components, a user dashboard, organizations, and its own billing metric. It sits in front of whatever backend and database you already run.

Supabase Auth is GoTrue, the auth server bundled into a Supabase project alongside Postgres, Storage and Realtime — one feature of a backend, not a separate product with its own dashboard product line.

## The billing metric is not the same word twice

Clerk bills Monthly Retained Users (MRU): a user counts only once they "visit your app in a given month at least one day after signing up" — so a user who signs up and never returns in a later session is not an MRU at all. Supabase Auth bills plain Monthly Active Users (MAU): any user active in Auth that month, full stop, no same-day exclusion.

That difference means the two numbers are not directly comparable even when they look alike. An app with a lot of one-time sign-ups and no return visits looks cheap on Clerk's MRU metric and ordinary on Supabase's MAU metric.

## Sources

- [Clerk: Pricing](https://clerk.com/pricing)
- [Supabase: Pricing](https://supabase.com/pricing)

## Pricing and SSO, side by side

_Clerk and Supabase published pricing pages, checked live 2026-11-18_

|  | Clerk | Supabase Auth |
| --- | --- | --- |
| Free tier | 50,000 MRU/app, Hobby plan, no SSO | 50,000 MAU/app included |
| Paid tier entry | $25/mo (Pro), 50,000 MRU included, then $0.02/MRU | $25/mo (Pro project), 100,000 MAU included, then $0.00325/MAU |
| SSO (SAML) | Not on Hobby; Pro/Business: 1 connection included, then $75/mo each | Pro/Team: 50 MAU included, then $0.015/MAU; Enterprise custom |
| Ships with | Standalone auth product, own dashboard, organizations | Postgres, Storage, Realtime and REST in the same project |

## Sources

- [Clerk: Pricing](https://clerk.com/pricing)
- [Supabase: Pricing](https://supabase.com/pricing)

## Where Scribase fits

Scribase Auth runs the same GoTrue-compatible API as Supabase, inside a project priced flat per month — $5 on Hobby or $25 on Pro — not metered per user on either the MRU or the MAU definition. Clerk's own migrate path creates every user with a one-time password (Clerk's Backend API has no endpoint that returns a portable password hash on any plan), the same real limitation whether the destination is Scribase or anywhere else.

## Sources

- [Scribase pricing](https://scribase.com/pricing)

## FAQ

**Is Clerk cheaper than Supabase Auth per user?**

Not a fair comparison at face value: Clerk's free and $0.02-overage numbers are priced in MRU (users retained past their sign-up day), Supabase's are priced in plain MAU. An app with many one-time sign-ups shows fewer Clerk-billable users than Supabase-billable ones for the same traffic.

**Does Supabase Auth include pre-built UI components like Clerk does?**

Supabase ships client SDKs and auth helpers, not a packaged drop-in UI component library the way Clerk's <SignIn /> components are; teams typically build their own screens against Supabase Auth's API.

**Can I move Clerk users to Supabase Auth or Scribase Auth with their passwords intact?**

No, on either destination. Clerk's Backend API does not return a portable password hash on any plan, so a migrated user gets a new one-time password and resets it on first sign-in, regardless of where the account moves to.

**Which one is the right pick if I already run Postgres?**

If the backend is already Postgres (Supabase, Neon, Scribase or self-hosted), the auth that ships inside that same project avoids a second vendor and a second dashboard; Clerk is the better fit when the backend is something other than Postgres, or when its specific UI components and organization features are the deciding factor.

## Related

- [Clerk alternative](https://scribase.com/clerk-alternative)
- [Clerk pricing per MAU](https://scribase.com/clerk-pricing-per-mau)
- [Clerk rate limit exceeded](https://scribase.com/clerk-rate-limit-exceeded)
- [Clerk webhook signature verification failed](https://scribase.com/clerk-webhook-signature-verification-failed)
- [Clerk session token expired](https://scribase.com/clerk-session-token-expired)
- [Migrate from Clerk](https://scribase.com/migrate/clerk)
- [Firebase Auth vs Supabase Auth](https://scribase.com/firebase-auth-vs-supabase-auth)
- [Supabase alternative](https://scribase.com/supabase-alternative)
- [Pricing](https://scribase.com/pricing)