Resend controls delivery IPs via DNS

Running its own MTA turns Resend from a thin developer layer on top of AWS into a company that controls the hardest part of email delivery, the IPs, pacing, and reputation that decide whether messages land in inboxes or spam. The key detail is that migration happens at the domain level through DNS, so a customer can keep the same API calls and templates while shifting one brand or product line onto Resend managed infrastructure.1 2 3 4

• This is really a control plane move. Application code still calls Resend the same way, but changing the return path and related DNS lets Resend decide which IP pool sends mail for that domain, which means it can tune warm up, throttling, and provider specific delivery behavior itself.1 2 3 4
• The closest analogue is how Amazon SES and other email platforms use custom MAIL FROM or dedicated IP setup. DNS is the switch that tells mailbox providers which infrastructure is speaking for a domain. Resend is packaging that low level setup behind one domain setting instead of asking customers to rebuild their integration.2 3 5
• Owning the sending layer also changes margins and product scope. Resend takes on fixed costs and abuse screening that AWS previously absorbed, but gains room to differentiate on deliverability and operations, which matters more as it expands from simple transactional sends into higher volume marketing and agent driven workflows.1 4 6

The next step is a larger share of volume moving onto Forge, because once a sender trusts Resend with domain level delivery, the company can bundle inbox placement, reputation management, and routing logic into the core product. That pushes the market away from commodity email APIs and toward full stack delivery operators.1 4 6