Why Supabase teams hit a wall on Auth email
Supabase Auth is excellent at generating and verifying OTPs, magic links, and recovery flows. Delivery is the hard part: the default mailer is rate-limited, and most teams then bolt on an ESP that owns the From domain and the inbox reputation.
Zindua takes a different path. You connect Gmail, SMTP, or Outlook (and WhatsApp via QR). Supabase still verifies. We only deliver — from your providers, with one template slug and unified logs.
What “Connect to Supabase” actually does
From Dashboard → Integrations, click Connect to Supabase. After OAuth, you pick a Supabase project. Zindua uses the Management API to write Edge secrets: ZINDUA_API_KEY, template slug, and Auth Hook secrets.
That is the same idea as one-click Integrations elsewhere — except we do not force you onto a third-party ESP network. Auth Hooks call POST /api/v1/send; phone Auth can map SMS to WhatsApp on your Zindua line.
- OAuth into your Supabase org (PKCE)
- Select the project to provision
- Edge secrets pushed automatically
- Deploy Auth Hooks starter + enable Send Email Hook
- Confirm delivery in Zindua Logs