BroadcastMail vs
Loops is for automated lifecycle emails triggered by user events. BroadcastMail is for broadcast campaigns sent straight from your Supabase database. They do different things.
Who Loops is for
Loops is a lifecycle email tool for SaaS products. You define triggers in your app (user signed up, user upgraded, trial expired) and Loops sends the right email automatically. It has a visual flow builder, branching logic, and a contact database that syncs from your app through its API or SDK.
It's built for teams who want to automate onboarding sequences, re-engagement flows, and event-driven email at scale. If that's what you need, Loops is genuinely good at it.
Who BroadcastMail is for
BroadcastMail is for developers who want to send a campaign to their Supabase users without setting up a sync, an SDK, or an automation flow. Connect your database, write your email, pick your audience, send.
No triggers, no sequences, no contacts to manage. Your users live in your database, and that's where BroadcastMail reads them from.
The core difference
Loops maintains its own copy of your contacts and reacts to events your app fires. BroadcastMail reads your Supabase database directly and sends when you tell it to. One is event-driven and asynchronous; the other is on demand.
Neither approach is wrong. They solve different problems.
Side by side
| Feature | BroadcastMail | Loops |
|---|---|---|
| Primary use case | Broadcast campaigns | Lifecycle automation |
| User data | Read from your Supabase database | Synced into Loops |
| Setup | Connect your database, done | SDK integration and flow setup |
| Supabase native | Yes | No (API sync required) |
| Event-driven sends | No | Yes |
| Visual flow builder | No | Yes |
| Email provider | Your own Resend key | Loops infrastructure |
| Branding on emails | Never | Free tier only |
| Free tier | 500 recipients/month | 1,000 contacts |
| Paid plans from | $9/month | $49/month |
Loops pricing as of October 2026. Verify on their site.
Where Loops genuinely wins
- Onboarding sequences that fire automatically when a user signs up
- Trial expiry emails, win-back campaigns, inactivity nudges
- Anything where the email should trigger from user behaviour
- A visual flow builder with conditional logic
- Dedicated contact profiles with event history
- A larger ecosystem of integrations
Where BroadcastMail wins
- Emailing your Supabase users without syncing them anywhere or integrating an SDK
- Broadcast campaigns: product updates, feature announcements, one-off messages to a segment
- Filtering by columns in your own database without firing events
- Delivery through your own Resend key, so the sender reputation is yours
- No branding on your emails at any tier
- Getting something out the door in under five minutes
On "Powered by Loops"
Loops adds its branding to emails sent on the free tier. It's common practice and a reasonable business decision. BroadcastMail doesn't do this at any tier. Your emails look like they came from you, not from the tool you used to send them.
Do you need both?
Possibly. Some teams use Loops for lifecycle automation and BroadcastMail for broadcasts. In practice the use cases rarely overlap.
If you're early stage and just want to email your users without a two-day integration, start with BroadcastMail. Add Loops when you're ready to build automated flows.