Home Projects Articles Learning Resume About Contact

Transactional Email Analysis

Analysis of transactional email services to optimize company communications.

By Connor Horning

Download original PDF

Introduction

We were tasked with finding a vendor to handle traditional and transactional email systems. Some of the vendors considered included Amazon SES, Mailchimp Transactional, Mailgun, MailerSend, Postmark, Twilio SendGrid, and ZeptoMail.

We decided on a hybrid approach: a transactional email service provider for outbound mail and an inbox-ingestion pipeline for inbound mail. We narrowed the options down to two:

Amazon SES

Amazon Simple Email Service is designed for high scalability. It uses AWS infrastructure to handle millions of emails per day without capacity issues. Along with scalability, it promotes deliverability best practices such as domain authentication through SPF and DKIM, as well as feedback loops.

SES offers shared IP pools managed by AWS and dedicated IP addresses for senders who need more control. Amazon also provides tools for monitoring delivery metrics through Amazon CloudWatch and Virtual Deliverability Manager. Overall, SES provides reliable throughput and inbox placement for large volumes of transactional email.

SendGrid

SendGrid’s email platform is built for scale and advertises a strong deliverability rate. It maintains relationships with internet service providers and provides deliverability support through tools such as Deliverability Insights, email validation services, and guidance from email experts.

Like Amazon SES, SendGrid uses shared IP pools, while higher plans let customers use dedicated IP addresses. SendGrid also supports DKIM and SPF. Its main focus is providing the infrastructure and guidance needed to keep large-scale transactional email out of spam folders.

Developer Integration

Both platforms support SMTP and API-based email sending. SES supports AWS SDKs and integrates with other AWS services. SendGrid simplifies development through its APIs, client libraries, and Inbound Parse Webhook.

The webhook makes handling replies and user-generated content simpler and faster than the more AWS-specific setup required by SES.

Cost Comparison

Amazon SES is the more affordable option at a high sending volume. The estimates used in this report were:

ProviderPricing modelEstimated monthly volume and cost
Amazon SES $0.10 per 1,000 emails sent Approximately $500 per month for 5 million emails
SendGrid Tiered pricing About $400 per month for 1 million emails; 5 million can exceed $1,500 depending on features

Features such as dedicated IP addresses and higher support levels can increase SendGrid’s price. Based on these estimates, SES would remain much less expensive at the volume expected for this project.

Pros and Cons Comparison

FeatureAmazon SESSendGrid
CostVery lowHigher, especially at large volumes
Developer toolsBasic APIs and AWS SDKsFeature-rich SDKs and an intuitive interface
Inbound emailS3 and Lambda setupSimple HTTP webhook
AnalyticsBasic unless built manuallyAdvanced built-in engagement tracking
IP managementOptional dedicated IP addressesShared or dedicated IP addresses on higher plans
ScalabilityExcellent and backed by AWSExcellent, but more expensive at scale
Ease of useDeveloper-oriented and AWS-focusedPolished experience and easy onboarding

Final Recommendation

After comparing Amazon SES and SendGrid, we decided that Amazon SES would be the better option. Its affordability, scalability, and tight integration with AWS make it a good fit for an application expected to grow rapidly to 50,000 users within a year.

SendGrid offers a more user-friendly interface and advanced analytics, but the cost difference does not support choosing it for this project. We can develop a basic monitoring tool that provides similar functionality to SendGrid’s analytics page for a fraction of the cost. Amazon SES offers the best balance of value and performance as we move forward with the project.

Sources