Resend
Send application email through an API, with a separate marketing workflow.
Sources checked
Our recommendation
When to choose it
Start with Resend for an application email integration. Treat transactional delivery and consent-based marketing as separate jobs.
A good fit for
- A web app sending welcome or account email
- A team authoring email alongside application code
Choose something else when
Compare Postmark when your priority is a dedicated transactional email operations workflow.
Watch out for
- Verify your sending domain and keep the API key on the server.
- Marketing needs consent, unsubscribe handling and its own sending cadence; account email is not blanket marketing permission.
How costs work
Email volume plans; marketing has a contact-based model
Check the lane you use, sending limits and overage settings. A sending service does not automatically provide a reply inbox.
Check current official terms and pricing ↗This is a pricing model, not a monthly quote. Check your region, intended usage and current plan before buying.
What connects to it
- Server-side API calls
- React-authored email templates
These are technical connections you can configure. Selecting a card creates no accounts or resources.
Compare the alternatives
Learn the boundary before you connect it
Lessons open through your account and the kits you own.
Check the evidence
Feature sources were reviewed on 4 Oct 2026. Plans and availability can change.
- Email API ↗
Server API integration and verified sending domains.
- Email pricing ↗
Transactional volume and marketing contact plan models.