External Auth (BaaS)
Use an external Backend-as-a-Service — Supabase, Convex, or Firebase — for authentication instead of built-in Better Auth.
Overview
If you already use a Backend-as-a-Service, or want real-time data from one, SiteKnock can delegate authentication to Supabase, Convex, or Firebase instead of the built-in Better Auth.
Enable it
"auth": {
"enabled": true,
"authBaas": {
"enabled": true,
"provider": "supabase", // "supabase" | "convex" | "firebase"
"emailDelivery": "app", // "app" | "baas"
"resetPassword": true,
"socialProviders": ["github", "google"]
}
}
Supported providers
| Provider | Description |
|---|---|
| Supabase | Supabase Auth with email and social sign-in |
| Convex | Convex Auth integration with real-time data |
| Firebase | Firebase Authentication |
Email delivery
Choose who sends auth emails (verification, reset, magic link):
emailDelivery: "app"— SiteKnock sends them through your configured email provider.emailDelivery: "baas"— the provider handles delivery (for example, Supabase's built-in email).
Built-in vs. external auth
| Your situation | Recommendation |
|---|---|
| Standard SaaS, full control in one place | Built-in Better Auth |
| Already invested in Supabase / Firebase | BaaS |
| Need real-time data from the provider | BaaS (Convex / Firebase) |
| Want the simplest setup | Built-in Better Auth |
Configure in Studio
Toggle external auth in the auth feature settings, select the provider, and add the provider credentials under integrations.
Next steps
Was this page helpful?