Broadcast to email
A release notes mailing list you never have to run.
Your public story page grows the list; Yanib does the rest. Subscribers verify by email, get every published release, and can leave with one click, no newsletter tool, no CSV exports.
Free forever. No credit card.
How it works
Three steps. Two minutes.
Connect
Connect a repo and enable its public story page. The subscribe form is already on it, rate limited and spam resistant out of the box.
Review
Each release tag becomes an AI draft from the real commits and PRs. You edit and approve what lands in inboxes.
Broadcast
Publish once. Verified subscribers get the release by email at the same moment Slack, Discord, and your story page get it.
Why the broadcasting layer
Email subscribers is one spoke of nine. Every channel gets the same reviewed update, from one publish.
- Double opt in: addresses are verified before they ever receive a release
- One click unsubscribe in every email, list hygiene is built in, not bolted on
- The email pairs the release card with a text summary that remains visible when images are blocked
- The subscribe form lives on your public story page, the list grows while you ship
Frequently asked questions
Do I need Mailchimp or another newsletter tool?
No. Yanib hosts the subscribe form, verifies addresses, sends the release emails, and handles unsubscribes. There's nothing to wire together.
How do people subscribe?
Through the subscribe box on your public story page. They confirm via a verification email, so the list only ever contains real, consenting readers.
Can subscribers leave easily?
Yes, every email carries a one click unsubscribe link. Clean exits protect your sender reputation and are simply the right thing to do.
What does the email look like?
The release title, the visual release card, and the full story entries as text. The text is always present, so the email works even in clients that block images.