Updated
Best authentication providers to use with Supabase in 2026
Learn which authentication providers you can use with Supabase in 2026.
Authentication is the part of an app that decides who a user is before any data is read or written.
Supabase includes its own authentication service, Supabase Auth, and also accepts tokens from the following third-party identity providers. You can use them through third-party auth, alongside Supabase Auth or on their own. Supabase accepts their JSON Web Tokens (JWTs) to access the Data API, Storage, Realtime, and Edge Functions.
Supabase Auth
Supabase Auth is the built-in authentication service for Supabase projects. It supports email and password sign-in, magic links, phone sign-in, OAuth providers, and more. Its tokens work directly with the Data API, Storage, and Row Level Security policies without an extra integration step.
If you are starting a new Supabase project, Supabase Auth is the best fit.
Clerk
Clerk is a user management platform for web and mobile apps. It provides prebuilt sign-in components, session management, and organization support for multi-tenant apps.
If you already have a production app using Clerk and want to use the rest of the Supabase Platform, see the Clerk integration with Supabase.
Firebase Auth
Firebase Auth is Google’s identity service within the Firebase platform. It supports email and password, phone, and federated sign-in with social providers.
If you already have a production app using Firebase Auth and want to use the rest of the Supabase Platform, see the Firebase Auth integration with Supabase.
If you want to migrate from Firebase Auth to Supabase Auth, see the Firebase Auth migration guide.
Auth0
Auth0, owned by Okta, is an identity platform for consumer and enterprise apps. It offers hosted sign-in pages, social and enterprise connections, and multi-factor authentication.
If you already have a production app using Auth0 and want to use the rest of the Supabase Platform, see the Auth0 integration with Supabase.
If you want to migrate from Auth0 to Supabase Auth, see the Auth0 migration guide.
Amazon Cognito
Amazon Cognito is AWS’s identity service. Its user pools handle sign-up and sign-in, and it works with AWS Amplify on the client. It fits teams whose infrastructure already runs on AWS.
If you already have a production app using Amazon Cognito and want to use the rest of the Supabase Platform, see the Amazon Cognito integration with Supabase.
WorkOS
WorkOS provides enterprise features for B2B software, including single sign-on, directory sync, and AuthKit for user authentication.
If you already have a production app using WorkOS and want to use the rest of the Supabase Platform, see the WorkOS integration with Supabase.
Custom OIDC providers
If your identity provider isn’t listed here but supports OpenID Connect (OIDC), you can use it with Supabase.
For the full setup, including provider requirements, the Management API option, client configuration, and Row Level Security policies, see Custom OIDC provider.
Other providers
You can also use Supabase as a standalone Postgres database, entirely separate from the rest of the Supabase Platform. You can set up your own authentication and authorization flows using any provider.