Supabase Auth emails with Brevo: check both sending limits before launch

October 16, 2026

Receiving a Supabase Auth email during development does not prove a new customer can receive it after launch. Check the built-in service's recipient restrictions, then evaluate custom SMTP and the email provider's separate allowance. For Brevo, an hourly Supabase limit and a daily Brevo limit must both fit your workload; neither is a guarantee of actual inbox delivery.

A new guide for an existing deployment question

Brevo's October 7 developer index added a Supabase SMTP integration guide; this article was reviewed October 10. That is a documentation event, not proof that SMTP first became available that day. The integration requires a domain you can verify and management access to both sides. Actual feature activation, DNS control and account eligibility were not checked here.Sources: Brevo — developer changelog · Brevo — SMTP for Supabase Auth

Supabase describes its built-in email service as restricted to team addresses, currently two emails per hour, and unsuitable for production. A successful test to a team member therefore does not establish delivery to arbitrary customers. Record who received the test and which sending route was used before judging a production authentication problem.Sources: Supabase — custom SMTP

There are two independent limits

Supabase's custom SMTP starts with a limit of 30 emails per hour that can be adjusted. Brevo Free separately allows 300 emails per day. A higher provider allowance does not automatically increase the application's limit, and changing the application setting does not remove the provider quota. Check the actual settings and approved changes in your own accounts.Sources: Supabase — custom SMTP · Brevo — pricing plans

As a hypothetical workload, 40 signup emails arriving in one hour are below 300 for the day but above an unchanged 30-per-hour setting. This arithmetic illustrates why time windows matter; it is not a test of queueing, retries or delivery. A daily total alone cannot determine what happens during a launch-time burst or a password-reset peak.

Checks before connecting production

  1. Confirm domain ownership, DNS control and administrator access to both services. Brevo's guide requires a verified sending domain and an SMTP key, which is different from an API key. Treat credentials as private; this article does not collect, create or rotate them.Sources: Brevo — SMTP for Supabase Auth
  2. Estimate hourly peaks and the daily total separately. Distinguish signup confirmations and password resets from marketing mail, including other uses of the provider allowance. Compare both sides' actual limits rather than copying a public Free number as your deployed configuration.
  3. Ask the product-testing owner to verify a controlled non-team recipient, confirmation, password-reset flow and relevant sending logs in a lawful test environment. Keep server acceptance and actual receipt separate. LessWork Lab did not send or receive test messages for this guide.
  4. Record failed delivery and the responsible service before a production change. Do not solve a sending failure by casually disabling confirmation emails. Any authorized quota adjustment still needs a check against provider capacity, account conditions and the intended authentication behavior.

A Free provider is not a free whole app

Brevo's public help shows Free at $0 with 300 daily emails and optional Starter from $9 per month. Country, currency code, taxes and needed capacity remain unverified. Your actual Supabase plan, usage, domain and DNS costs are unknown. Do not record zero total application cost merely because one email-provider plan is free.Sources: Brevo — pricing plans

No negotiated reader code or verified promotional deadline was obtained. Before paying, find the constraint you actually need to change: recipient restrictions, hourly application capacity, daily provider capacity or another observed failure. Buying more email allowance does not itself prove delivery, resolve domain configuration or authorize a quota increase elsewhere.

Two questions about sending

Why can the team receive a message while a customer cannot? The built-in service is documented for team addresses. Confirm the route and actual error before assuming the customer's inbox caused the failure. This guide has not diagnosed a reader's deployment.Sources: Supabase — custom SMTP

Does custom SMTP remove all limits? No: the documented starting 30-per-hour application limit and Brevo's separate 300-per-day Free allowance remain different checks. Their real settings and any granted increases need verification. Cross-country delivery rate and real inbox outcomes were not measured.Sources: Supabase — custom SMTP · Brevo — pricing plans

Official documentation reviewed October 10, 2026; no product test, delivery guarantee, time saving or ROI established. Brevo's public affiliate rules require review and website traffic and prohibit PPC. This applicant's CPA, approval, valid link, commission and Taiwan commercial payout are unverified. This candidate does not create a paid recommendation or affiliate CTA.Sources: Brevo — affiliate eligibility · Brevo — referral and promotion restrictions

Official sources

Reviewed:

Related reading