One email stack for your code, your team and your AI agents: how are you handling it?

Hey everyone 👋 I'm the maker of MarkRelay.

Our team runs several independent products, each on its own brand domain. And every brand needs email in three very different ways:

1. Code: our products send transactional emails through an API: sign-up confirmations, password resets, receipts, notifications.

2. People: our team uses webmail for user support and marketing ops: answering customers, following up with partners, running outreach. Different mailboxes belong to different teammates.

3. AI agents: a lot of email work is repetitive: sorting inbound, drafting first replies, chasing follow-ups, pulling info out of threads. We want agents to handle that in real mailboxes, with a human stepping in when needed.

Covering all three meant stitching tools together: one service for API sending, Google Workspace seats for the team, custom glue for agents. That's three bills, three places to configure DNS, and no single view of what each brand actually sent and received. So we built MarkRelay: one self-hosted email stack that serves all three.

- Sending API: automate transactional and product emails from any of your domains

- Webmail for the team: send & receive as any brand, and give each teammate access to only the mailboxes they own

- Mailboxes for AI agents: agents read, draft and reply through the same mailboxes, with full history your team can review

- Every brand, every domain, one place: no per-seat pricing, your data on your own infrastructure

We're launching on Product Hunt soon. Before that I'd love to learn from teams in the same spot:

1. Do your API emails, team inboxes and agent workflows live in separate tools today?

2. What email work would you hand to an AI agent first?

3. What's held you back so far: trust, deliverability, setup effort?

I'll reply to every comment 🙏