Transactional Email for Ruby on Rails: what 11 makers' products chose
Among 11 makers' products built with Ruby on Rails that we know the transactional email of, Postmark leads: 6 of them (55%). Next come Resend (3) and SendGrid (3).
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 Ruby on Rails chose
| Option | Ruby on Rails products | All makers | Free for | At 10,000 users |
|---|---|---|---|---|
| 6 (55%) | 27% | ~20 users | $55/moBasic 50k | |
| 3 (27%) | 44% | ~600 users | $20/moPro 50k | |
| 3 (27%) | 46% | None | $20/moEssentials 50k |
Live makers' products with a source for both: that they're built with Ruby on Rails, 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 3 here - Your login codes and password resets must arrive within seconds
Postmark 6 here
Postmark
Transactional API6 Ruby on Rails products here (55%). 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.
“For emails I use ConvertKit to manage my newsletter subscriptions, and Postmark for transactional emails.”
- 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
“For emails I use ConvertKit to manage my newsletter subscriptions, and Postmark for transactional emails.”
Transactional EmailMaker says so +1 · source ↗
Resend
Transactional API3 Ruby on Rails products here (27%). 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
SendGrid
Transactional + marketing3 Ruby on Rails products here (27%). 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.
“Listed in their tool stack on Starter Story (trello firebase email)”
- 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 (trello firebase email)”
Transactional EmailMaker says so +1 · source ↗Also chosen, and not seen yet
Real options for transactional email not seen among these Ruby on Rails products yet: Mailgun, Amazon SES.
Who switches, and to what
Public GitHub pull requests whose title says "X to Y", by developers in general, not only on Ruby on Rails.
- SendGrid → Resend 60 pull requests · how they moved
- Resend → SendGrid 17 pull requests
- Resend → Postmark 6 pull requests
- SendGrid → Postmark 6 pull requests
- Postmark → 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 Ruby on Rails stack
What makers' Ruby on Rails products chose for their other decisions, the most common pick for each:
Questions
What do most Ruby on Rails apps use for transactional email?
Among 11 makers' products built with Ruby on Rails that we know the transactional email of, Postmark leads: 6 of them (55%). Next come Resend (3) and SendGrid (3).
What does transactional email cost for a Ruby on Rails app with 10,000 users?
On our usage model at 10,000 users, Postmark comes to about $55 a month (Basic 50k); Resend comes to about $20 a month (Pro 50k); SendGrid comes to about $20 a month (Essentials 50k). Prices are from each vendor's pricing page.
Which transactional email option stays free longest for a Ruby on Rails app?
Resend: on our usage model its cheapest plan stays free up to about 600 users.
How this is counted: a product is on Ruby on Rails 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.