Resend

Multiple users report significant delays in email delivery, with some confirmation messages taking over a minute to arrive, and general performance degradation in production environments despite Resend's developer-first positioning.

Resend lacks native support for email preview testing across different email clients, A/B testing, and has no built-in inbox placement testing or blocklist monitoring. Teams must handle these critical deliverability checks outside the platform.

Resend does not adequately serve serverless and background job-based email workflows that are common in modern technology stacks. Documentation and tooling for these patterns are unclear or insufficient.

Free and Pro plans only retain email data for 1 and 3 days respectively, making it difficult to diagnose deliverability issues or identify longer-term trends without upgrading or implementing custom logging infrastructure.

The React Email CLI tool has suboptimal performance in monorepo setups and cross-platform environments (Windows, Linux, macOS), creating friction for developers not using macOS or traditional project structures.

Resend lacks a visual email builder or drag-and-drop template editor, requiring all emails to be created in code using raw HTML or markdown. This is a significant limitation for non-technical users, marketers, or teams that need rapid template iteration without developer involvement.

Resend enforces a 2-day account approval process before developers can send their first email. Additionally, advanced features and white-glove support require contacting sales, creating friction for teams wanting to evaluate the platform independently.

Resend lacks native support for dynamic content generation, localization, or complex personalization logic, forcing teams to implement these features outside the platform or in their application code.

Resend's relatively young ecosystem lacks the breadth of integrations, no-code tooling, and marketing automation features available from long-established email providers, limiting its use case for hybrid developer-marketer teams.