Need advice about which tool to choose?Ask the StackShare community!
Amazon SES vs SendGrid: 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; SendGrid: Email Delivery. Simplified. SendGrid's cloud-based email infrastructure relieves businesses of the cost and complexity of maintaining custom email systems. SendGrid provides reliable delivery, scalability and real-time analytics along with flexible API's that make custom integration a breeze.
Amazon SES and SendGrid 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, SendGrid provides the following key features:
- Open Tracking
- Click Tracking
- Unsubscribe Tracking
"Reliable", "Cheap" and "Integrates with other aws services" are the key factors why developers consider Amazon SES; whereas "Easy setup", "Cheap and simple" and "Easy email integration! " are the primary reasons why SendGrid is favored.
According to the StackShare community, SendGrid has a broader approval, being mentioned in 2692 company stacks & 421 developers stacks; compared to Amazon SES, which is listed in 1283 company stacks and 274 developer stacks.
For transactional emails, notifications, reminders, etc, I want to make it so writers/designers can set up the emails and maintain them, and then dynamically insert fields, that I then replace when actually sending the mail from code.
I think the ability to use a basic layout template across individual email templates would make things a lot easier (think header, footer, standard typography, etc).
What is best for this? Why would you prefer Mailgun, SendGrid, Mandrill or something else?
If you need your emails to be sent in a time-sensitive manner, I'd recommend SendGrid. We were using Mailgun and the lag because they aren't "transactional" in nature caused issues for us. SendGrid also has the ability to do dynamic templates and bulk send from their API. I don't know that they have the shared layout ability you mentioned, though.
The only transactional email service that I've been able to stomach is Postmark! It is by far the easiest (and quickest to get feedback from) service that I have come across. While drowning in attempts to debug Mandril, Mailgun and others I get quick feedback from Postmark in what I need to do.
Postmark for the win!
We are using more extensively Mandrill.
It is a ok tool, which gives you the power for emailing with nice set of features.
The templates editing and management is a bit tricky, but this is mostly related to email templates in general, which are hard to create and maintain.
I do not think you can share the parts of the templates. You can have your predefined templates with possibility to insert dynamic content.
They provide a limited possibility to preview and test your templates.
The template editor is text only. For the better editors checkout http://topol.io or https://mosaico.io
Unfortunately, I do not have experience with the other tools and possibilities to manage templates.
At this stage, all of the tools you mentioned do email delivery pretty well. They all support email templates as well. Here are some considerations:
- Twilio owns SendGrid. If you're an existing Twilio customer, in my opinion that's a good reason to use SendGrid over the other solutions. The APIs are solid, and Twilio has excellent developer tools that allow you to create interesting automations (which is important for scaling).
- Mandrill was created by MailChimp, who have massive experience with email delivery and specifically with emailing beautiful email templates.
- Mailgun is a tool on its own. Like the other two, it supports mail templates and is built to be controlled almost exclusively via APIs.
SendGrid and Mandrill have pretty nice WYSIWIG template editors as part of their platform. Not so sure about Mailgun.
So for me the considerations would be: 1. How easy is it for you to integrate with their API? How complete is their API in terms of your own specific needs? 2. Prices: Which one works best for my budget? 3. Am I OK with editing the templates elsewhere (or even by hand), and then pasting the code into Mailgun? Or do I want the comfort of Mandrill or Sendgrid with their WYSIWYG editors?
Personally I'd go with Twilio, simply because it's such a massive ecosystem they are less likely to go bankrupt, and their APIs are rock solid.
We chose Postmark as our transactional email service for several reasons:
Laser-focus (at the time) on transactional email - their success/speed/reliability with delivering transactional email is amazing. Note, they have now branched out and offer marketing/broadcast email services too.
Developer-friendly - Awesome docs and resources. Their Rail gem integrates directly with ActionMailer so nearly all of our code worked without changes.
Servers - You can set up "Servers" for different mail streams/workflows to keep things separate and easy to review.
Bootstrapped - Wildbit (who makes Postmark) is bootstrapped just like the Friendliest.app and they offer a service credit to other bootstrapped startups.
Of course we chose Coresender to send our own transactional emails :) So I thought I'll let you know how we use it.
We set up separate sending accounts for all company needs, eg. transactional emails, monitoring alerts, time to inbox. We even configured our office printers to send emails through Coresender.
We have a real-time and extremely usable view into what emails go through each account, so each time anybody reports an email not arriving we're able to assist them in a few seconds
We utilize our message timeline feature, so we can learn eg. if people are clicking on password reset links
We always know how many of our onboarding emails are being opened which helps us improve them
Finally, we have full controll over our suppressions lists, so we can add (and remove!) from them whenever necessary.
To sum up, at Coresender we're eating our own dogfood and it helps us stay connected to the product and understand our customers better.