Some tools you find. Some you build.
A while back I was working on Raisepine, an AI tool for salary negotiation, and at some point I caught myself wondering: okay, when this has users, how do I actually email them? Not transactional stuff, that’s easy. I mean just… reaching out. A product update, an announcement, a nudge to people who signed up and never came back.
I started looking into it properly and honestly couldn’t find anything that felt right. Mailchimp and the like are fine if you’re a marketer, but as a developer you’re immediately fighting the interface. Suddenly your users are living in some third-party list you had to export and import just to send one email. The other direction was tools like Loops, which are great but assume you want sequences and triggers and an automation builder, when really I just wanted to write a message and send it to the people in my database.
The obvious thing (connect to Supabase, pick your users, send) nobody had really built cleanly. So I did.
What I was going for
Honestly, nothing fancy. I wanted something I’d actually enjoy using. Something that respects that your users are in your database and you shouldn’t have to jump through hoops to talk to them. Something that uses your own Resend key so your emails are yours, your sender reputation is yours, and if you ever stop using BroadcastMail nothing is lost.
I kept the scope tight on purpose. There are better tools for lifecycle automation. BroadcastMail does one thing: broadcast email from your Supabase app, and tries to do it really well.
If you want to look under the hood
I care a lot about how things are built, not just what they do. The architecture uses an outbox pattern for reliable fan-out, every decision has a written rationale in DECISIONS.md, and the full schema and security design are documented publicly. If you’re the kind of person who wants to understand what you’re connecting before you connect it, I wrote it all down for you.
Say hi
I’m Laki (Luka), a CS student from Zagreb, building things I think should exist. If you have feedback, hit a bug, or just want to talk about the architecture, I’m genuinely happy to hear from you.