Reviewers mostly see Resend as a simple, developer-first way to handle transactional email, with fast setup, clean APIs, good logs, and reliable deliverability showing up again and again. Users say it reduces the usual DNS, config, and maintenance hassle, and many pair it with React Email or modern serverless stacks. Makers of
Refgrow and
Rectify say they use it for onboarding, alerts, payouts, and support emails because it “just works.” Complaints are narrower: thin Python examples, missing unsubscribe or broadcast workflows, domain setup friction, and one report of severe sending delays.
QA.tech
It's launch week at @Resend - a week of announcing new features every day.
So far, the team announced Automations, launched an AI Email Editor, and just released their new CLI.
S/O to @zenorocha and team - Looking forward to what's next!
Resend
@fmerian thanks for hunting it!
If anyone wants to follow along this Launch Week, check this out: https://resend.com/launch-weeks/6
Product Hunt
@curiouskitty Funny you should ask because, as part of my current project I was actually referred and recommended to use Resend. I had never heard of it but, I decided to consider the recommendation and the configuration was simply "SIMPLE". My previous experience with sendgrid has been somewhat interesting but my exposure to Resend has been a pleasant experience. Keep doing what you guys do, it's a great tool!
React Email support in the CLI is smart. debugging email templates locally before sending has always been painful. does this let you preview the rendered output or just validate the components?
Resend
@piotr_pasierbek that's mostly for sending using the CLI. For preview and validation, you would still use React Email's local development server.
webhook listening from terminal is clever for development. beats spinning up ngrok every time you want to test email events. how does it handle multiple webhook endpoints if you're working on different projects?
Resend
@piotreksedzik you would need to setup a different terminal session for each webhook listening.
the AI agent skills feature is interesting - what kind of email workflows are you seeing agents handle best? we've been automating a lot of our healthcare product notifications and curious how this compares to just hitting the API directly
@zenorocha the agent Skills feature is interesting — are these MCP-compatible or a custom spec? I'm thinking about agent pipelines where email is a side-effect trigger, and protocol compatibility matters a lot.
nice to see a CLI that treats AI agents as a first-class user. curious what the skills format looks like — is it a standard spec or something resend-specific?