This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
Product upvotes vs the next 3
Waiting for data. Loading
Product comments vs the next 3
Waiting for data. Loading
Product upvote speed vs the next 3
Waiting for data. Loading
Product upvotes and comments
Waiting for data. Loading
Product vs the next 3
Loading
Wraps
Amazon SES, set up and run for you in your own AWS
One command deploys Amazon SES into your own AWS account: DKIM, SPF, DMARC, event tracking and suppression. Then Wraps runs it, checking bounce and complaint rates hourly against the lines where AWS pauses accounts. React Email templates, TypeScript workflows, broadcasts, segments, unlimited contacts. Agent sends pass a kill switch, allowlist and caps in your account. Free plan, and AWS bills sending at about $10 per 100k. Open source under AGPL-3.0. You need an AWS account.
Most teams pick Resend or SendGrid because they don't want to deal with Amazon SES. Nobody argues SES is expensive. The objection is the effort: domain auth, an event pipeline, suppression, and watching bounce and complaint rates so AWS doesn't pause you.
Wraps does that part. One command sets it up in your AWS account, and the dashboard runs it after that. Sending goes through your SES directly. Events land in your DynamoDB. Access is an IAM role you can revoke from your side, no stored credentials.
Who it isn't for: if you don't have an AWS account and don't want one, use a hosted API. And only AWS can approve SES production access. Wraps can't skip that step.
Two things I'd like to hear. What made you put off SES? And what would you want watched that isn't on the list yet?
Onward.
About Wraps on Product Hunt
“Amazon SES, set up and run for you in your own AWS”
Wraps was submitted on Product Hunt and earned 5 upvotes and 1 comments, placing #36 on the daily leaderboard. One command deploys Amazon SES into your own AWS account: DKIM, SPF, DMARC, event tracking and suppression. Then Wraps runs it, checking bounce and complaint rates hourly against the lines where AWS pauses accounts. React Email templates, TypeScript workflows, broadcasts, segments, unlimited contacts. Agent sends pass a kill switch, allowlist and caps in your account. Free plan, and AWS bills sending at about $10 per 100k. Open source under AGPL-3.0. You need an AWS account.
On the analytics side, Wraps competes within Email, Email Marketing, Developer Tools and GitHub — topics that collectively have 633.4k followers on Product Hunt. The dashboard above tracks how Wraps performed against the three products that launched closest to it on the same day.
Who hunted Wraps?
Wraps was hunted by Jarod Stewart. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
For a complete overview of Wraps including community comment highlights and product details, visit the product overview.
Jarod Stewart
Hey Product Hunt, I'm Jarod, and I built Wraps.
Most teams pick Resend or SendGrid because they don't want to deal with Amazon SES. Nobody argues SES is expensive. The objection is the effort: domain auth, an event pipeline, suppression, and watching bounce and complaint rates so AWS doesn't pause you.
Wraps does that part. One command sets it up in your AWS account, and the dashboard runs it after that. Sending goes through your SES directly. Events land in your DynamoDB. Access is an IAM role you can revoke from your side, no stored credentials.
Who it isn't for: if you don't have an AWS account and don't want one, use a hosted API. And only AWS can approve SES production access. Wraps can't skip that step.
Two things I'd like to hear. What made you put off SES? And what would you want watched that isn't on the list yet?
Onward.