Amazon SES vs Mandrill: What are the differences?
Amazon SES: Bulk and transactional email-sending service. Amazon SES eliminates the complexity and expense of building an in-house email solution or licensing, installing, and operating a third-party email service. The service integrates with other AWS services, making it easy to send emails from applications being hosted on services such as Amazon EC2; Mandrill: Send transactional, triggered, and personalized email, then track results. Mandrill is a new way for apps to send transactional email. It runs on the delivery infrastructure that powers MailChimp.
Amazon SES and Mandrill belong to "Transactional Email" category of the tech stack.
Some of the features offered by Amazon SES are:
- Simple – Amazon SES eliminates the complexity of licensing, installing, and operating a third-party service, or building and maintaining an internally hosted email solution. Sending email through Amazon SES is as simple as using SMTP or calling an API, and Amazon SES makes it easy for you to monitor your sending activity and deliverability statistics.
- Inexpensive – There are no up-front fees or fixed expenses with Amazon SES, and you benefit from the efficiencies of Amazon’s scale. Your only costs are low charges for the number of emails sent and data transfer fees.
- Reliable – Amazon SES runs within Amazon’s proven network infrastructure and datacenters. All outgoing email messages are stored redundantly across multiple servers and datacenters, providing high availability and data durability.
On the other hand, Mandrill provides the following key features:
- Inbound Email- Set up inboxes for Mandrill to control. When they receive email, we’ll make an API call to your app with all the relevant information, so you don’t have to worry about what’s happening behind the scenes.
- Webhooks Support- Create custom event notifications, keep track of new signups and unsubscribes in real-time, get a notice of every spam complaint so you can flag them in your database.
- Rules Engine- Modify the content of email coming through Mandrill without having to involve developers. For example, you could tell Mandrill to take any email coming from email@example.com, give it a new template, and add Google Analytics tracking.
"Reliable", "Cheap" and "Integrates with other aws services" are the key factors why developers consider Amazon SES; whereas "Simple installation", "Great api" and "Generous free allowance to get you started" are the primary reasons why Mandrill is favored.
According to the StackShare community, Mandrill has a broader approval, being mentioned in 2312 company stacks & 205 developers stacks; compared to Amazon SES, which is listed in 1283 company stacks and 274 developer stacks.
What is Amazon SES?
What is Mandrill?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Amazon SES?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
We've moved our transactional email away from Mandrill to Mailgun. We had continued using Mandrill after Mailchimp deprecated the service awhile back, because the amount of credits we were offered essentially made it free.
However, following a couple weeks of frequent downtime and poor service transparency from Mandrill, we decided it was time to make the switch. It appears they no longer had any engineers with the ability to identify the core problems.
Mailgun has been more reliable, yet not as reliable as we expected. We still see issues a few times per week with the API failing when we attempt to make a call. The Reporting UI is way better.
This is by far the best way to send emails. I learned the API in under 15 minutes and started sending email right then. And best of all, it's completely free to use them for me! They give you 12,000 emails/month for free. I don't have to send much email, so I've never paid a cent. I highly recommend them.
We use Mandrill to send transactional emails and newsletters. We've just moved from SendGrid as Mandrill has far better support for templates and also integrates really nicely with MailChimp where we can design the emails.
We started off with AWS SES, but found it to be lacking in diagnostics and reporting. Mandrill is a quantum leap forward in this regard. Has some other really neat features carried over from MailChimp (templating).
Our internal emails (such as exception notifications) are sent via Amazon SES, since it's cheaper than using Sendgrid. We also use Amazon SES as a fallback in case we have deliverability issues with Sendgrid.
We use Mandrill to handle all transactional emailing - from welcome letters to password reminders to notifications.
Mandrill is used to send out all e-mail from the application and any tools and services in our infrastructure.
We have add-on for Agile Toolkit that implements "Outbox" for your application through Mandrill API.
Sending transactional emails, such as reminders, contact form notifications, confirmations …etc.
Amazon SES is the email service we commonly use in clous AWS e-commerce infrastructure.
Some e-mail communication needs a independent provider, for these purposes we use SES.