Firebase Auth vs Supabase Auth: the same free MAU number, different products behind it
Firebase Authentication and Supabase Auth both advertise 50,000 free monthly active users — a genuine coincidence worth checking, not assuming. What differs is what sits behind the login: Firestore (NoSQL) behind Firebase Auth, Postgres behind Supabase Auth, and that choice matters more than the auth price once the app needs joins, SQL or row level security.
Last checked November 18, 2026.
Free tier, SSO and phone auth, side by side
| Firebase Auth | Supabase Auth | |
|---|---|---|
| Free MAU (standard auth) | 50K MAUs at no cost (Spark and Blaze) | 50,000 included on Free |
| Free SAML/OIDC MAU | 50 MAUs at no cost | 50 included on Pro/Team; none advertised on Free |
| Paid overage | Google Cloud Identity Platform rates beyond 50K (not quoted on the Firebase pricing page itself) | 100,000 included on Pro/Team, then $0.00325/MAU |
| Phone auth (SMS) | Billed per SMS sent; not available on the free Spark plan | Available via third-party SMS providers configured per project; Supabase does not run its own SMS gateway |
| Database underneath | None included — Firestore or Realtime Database are separate products billed separately | Postgres, in the same project, same billing |
Sources: Firebase: Pricing, Supabase: Pricing
The free MAU number matching is a coincidence that stops mattering fast
Both free tiers land on the same 50,000 MAU figure today, but Firebase Auth has no SQL database bundled with it at any price — Firestore (NoSQL, pay per document read/write) or Realtime Database are separate products with their own bills. Supabase Auth's 50,000 MAU comes attached to a Postgres database in the same project, no separate database bill to add.
Past the free tier, the two diverge in shape, not just price: Firebase's overage sends you to Google Cloud Identity Platform's own rate card (not fully published on Firebase's own pricing page), while Supabase's overage is one flat per-MAU number stated directly on its pricing page.
Sources: Firebase: Pricing, Supabase: Pricing
Where Scribase fits
Scribase Auth runs the same GoTrue-compatible API as Supabase Auth, inside a Postgres project at a flat $5 (Hobby) or $25 (Pro) a month — not metered by MAU at all, free or paid. The Firebase importer moves Firebase Auth users with their modified-scrypt password hashes intact (nobody resets a password), which is the one piece Clerk's own migration path above cannot do, because Clerk never exposes a portable hash on any plan.
Sources: Scribase pricing
Questions people ask
Do Firebase Auth and Supabase Auth really both give 50,000 free users?
Yes, as published on each vendor's own pricing page as of this check: Firebase states "50K MAUs" at no cost for standard authentication, and Supabase states "50,000 included" on its Free plan.
Does the free MAU figure include SSO users on either platform?
No, not the same bucket on either. Firebase prices SAML/OIDC separately at 50 free MAUs; Supabase includes 50 SSO MAU on Pro and Team only, with none advertised on its Free plan.
Can I move Firebase Auth users to Supabase Auth or Scribase Auth without a password reset?
Yes, on Scribase: Firebase stores passwords with a modified-scrypt hash keyed by the project's own signer key, and the importer copies the hash and its parameters, verifying it natively at sign-in so no user needs to reset.
Is phone authentication free on either platform?
No, on either. Firebase bills phone auth per SMS sent and does not offer it on the free Spark plan at all. Supabase routes phone auth through a third-party SMS provider you configure and pay separately; Supabase itself does not run the SMS gateway.