Amazon SES vs Twilio SendGrid Email API

Amazon SES

The sending paths are genuinely documented: HTTPS API endpoints, an SMTP relay with per-region endpoints and credentials, sending quotas per second and per 24 hours, a 40 MB message cap, attachments, inbound email stored to S3 with Lambda triggers, and both a sandbox limited to verified identities and a mailbox simulator that never touches real recipients. We found no public information on stored templates, batch sending, idempotency keys, scheduled sends, or SDKs and framework guides identified by language. The plumbing is solid and inspectable; the developer conveniences are simply not on these pages.

Twilio SendGrid Email API

The documented surface is real: a REST API and SMTP relay, official libraries for seven named languages, dynamic templates with Handlebars personalisation, an inbound parse webhook, an X-SMTPAPI header and an OpenAPI specification. What the captured pages never state are rate limits, attachments, batch sending, idempotency, scheduled sending or a sandbox mode that does not deliver. The terms do commit to sixty days' notice before backwards-incompatible changes, which is more than most vendors put in writing.

Amazon SES

The reputation machinery is real: managed dedicated IPs that SES warms up itself, pools you group manually, a global suppression list that auto-blocks hard bounces, custom MAIL FROM domains, outbound content filtering and virus scanning, plus a Virtual Deliverability Manager with inbox placement testing, blocklist monitoring and dashboards cut by ISP, identity and tenant. Before I trust an inbox claim I still want the missing pieces — a vetting policy for who shares your pool, the Gmail and Yahoo sender requirements, DMARC reports, and published delivery times — and the pages themselves state that no email service can guarantee delivery of every single email. Reputation isolation is a paid feature by plan and tenant, which tells you the shared default is what a careful sender pays to escape.

Twilio SendGrid Email API

Automated dedicated IP warm-up, IP pooling, domain authentication with SPF and DKIM, link branding, ISP feedback loop data, bounce and block classifications and paid expert help are all on the record. The 99.5 percent average delivery rate, 91.3 percent inbox placement and 1.9 second median delivery are published with no method behind them — exactly the figure I refuse to take on faith — and nothing on these pages describes how shared pools are vetted or states Gmail and Yahoo bulk-sender compliance. DMARC reports and BIMI also escape every capture.

Amazon SES

Bounce, complaint and delivery notifications flow through SNS and onward to CloudWatch or Firehose, statistics break down by ISP, identity, configuration set and tenant, and an archiving add-on stores sent and received mail with search and export. On the questions that bite during an incident — log retention periods, the receiving server's answer per message, retry and signature behaviour of the notifications, alerts on bounce spikes — we found no public information. The searchable message store is an add-on on all plans, priced per gigabyte, not part of what you see by default.

Twilio SendGrid Email API

There is a searchable email activity feed, event webhooks with per-plan counts, and real-time analytics on bounces and engagement — but log retention is three days on Essentials and seven on Pro, the number you discover on day eight of an incident. Whether webhooks are signed and retried with a stated schedule, whether the raw receiving-server answer is viewable, whether retention can be extended and at what price: the captured pages are silent. A feature named "Event Webhook Security" is a label, not a specification.

Amazon SES

The controls are concrete: a require-secure-connection option with TLS 1.2 minimum, AES-256 at rest, customer-controlled keys via KMS and CloudHSM, MFA, IAM-scoped access, CloudTrail audit logging enabled by default, and a contract clause that content stays in the regions you select absent legal compulsion — with certifications running deep (ISO 27001, 27017, 27018, SOC 1-3, PCI DSS Level 1, BSI C5, ENS High). We found no public information on what is stored per message and for how long, on switching off open and click tracking, or on SSO and IP allow-listing; the retention language on the privacy page is purpose-based, not a per-message setting.

Twilio SendGrid Email API

Two-factor authentication, SSO, IP access management, SOC 2 Type II and a data protection addendum are on the record, and the terms state the customer owns the customer data. But the SOC 2 statement carries no scope, encryption at rest appears nowhere, API key scopes, an audit log and deletion of a recipient's data by API are undocumented, and whether message bodies or only metadata are stored is left unstated. Security badges without scope and a blank message-store policy is a mid-tier answer.

Amazon SES

Redundancy is described, not implied — multiple availability zones per region and multi-region endpoints that route traffic away from an impaired region — and isolation exists via tenants with separate identities, configuration and reputation. Access control runs through IAM at no charge, and support scales from a free forum to plans from $29 per month with a technical account manager for enterprise buyers. We found no public information on a public status page with incident history, on an uptime commitment with service credits, or on response times per plan; the customer agreement promises 90 days' notice before adverse service-level changes, which presupposes a commitment without showing one.

Twilio SendGrid Email API

A public status page, a 99.99 percent uptime figure, redundant hybrid infrastructure with failover policies, subusers, teammate permissions up to a thousand, and 24/7 expert support are all evidenced. Service credits, incident history, queueing and retry of mail during outages, response times per plan and named migration help are not on these pages, and only Microsoft Azure is named as a platform integration. The SLA number is a promise; the credits that make it a promise are missing.

Amazon SES

A Luxembourg EMEA entity contracts with European customers, a DPA with the 2021 standard contractual clauses is published, subprocessors are listed with locations and 30 days' notice of changes, and the certifications include BSI C5, ENS High and the CISPE code. But the captured pages state that messaging providers "route and process data globally as necessary", region selection is the customer's job with no stated default, and we found no public information that the SES sending chain itself stays in the EU. Sovereignty here is a configuration the buyer must assemble and monitor, not a property the vendor commits to end to end.

Twilio SendGrid Email API

EEA customers contract with Twilio Ireland Limited in Dublin and a data protection addendum is referenced in the terms, while the pricing page carries a bare "Data Residency (EU)" feature name — but no capture says where messages, logs and account data are actually processed or what that region covers. The parent is Twilio Inc. of San Francisco, subject to FTC oversight, and the subprocessors for hosting, sending infrastructure, logging, support and payment are unnamed on every captured page. An Irish signature is not a European chain.

Amazon SES

A buyer can genuinely compute a bill: three named plans with per-1,000-email rates by volume tier applied marginally, fixed monthly charges of $105 and $500 per account per region for Pro and Enterprise, à-la-carte rates for outbound ($0.10 / 1,000 emails), standard dedicated IPs at $24.95 / month / IP, archiving, validation and tenants at $0.005/month/tenant beyond the included 1,000, fees exclusive of indirect taxes, no minimum term and closure at will. The gaps are narrow but real: deliverability expert services are priced only by opening a support ticket, support plans above the $29 floor are unpriced in the captures, and we found no public information on log retention per plan.

Twilio SendGrid Email API

Two tiers are public — Essentials starting at $19.95/mo for 50,000 to 100,000 emails a month, Pro starting at $89.95/mo — with a free trial of 100 emails a day for sixty days and no credit card required. But overages are waved off as "Taxes and overages may apply", additional dedicated IPs are merely "purchasable", extra validation and testing credits carry no price, and no minimum term appears on any captured page. I can price the first year of a tier; I cannot price the month I exceed it.