Your agents sign up for tools, receive verification codes and reply to customers, mostly from your Gmail or a shared sending pool where one bad actor gets everyone flagged. OpenMail gives every AI agent its own inbox on your domain with its own sending reputation, for one API call each. Incoming mail reaches your code over webhook or WebSocket, attachments arrive as text, and there's a hosted MCP server and a Hermes plugin. Built and hosted in the EU, free for 3 inboxes.
Hi Product Hunt, Jokūbas here, co-founder of OpenMail with @efemeralizacija .
We started in March because every agent we saw was using a borrowed email address. It signed up for tools and answered customers from someone's Gmail, or from a shared sending domain where one bad tenant got everyone's mail flagged. That falls apart once you run more than a few agents, and faster when the agents belong to your customers.
OpenMail gives each agent its own inbox: a real address on your domain, inbound delivered to your code over webhook or WebSocket, attachments turned into text your model can read, and a sending reputation that belongs to that inbox alone, so one agent misbehaving doesn't take the others down with it. There's a hosted MCP server and a Hermes Agent plugin, and all of it runs in the EU.
Most of this year went into receiving and keeping tenants apart: isolation and abuse containment, the part that never makes it into a demo video and that you need by your second customer.
Launch-day offer: make an account today and enter Launch2026 in billing before Friday 6 November for three months of Pro. The free tier is 3 inboxes and 3,000 emails a month either way.
If you've built something that needs email, tell me what broke with your current setup; that is what we build next. And ask the hard questions about deliverability, abuse and pricing. Armandas and I are here all day and will answer every one, with numbers where we have them.
congrats on the launch jokubas. own reputation per agent makes sense, shared domains are scary when one tenant misbehaves. how does dns work when the inbox is on my domain, is spf and dkim a one time setup?
The per-inbox reputation isolation is the part I'd care about most. What happens when one inbox crosses a bounce or complaint threshold, do you pause just that inbox automatically or does it need a manual call from you first?
Congrats on the launch! This looks like exactly what we need right now. We're doing an outreach campaign, but warming up inboxes takes a lot of time and we don't want to use random inboxes from Explee. We want to use our own domain lookalikes. Will OpenMail help with that?
Do you have control policies? For instance, can you limit which domains a mailbox is allowed to send to or receive email from?
Could I have my agent draft replies and let me approve them before they go out?
I hate when I set a prompt for an AI agent to code all night but it gets stuck on some email verification. Tons of time wasted. Could this help me out?
This looks like a very interesting addition to the agent ecosystem. I was curious how you handle spam / marketing emails. Do agents also alert users about marketing emails?
Love it, where do you think differentiation will come from in this space? What’s next?
@jokubas_vaiciulis_@efemeralizacija This could become an important part of the AI agent ecosystem. How do you handle identity verification for agents ?
Congrats on the launch! The year you spent on isolation and abuse containment probably won’t show up in a demo, but it’s what will make teams trust this in production. Good luck today.
Inbound retries seem worth making very visible when an agent is on the other end. I'd want it to recognize the same message arriving twice before it sends two replies.
a sending reputation per inbox instead of a shared pool is the part i care about, one noisy agent dragging down evrything else is exactly what goes wrong with shared sending
when someone spins up a brand new inbox on a fresh domain, do you ramp its volume slowly on your side??? or is warming it up left to the customer???
About OpenMail on Product Hunt
“Give your AI agents an identity through email”
OpenMail launched on Product Hunt on November 4th, 2026 and earned 161 upvotes and 33 comments, placing #4 on the daily leaderboard. Your agents sign up for tools, receive verification codes and reply to customers, mostly from your Gmail or a shared sending pool where one bad actor gets everyone flagged. OpenMail gives every AI agent its own inbox on your domain with its own sending reputation, for one API call each. Incoming mail reaches your code over webhook or WebSocket, attachments arrive as text, and there's a hosted MCP server and a Hermes plugin. Built and hosted in the EU, free for 3 inboxes.
OpenMail was featured in Email (36.8k followers), Developer Tools (522.4k followers) and Artificial Intelligence (482.8k followers) on Product Hunt. Together, these topics include over 234.9k products, making this a competitive space to launch in.
Who hunted OpenMail?
OpenMail was hunted by André J. 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.
Want to see how OpenMail stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
André J
Hi Product Hunt, Jokūbas here, co-founder of OpenMail with @efemeralizacija .
We started in March because every agent we saw was using a borrowed email address. It signed up for tools and answered customers from someone's Gmail, or from a shared sending domain where one bad tenant got everyone's mail flagged. That falls apart once you run more than a few agents, and faster when the agents belong to your customers.
OpenMail gives each agent its own inbox: a real address on your domain, inbound delivered to your code over webhook or WebSocket, attachments turned into text your model can read, and a sending reputation that belongs to that inbox alone, so one agent misbehaving doesn't take the others down with it. There's a hosted MCP server and a Hermes Agent plugin, and all of it runs in the EU.
Most of this year went into receiving and keeping tenants apart: isolation and abuse containment, the part that never makes it into a demo video and that you need by your second customer.
Launch-day offer: make an account today and enter Launch2026 in billing before Friday 6 November for three months of Pro. The free tier is 3 inboxes and 3,000 emails a month either way.
If you've built something that needs email, tell me what broke with your current setup; that is what we build next.
And ask the hard questions about deliverability, abuse and pricing. Armandas and I are here all day and will answer every one, with numbers where we have them.
Docs: docs.openmail.sh. Thanks for having a look.