Auth · June 2026

We Switched From Clerk to Supabase Auth and Saved $1,800/Month

June 5, 2026 · 9 min read

At 10,000 users Clerk was free. At 50,000 users our bill was $800/month. At 100,000 it would have been $1,825/month. We switched to Supabase Auth and now pay $25/month for the same functionality. Here is how the math works and when Clerk is still worth it.

The Auth Provider Pricing Nobody Talks About

Every auth provider has a "free tier" that makes them look cheap on the pricing page. The real cost emerges at scale. At 100K monthly active users:

ProviderFree MAUPer MAU after50K MAU100K MAU
Supabase AuthCHEAPEST50,000$0.00325$0$25
Firebase Auth50,000$0.0055$0$275
Clerk10,000$0.02$800$1,825
Auth0 (Okta)7,500$0.07$2,975$5,000+

Same authentication. Same JWT sessions. Same social providers. The 73x price difference is purely a per-MAU billing model decision.

Why Clerk Gets Expensive Fast

Clerk's $0.02/MAU rate sounds tiny. Then you do the math: 100,000 users × $0.02 = $2,000. Minus the 10,000 free MAU allowance = $1,800. Plus the $25 base plan fee = $1,825/month.

The inflection point is brutal. At 9,999 MAU: $0. At 10,001 MAU: $0.02. Growth from 10K to 100K means your auth bill goes from $0 to $1,800. Most SaaS products don't notice until they're already at 50K+ users.

The 10K cliff

Clerk is free under 10K MAU. Once you cross that threshold, you are paying $0.02/user/month on every user above 10K. At 50K users that is $800/month. At 100K that is $1,825/month.

Supabase Auth: What You Give Up

Supabase Auth does not have Clerk's polished pre-built components. There is no drag-and-drop sign-in modal. You build login UI with their SDK. For teams already using Supabase for their database, this is a non-issue — the SDK integrates naturally. For teams starting fresh, Clerk's DX advantage is real and worth paying for until you hit scale.

When to Choose Each Provider

SituationRecommendationReason
Early stage, under 10K MAUClerkFree + best DX
Using Supabase DB alreadySupabase AuthEssentially free, native integration
Growing past 50K MAUSupabase Auth or FirebaseClerk becomes $800+/mo
Enterprise B2B with SSOWorkOS1M MAU free, SSO-first
Complex compliance (HIPAA, SOC2)Auth0Compliance-first, expensive

Calculate your auth cost at your current and projected MAU

Calculate My Auth Cost →
What is the cheapest auth provider in 2026?+

Supabase Auth is the cheapest at scale: 50,000 free MAUs then $0.00325/MAU. At 100K users it costs ~$25/month. If you are already using Supabase for your database, auth is essentially free.

Clerk vs Auth0 — which is better?+

Clerk wins for developer experience and Next.js/React apps. Auth0 wins for enterprise compliance, SAML SSO, and complex B2B requirements.

Is migrating from Clerk to Supabase Auth difficult?+

Moderately difficult. You need to export users, recreate social provider connections, and rebuild any pre-built Clerk UI components. Budget 1-3 days depending on your app complexity.

Auth Provider Migration: What to Expect and How to Reduce Risk

Switching authentication providers is one of the highest-risk infrastructure changes a SaaS product can make. Users sessions, social login connections, MFA settings, and password hashes are all tied to your current provider. A botched migration can lock users out of their accounts. Here is how to migrate safely.

Never do a hard cutover. Run both providers in parallel for at least 2-4 weeks. Configure your auth middleware to check the new provider first; fall back to the old provider if the user does not exist yet. Migrate users lazily on next login, or in batches during low-traffic windows. This eliminates the all-or-nothing risk that makes auth migrations scary.

Social login is the hard part. Each OAuth provider (Google, GitHub, Apple) has its own rules about transferring app credentials. In most cases, you can reuse your existing Google OAuth client ID and secret with Supabase — users will not notice the switch. But some providers require re-authorization by the end user, which creates friction. Test every social provider in staging before touching production.

Password hash migration. Clerk uses bcrypt by default; Supabase Auth supports bcrypt import. This means you can export password hashes from Clerk and import them into Supabase without forcing users to reset passwords. Confirm hash compatibility and test with a small cohort of users before full migration.

Plan for MFA re-enrollment. TOTP secrets (authenticator app codes) are typically not exportable for security reasons. Users with MFA enabled will need to re-enroll after migration. Communicate this in advance via email, provide a clear re-enrollment flow, and temporarily increase session duration so users are not immediately locked out. Budget 2-3% support ticket volume increase during the migration window. Use the auth provider cost calculator to model your specific MAU trajectory and identify the crossover point where migration ROI is positive.