Amazon SES vs Postmark: What are the differences?
What is 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.
What is Postmark? Email delivery for web apps - done right. Postmark removes the headaches of delivering and parsing transactional email for webapps with minimal setup time and zero maintenance.
Amazon SES and Postmark can be categorized as "Transactional Email" tools.
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, Postmark provides the following key features:
- Create a new virtual server- Instant access to our infrastructure, no waiting required. Create as many servers as you want, for each of your web applications and environments.
- Drop code into your app- Swap in our SMTP endpoint, or get started with our APIs using one of our send API libraries for Ruby, Rails, .NET, Python, PHP, and more.
- Send emails and track delivery- A beautiful interface to monitor volume, bounces, spam complaints, and send activity. View full email content to troubleshoot issues.
"Reliable" is the primary reason why developers consider Amazon SES over the competitors, whereas "Simple" was stated as the key factor in picking Postmark.
Netflix, Medium, and Stripe are some of the popular companies that use Amazon SES, whereas Postmark is used by Swat.io, Docplanner, and Walls.io. Amazon SES has a broader approval, being mentioned in 1291 company stacks & 284 developers stacks; compared to Postmark, which is listed in 67 company stacks and 15 developer stacks.
The problem I have is we are using mailchimp and not happy. We want to switch to mailster and are curious the easiest and best way to send emails with mailster.
The most important factors for me are ease of use, tracking.
I have only had experience with mailchimp, constant concact and streamsend. So ease of use is important.
While building our authentication system, we originally picked Mailgun. However, emails took minutes to arrive and some of them didn't get delivered - or got delivered to spam.
We started looking for a new provider, and settled on Postmark. We love that they track time-to-inbox, it makes me feel they really care about going above and beyond to provide a good service.
What is Amazon SES?
What is Postmark?
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
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 Postmark for application-specific transactional emails like notifications and digests for our users.
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.
Good enough, could get a bit more TLC from AWS to beef up compared to the competition