Email forwarding for custom domains. Receive and send emails from your own domain with ARC/DKIM signing, webhook delivery, and simple setup. No credit card required.
Hey Product Hunt folks π
I built KaiMail because I kept running into the same problem.
I co-founded PyCon JP and PyCon MY. Every community event we ran had a beautiful domain β and then used @gmail.com for email, because setting up real email hosting was either too complicated or too expensive. Google Workspace charges per seat. That doesn't work for a rotating team of volunteers.
So I built KaiMail: email forwarding for custom domains that actually works. Point your MX records at us, set your routes, and start receiving email at your domain. No mail servers to manage, no per-seat pricing.
Two things I'm particularly proud of:
1. Proper ARC + DKIM handling β most forwarding services silently break email authentication. KaiMail handles forwarding correctly so your emails don't end up in spam.
2. Webhook delivery β instead of (or in addition to) forwarding to an inbox, KaiMail can POST incoming emails as signed JSON payloads to any endpoint. Great for building email-powered apps or data pipelines.
KaiMail is free to start, no credit card required. Would love to hear what you build with it.
Report
How do you guys will handle spam especially for webhooks? Congrat on the launch btw.
@koditiΒ Thanks. Spam comes with the territory when you deal with emails unfortunately, and we currently have a roadmap for this. There are already established best-practices within the industry that help with this problem such as checking for DKIM, ARC or SPF records which can be implemented on the SMTP level, that is where we will work on first. Those alone can stop a bulk of the spam, but beyond that will require a more dedicated filtering system, which requires reading the contents of the email. Due to the nature of the topic, it will be unwise to divulge more than that at this point.
Replies
Kafkai
How do you guys will handle spam especially for webhooks? Congrat on the launch btw.
Kafkai
@koditiΒ Thanks. Spam comes with the territory when you deal with emails unfortunately, and we currently have a roadmap for this. There are already established best-practices within the industry that help with this problem such as checking for DKIM, ARC or SPF records which can be implemented on the SMTP level, that is where we will work on first. Those alone can stop a bulk of the spam, but beyond that will require a more dedicated filtering system, which requires reading the contents of the email. Due to the nature of the topic, it will be unwise to divulge more than that at this point.