You can try it when you need it.
We have all been there when you have been asked to send a selfie but the one you took is not making it maybe its lighting but you dont look good.And you think that person on the other side is going to judge you and maybe ghost you.So I have created half twin for it, where you post that selfie and it touches it up, fixing up all of your insecurities with a single click so you can send that care...
Because it's built on gRPC instead of just standard REST, you get much better performance and fully typed SDKs. Right now, I have a TypeScript SDK live, and a Go SDK is in the works. But since I’m using Buf, you can basically generate a fully typed client for any language they support.
On Performance & Modes: I’ve implemented two ways to send:
Async (p50 ~34ms): This is for when you just want to fire and forget. You get an instant response, and our infrastructure handles the retries, queuing, and delivery in the background.
Sync: This is for when you need the Message-ID immediately (useful for threading replies or specific logging). You wait for the full handoff, but you get all the data you need for complex inbound flows.
The Plumbing: I’m using Amazon SES for the actual mail delivery to ensure high deliverability from day one. On top of that, I’ve built the logic to automatically handle reputation management, bounces, and complaints. You just add a domain, drop in two lines of code, and you’re done.
I really tried to strip away the "over-engineered" parts of email. No complex CRM-style contact syncing—just a high-performance pipe to send and receive mail.
Happy to answer any questions about the setup!
https://www.simpleemailapi.dev/
I’m an indie hacker. Like many of you, I usually have 3 or 4 projects running at once. My biggest frustration with existing email APIs (the Resends and Postmarks of the world) is how they handle domains.Most platforms restrict you to a single domain on the free tier, and even the initial paid tiers are surprisingly stingy. Whenever I started a new experiment, I had to "kill" the email for a...
Lately I have been building something, and sending transactional emails via api is easy with resend and couple of other services. But receiving been pretty difficult for me when I want to thread the replies easily and quickly?My use case is that from web based email client we have to send transactional emails and users can reply to it and I need a way to receive them and thread them properly in...
Hey HN,for sometime now I am building useful products for the community and every time I build some product I really struggled with collecting feedback for it. I have integrated feedback widgets in the past from posthog and also sent users email from my personal email and much more and mostly no one cared to reply or they ignored the in app widget. So I had to manually send them these email...
I have been building SaaS for sometime now and I always stumbled across this problem when your landing page doesn't convert. You always think that you have built the best landing page for your SaaS in the world but when you get another set of eyes on there they simply say "I dont get what are you trying to sell here" or "I don't whats the way through it" and many other things.So on this quest...
I aim to make it into a agentic system that provides you expert level CRO analysis but at fraction of the costs then those expensive CRO consultants