Email for everything you ship

What are you building?

• Indie hackersEach product needs auth emails, a support@ address, DNS records and another bill. Then you start the next one.A project per product, auth emails through Supabase SMTP, a support inbox.
• SaaS teamsThe sending bill grows with every user, and support@ lives in a separate help desk with its own seats.Resend compatible sending, a shared support@ and signed webhooks.
• Vibe codersThe app works, but sign up emails never arrive or land in spam, and you are not sure where the email code should even go.One prompt for Lovable, Bolt, v0, Replit or Cursor.
• AI agent buildersAn agent that signs up for things needs a real address, has to catch the verification code, and should never touch your own mailbox.Inboxes over MCP; wait_for_email returns the code.
• QA and test engineersSign up, magic link and password reset flows need a real inbox, and a polling loop that is flaky in parallel.A catch-all address per test and a blocking wait.
• Agencies and freelancersEvery client site needs a contact form, a sender domain and a support address, and every teammate needs the right access to each.A project per client and roles per teammate.

Whichever you pick, it is one product: sending, receiving, support inboxes, agent inboxes and test inboxes share the same domains, keys and API. Not sure where to start? The integrations directory lists every tool by status.