We'll put our bias on the table we build email infrastructure, so take this with a grain of salt. But we genuinely think sending email costs more than it should for something this old and commoditized, especially now that the entry-level free tiers are disappearing.
Our hunch: you're mostly paying for deliverability you can't see and a nicer dashboard.
Tell us where we're wrong.
Hey Product Hunt.
In 2009 we started SendGrid because email was broken for developers: sending was
hard, deliverability harder. We shipped a cloud API and left in 2018. Cloud APIs
solved sending. The deliverability problem they were pointed at is still wide
open — a 200 OK from any ESP doesn't mean the email landed.
Here's the part nobody says out loud: per-email pricing is a tax on bad senders,
and clean senders pay it. The price covers the abuse team, the IP warmup, the
complaint handling — not the bytes. Remove the abuse surface and the price collapses.
So we came back. GoodSender is the SendGrid playbook, automated, wired around the
two things that actually move deliverability: permission to get in, engagement to
stay in.
What's in v1:
- Confirmed recipients only, enforced at the endpoint. They click, they're
unlocked for your API key, and you send markdown or HTML in one call. Anyone
who hasn't confirmed simply can't be reached.
- Transactional templates that just ship — MFA, OTP, Login, Order Completed,
New Device. No consent gate.
- Engagement watched, list hygiene automatic. Suppressions are workspace-wide.
Reputation only goes up.
- 100,000 emails a month free. $1 per 100K after. No subscription, no credit card.
- MCP coming soon — run a mailing list from Claude, ChatGPT, or your terminal.
It runs on Laneful — the same stack we built for the world's largest senders.
One firm no: cold outreach. Not at any volume.
Would love your feedback. Grab an API key, send your first email in under 10
minutes, and tell us what's broken.
— The GoodSender team
@givi_pataridze Love the earned deliverbility angle. Email API's usually stop at sending but inbox placement is the real pain. Curious how you measure engagement quality over time?
@dmitrii_volosatov good catch! We split the problem in two: deliverability and engagement quality.
In terms of deliverability - we pull in ESP providers data, handle spam/complaint/unsubscribe events, track domain reputation, inbox-vs-spam trends and constantly monitor IP reputation.
In terms of engagement - we track how each recipient interacts over time, not just per-send. Recent interactions weigh more than old ones, and recipients drift through lifecycle stages as their behavior changes. The point isn't another vanity dashboard - it's so you can actually act on it: sunset the cold addresses before they tank your sender rep, double down on the ones still paying attention.
@i_am_andrii Good approach, thanks for clarify!