Developer email infrastructure
Lumail vs Resend
Choose Resend for developer-first transactional infrastructure. Choose Lumail when newsletters, audience workflows, a visual editor, and agent-run marketing operations should be first-class too.
Pricing checked August 9, 2026
| Decision | Lumail | Resend |
|---|---|---|
| Free allowance | $0, 5,000 emails/month | 3,000 transactional emails or 1,000 marketing contacts |
| Paid entry | $20/month, 20,000 included, then $0.60/1,000 | $20/month transactional; $40/month marketing |
| Pricing basis | Unlimited subscribers; pricing follows email volume | Separate transactional volume and marketing contact plans |
| Automation | Graph workflows with triggers, branches, goals, exits, and A/B paths | 10,000 automation runs included; usage overage on paid plans |
| AI and developer access | ChatGPT OAuth, MCP, skills, CLI, SDK, REST API, and visual editor | Developer API, SDKs, and AI-oriented documentation |
| Transactional email | Included through API, SMTP, SDK, CLI, and agent tools | Core product with REST API and SMTP |
| Publishing surface | Capture pages and custom web domains; not a general website builder | Broadcasts and contacts, not a hosted newsletter publication |
Where Resend is strong
A real alternative, not a straw man.
Resend provides developer-focused transactional sending, inbound email, broadcasts, contacts, automations, SDKs, SMTP, webhooks, and deliverability tooling. Its strongest fit is developers prioritizing transactional delivery and api ergonomics.
- Strong developer experience and SDK ecosystem
- Transactional email, inbound, and deliverability tooling
- Clear volume pricing with paid overages
The workflow is the real product test.
Feature tables flatten important differences. Rebuild one journey with a real trigger, a branch, a wait, a conversion goal, and an exit rule. Then inspect what happened to one subscriber. That test exposes more than a checklist ever will.
- 1. Import a small, consented subscriber sample.
- 2. Recreate one campaign and its audience rule.
- 3. Publish one automation with a measurable goal.
- 4. Trigger a test run and inspect every event.
- 5. Compare the repeated work, not only setup time.
Choose Lumail if…
- You want one subscription for newsletter and transactional workflows
- Non-developers need a full visual campaign and workflow surface
- You want organization-aware MCP and CLI operations
Choose Resend if…
- Transactional email infrastructure is the primary product
- You prefer separate plans for transactional and marketing email
- Resend's SDK and React Email ecosystem fit your stack
Test the operating model
Store unlimited subscribers. Start with 5,000 emails free.
Recreate one real campaign, workflow, and transactional message before migrating a full audience. No credit card required.
Questions before you switch
Is Lumail cheaper than Resend?
It depends on list size, sending frequency, and the features you need. Lumail charges by email volume and stores unlimited subscribers. Resend uses separate transactional volume and marketing contact plans. Model one normal month and one peak month before deciding.
What is the main difference between Lumail and Resend?
Choose Resend for developer-first transactional infrastructure. Choose Lumail when newsletters, audience workflows, a visual editor, and agent-run marketing operations should be first-class too.
Can I migrate from Resend to Lumail?
Yes. Export a controlled subscriber sample first, reproduce one campaign and one automation, verify sender-domain authentication, then compare delivery and workflow behavior before moving the full audience.