Route every Supabase Auth email through SenderKit with one click. Branded templates, your-domain DKIM for the inbox, and no template lock — via Supabase’s Send Email Hook.
Connect your Supabase account once. SenderKit uses the Management API — no SMTP host, port, or passwords to copy.
Choose the project whose auth emails you want to own. SenderKit configures its Send Email Hook for you.
Every auth email now renders from your templates and sends from your authenticated domain. Verify with one test sign-up.
Authorize Supabase once and SenderKit configures the Send Email Hook through the Management API — no copy-pasting host, port, or passwords.
Auth mail is DKIM-signed for your own domain via Amazon SES, with SPF/DMARC alignment — the fix for the Outlook/spam problem Supabase's shared mailer can't solve.
SenderKit renders six editable auth templates, so you brand every auth email instead of living with Supabase's template constraints.
Sign-up, magic link, password recovery, invite, email change, and reauthentication all route through a single hook.
Every send is logged, with delivery, bounce, and complaint webhooks — observability Supabase's built-in mailer doesn't give you.
The same workspace sends transactional email, SMS, and push via the SenderKit API and an MCP server for AI agents.
Most providers plug into Supabase as a custom-SMTP relay — which means Supabase still renders your templates, so you’re stuck with its template constraints and only the sending changes. SenderKit connects through Supabase’s Send Email Hook instead, so it owns both sending and rendering. You get your own branded templates and your-domain DKIM in one move — not just a different SMTP server.
Largely, yes — once you authenticate your sending domain. SenderKit signs auth mail with DKIM for your own domain (via Amazon SES) and aligns SPF/DMARC, which is what actually moves mail out of Outlook and Gmail spam. You publish a few DNS records — SenderKit gives you the exact ones and verifies them — and a zero-DNS shared domain is available to start.
Yes. The Send Email Hook hands every auth email to SenderKit, so Supabase's ~2 emails/hour built-in limit no longer applies — SenderKit governs volume under your plan.
Yes. SenderKit seeds six editable auth templates and renders them itself, so you control the look of every auth email. An existing template with the same name is never overwritten. Unlike a custom-SMTP relay — where Supabase still renders the email — the Send Email Hook lets SenderKit own both sending and templates.
No. Hosted Supabase connects in one click via OAuth. If you self-host, a documented manual setup wires the same Send Email Hook by hand.
The same SenderKit workspace sends transactional email, SMS, and push from the API (and an MCP server for AI agents) — so your receipts, notifications, and OTPs live alongside your Supabase auth mail, with no second integration.
New to deliverability? Read email authentication (SPF/DKIM/DMARC) or why emails go to spam.
Connect your Supabase project, keep your branding, and land auth mail in the inbox. Start free — 500 emails a month, no credit card.
By creating an account, you agree to our Terms.