Transactional Email for Django: what 14 makers' products chose
Among 14 makers' products built with Django that we know the transactional email of, SendGrid leads: 7 of them (50%). Next come Postmark (6) and Resend (2).
Transactional or marketing. Transactional services send one message the moment your app triggers it (a password reset, a receipt). Marketing/lifecycle tools send sequences and campaigns to lists. Most apps need the first on day one and the second later.
What makers on Django chose
| Option | Django products | All makers | Free for | At 10,000 users |
|---|---|---|---|---|
| 7 (50%) | 46% | None | $20/moEssentials 50k | |
| 6 (43%) | 27% | ~20 users | $55/moBasic 50k | |
| 2 (14%) | 44% | ~600 users | $20/moPro 50k | |
| 2 (14%) | 2% | ~600 users | $35/moFoundation 50k |
Live makers' products with a source for both: that they're built with Django, and what they use for transactional email. A product using two options counts in both; not market share. "All makers" is the option's share among every maker's product that made this decision.
Costs are the cheapest plan that fits, from each vendor's pricing page, at the usage our stack planner assumes for a product with that many users. Free for: the users its cheapest plan a business can use stays free for; plans for personal use only, like a non-commercial hobby tier, don't count.
Which to pick, by situation
- You write React or TypeScript and want email templates as components in the same codebase
Resend 2 here - Your login codes and password resets must arrive within seconds
Postmark 6 here - Your app also needs to receive and parse email that users send to it
Mailgun 2 here
SendGrid
Transactional + marketing7 Django products here (50%). About $20 a month at 10,000 users (Essentials 50k).
llms.txtIn ReplitBest forOne vendor for both jobs at large scale.
Trade-offHeavier than a small team needs.
- Client libraries for JavaScript and Python are easy to use, and the docs are clear. 2 sources
- One service covers onboarding, transactional and bulk marketing email at scale. 3 sources
- Deliverability is poor, and its internal reputation score can look great while Gmail and Microsoft reputation tanks. 4 sources
- Since the Twilio acquisition the free plan was retired and the product feels neglected. 3 sources
Status page: 1+ incidents in the last 90 days (its own page, 2026-10-19).
“Listed in their tool stack on Starter Story”
Transactional EmailMaker says so · source ↗
Postmark
Transactional API6 Django products here (43%). Free up to about 20 users. About $55 a month at 10,000 users (Basic 50k).
llms.txtBest forDeliverability when the mail has to arrive within seconds.
Trade-offStrict about transactional-only sending — marketing email goes through a separate stream — and the free developer plan is small.
“Listed in their tool stack on Starter Story (email)”
- Its reputation for transactional mail gives strong inbox deliverability. 3 sources
- The API is simple enough to use with plain curl, and templates and layouts speed up building emails. 3 sources
- Opening up to broadcast mail and ActiveCampaign ownership worry some that its deliverability edge will erode. 2 sources
- There is no built-in idempotency, so preventing duplicate sends needs locks and metadata checks. 1 source
“Listed in their tool stack on Starter Story (email)”
Transactional EmailMaker says so +1 · source ↗“Listed in their tool stack on Starter Story (email)”
Transactional EmailMaker says so +2 · source ↗“Listed in their tool stack on Starter Story (email)”
Transactional EmailMaker says so · source ↗
Resend
Transactional API2 Django products here (14%). Free up to about 600 users. About $20 a month at 10,000 users (Pro 50k).
llms.txtIn Bolt, Lovable, ReplitBest forA modern developer API with email templates written as React components.
Trade-offA younger service than Postmark or SES, and costlier than SES at very high volume.
- The API is clean and TypeScript-first, simple enough to call with a plain fetch and no SDK. 2 sources
- Transactional email goes live within a day, with DNS setup and deliverability basics handled. 2 sources
- It runs on AWS SES, so an AWS us-east-1 outage stopped both its dashboard and email sending. 2 sources
- API gaps remain, such as the broadcast API not returning email content and no stored copy of sent threads. 2 sources
Mailgun
Transactional API2 Django products here (14%). Free up to about 600 users. About $35 a month at 10,000 users (Foundation 50k).
In LovableBest forHigh volume and inbound email parsing and routing.
Trade-offIts dashboard and API are older and busier than newer services, and the free tier is small.
“Listed in their tool stack on Starter Story (trello email)”
- Reliable transactional email that gets a SaaS sending within days or weeks of starting. 2 sources
- The API is a cost-effective choice for transactional mail next to a separate marketing tool. 2 sources
- Shared sending IPs regularly land on Yahoo and Outlook blocklists, partly because spam also flows through its network. 4 sources
Status page: 10 incidents in the last 90 days, 3 major (its own page, 2026-10-19).
“Listed in their tool stack on Starter Story (trello email)”
Transactional EmailMaker says so · source ↗Also chosen, and not seen yet
Real options for transactional email not seen among these Django products yet: Amazon SES.
Who switches, and to what
Public GitHub pull requests whose title says "X to Y", by developers in general, not only on Django.
- SendGrid → Resend 60 pull requests · how they moved
- Resend → SendGrid 17 pull requests
- SendGrid → Mailgun 11 pull requests
- Resend → Postmark 6 pull requests
- SendGrid → Postmark 6 pull requests
- Mailgun → Resend 3 pull requests
Getting transactional email right
Send from a subdomain (mail.yourapp.com), set up SPF, DKIM and DMARC before launch, and keep marketing mail on a separate stream so a campaign can't hurt your password resets.
- Sending without SPF, DKIM and DMARC set up, so password resets land in spam or get rejected by Gmail and Yahoo.
- Sending campaigns through the same stream and domain as transactional mail, so spam complaints about a newsletter hurt delivery of your password resets.
- Sending email inline in the request, so a slow or failing provider breaks sign-up; queue it and retry instead.
The rest of the Django stack
What makers' Django products chose for their other decisions, the most common pick for each:
- Hosting: DigitalOcean 8 of 17
- Payments: Stripe 12 of 13
- Web Analytics: Google Analytics 10 of 12
Questions
What do most Django apps use for transactional email?
Among 14 makers' products built with Django that we know the transactional email of, SendGrid leads: 7 of them (50%). Next come Postmark (6) and Resend (2).
What does transactional email cost for a Django app with 10,000 users?
On our usage model at 10,000 users, SendGrid comes to about $20 a month (Essentials 50k); Postmark comes to about $55 a month (Basic 50k); Resend comes to about $20 a month (Pro 50k); Mailgun comes to about $35 a month (Foundation 50k). Prices are from each vendor's pricing page.
Which transactional email option stays free longest for a Django app?
Resend: on our usage model its cheapest plan stays free up to about 600 users.
How this is counted: a product is on Django when a live-product source says so (the maker, its website, a customer story or a subprocessor list), and the same for its transactional email. How evidence is collected.