Banger is a native Mac app for teams running shared inboxes like support@, sales@, and founder@. You and AI agents work the same mailboxes: agents triage, label, and draft with scoped access, while you review before anything sends. Connect your own domain or Google Workspace accounts, search everything, assign threads, and track work on a board. Early access: 14 days free, 2 mailboxes, 100 AI credits, no card. 500 spots now. Mac first, Windows and mobile next.
I’ve spent the last few years building chat apps, first at Beeper, including Beeper Mini, and then at Automattic. Most of my work has been deep app engineering: native clients, messaging surfaces, sync, reliability.
One thing I kept running into is that email still feels built for one person, even though a lot of company work happens there. Support, sales, invoices, recruiting, partnerships. It all lands in the inbox, but teams still end up sharing passwords, forwarding threads around, or pasting drafts into Slack when they want someone else to review a reply.
So I left my job and started MuchBetterApps with a friend who has spent years building and operating infrastructure. Banger is the first thing we’re building.
The basic idea is shared email with review built in. You can have shared mailboxes, real permissions instead of one shared login, and a way to put an email up for review before it sends. That can be for a teammate’s draft, or for something an AI agent wrote. The closest analogy is probably a pull request, but for email.
One important detail: for custom domains, we are not just putting a nicer UI on top of someone else’s email product. We built our own mail infrastructure for receiving and sending email, including the domain setup layer. We are not relying on AWS SES, SendGrid, Postmark, Mailgun, or another hosted email service for that part. There is a lot of unglamorous work in deliverability, routing, queues, DNS setup, bounces, retries, and abuse prevention, but I think owning this layer matters if we want to build the kind of email product we have in mind.
Today we're launching the native Mac app. It supports your own domains and Google Workspace. For new domains, we’re trying to make setup less annoying. For existing Google Workspace teams, the goal is to add the collaboration layer that Gmail does not really have.
This is early access, so it’s not the whole vision yet. There are 500 open spots now and we plan to open more as the infrastructure scales.
I’ll be around in the comments. I’d love to hear what you like, what feels unclear, and what you think we’re missing. Thanks for checking it out.
How scoped exactly is the agent access — can it send on its own in some scenarios, or does every outbound always wait on a human click?
Building your own send/receive infrastructure instead of layering on SES or Postmark is the choice most teams talk themselves out of because the ROI takes years to show. But it's the one that separates products that stay flexible from ones that hit ceilings the moment their upstream provider decides to change something.
The "pull request for email" analogy is the tightest way to state that pattern I've heard. Review-before-send with AI drafts is exactly the missing layer, I've watched teams try to bolt this on with Slack channels, forwarded threads, and shared Google Docs, and it collapses within a month because the review context doesn't survive being ripped out of email.
Genuine question, for someone running cold email operations across multiple mailboxes and warmed domains, does Banger's shared inbox model extend to that use case, or is it strictly for shared team inboxes like support@ and sales@? The reason I ask: cold email is one of the places where "one draft, three eyes on it before it goes" would materially reduce misfires, but the current tooling assumes single-operator workflows.
Shared mailboxes where agents triage and draft but a human reviews before send is exactly the setup I'd want for a support@/founder@ inbox — the 'forward the thread into Slack for a second opinion' dance is real. One thing I'd test first: does the review-before-send gate apply to every agent-drafted reply forever, or can you whitelist specific labels/intents (say, shipping-status replies) for auto-send once you trust the triage? And is an agent's scoped access set per-mailbox, or can you restrict it to certain threads/labels within a single inbox?
finally a shared inbox that feels built for mac, the scoped ai access for drafting is genuinely useful and the kanban board for threads makes support way easier to follow
finally a mac app that doesn't feel like a chrome wrapper for shared inboxes. love that ai drafts sit waiting for approval before sending, keeps things sane for support@
how does the AI scoping actually work in practice, like can two agents see different drafts of the same thread or is everything shared across the team
Scoped access + human review before send is the right trust boundary for mixing AI agents into shared inboxes. How granular does the scoping get - can one agent draft-only on support@ while another gets broader access on sales@, or is it set per-mailbox rather than per-agent?
How do the AI agents actually decide when to draft a reply vs just label something, and can I set per-agent rules or do they all run on the same defaults?
shared password / forwarding threads around for a support@ inbox is such a specific, real pain that never gets fixed properly. glad you kept a review step before send instead of letting agents fire off replies on their own, that's the part that would actually make me trust it with a customer-facing mailbox
Shared inboxes are a good place for AI because the work is repetitive but the accountability is still human. The guardrail I would want is a clean separation between draft, suggested action, and actual send, especially for support or billing threads.
How do you envision the AI agents handling email threads with multiple stakeholders or complex customer support issues?
If two teammates are reviewing the same conversation at the same time, how does Banger prevent duplicate replies or conflicts?
I appreciate that you built your own email infrastructure instead of just adding another interface on top of existing services. That is a much bigger undertaking than most people realize.
The "pull request for email" framing is exactly right. I build support and sales agents for ecommerce stores, and
review-before-send is the single thing that makes owners comfortable letting an agent anywhere near their inbox. So, it
is great to see it treated as a first-class feature instead of a bolt-on.
The question that I think decides whether this scales: what happens after a reviewer has approved 50 routine drafts in
a row and starts rubber-stamping? Do you plan per-agent or per-thread-type trust levels (auto-send the routine stuff,
always hold refunds, pricing, anything with money), or sampled review once an agent earns confidence? That dial
between safety and approval fatigue is the hardest part of this pattern in my experience.
Also, respect for owning the mail infrastructure yourselves. Deliverability, bounces and abuse handling are unglamorous, but that layer is usually where products like this live or die.
Congrats on the launch, Tiago.
This is very interesting. We're building an AI agent for outreach and encountered this issue. Will explore how it works. Congrats on the launch!
Congrats! QQ, this is only for MacOS or any future plans to release on Win?
About Banger Mail on Product Hunt
“Shared mailboxes for teams and AI agents”
Banger Mail launched on Product Hunt on July 2nd, 2026 and earned 128 upvotes and 28 comments, placing #7 on the daily leaderboard. Banger is a native Mac app for teams running shared inboxes like support@, sales@, and founder@. You and AI agents work the same mailboxes: agents triage, label, and draft with scoped access, while you review before anything sends. Connect your own domain or Google Workspace accounts, search everything, assign threads, and track work on a board. Early access: 14 days free, 2 mailboxes, 100 AI credits, no card. 500 spots now. Mac first, Windows and mobile next.
Banger Mail was featured in Email (36.7k followers), Productivity (655.1k followers) and Customer Success (6.2k followers) on Product Hunt. Together, these topics include over 152.2k products, making this a competitive space to launch in.
Who hunted Banger Mail?
Banger Mail was hunted by Tiago Loureiro. 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 Banger Mail stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Tiago Loureiro
Hey Product Hunt 👋 I'm Tiago.
I’ve spent the last few years building chat apps, first at Beeper, including Beeper Mini, and then at Automattic. Most of my work has been deep app engineering: native clients, messaging surfaces, sync, reliability.
One thing I kept running into is that email still feels built for one person, even though a lot of company work happens there. Support, sales, invoices, recruiting, partnerships. It all lands in the inbox, but teams still end up sharing passwords, forwarding threads around, or pasting drafts into Slack when they want someone else to review a reply.
So I left my job and started MuchBetterApps with a friend who has spent years building and operating infrastructure. Banger is the first thing we’re building.
The basic idea is shared email with review built in. You can have shared mailboxes, real permissions instead of one shared login, and a way to put an email up for review before it sends. That can be for a teammate’s draft, or for something an AI agent wrote. The closest analogy is probably a pull request, but for email.
One important detail: for custom domains, we are not just putting a nicer UI on top of someone else’s email product. We built our own mail infrastructure for receiving and sending email, including the domain setup layer. We are not relying on AWS SES, SendGrid, Postmark, Mailgun, or another hosted email service for that part. There is a lot of unglamorous work in deliverability, routing, queues, DNS setup, bounces, retries, and abuse prevention, but I think owning this layer matters if we want to build the kind of email product we have in mind.
Today we're launching the native Mac app. It supports your own domains and Google Workspace. For new domains, we’re trying to make setup less annoying. For existing Google Workspace teams, the goal is to add the collaboration layer that Gmail does not really have.
This is early access, so it’s not the whole vision yet. There are 500 open spots now and we plan to open more as the infrastructure scales.
I’ll be around in the comments. I’d love to hear what you like, what feels unclear, and what you think we’re missing. Thanks for checking it out.