Blog
Field notes
Amazon SES operations, email deliverability, and what we learn building managed email for applications.
ESP vs Amazon SES vs self-hosted email: choose the work you own
An ESP, direct Amazon SES, and an open-source mail server move different responsibilities onto your team. For application email, compare the operating boundary before comparing the price per thousand.
Read
Guides8 minAmazon SES production setup: review the whole sending path
Leaving the SES sandbox is one checkpoint, not a production-readiness test. Review regional access, identity, credentials, feedback, recipient policy, and ambiguous sends before application traffic depends on them.
Comparisons7 minESP vs Amazon SES vs self-hosted email: choose the work you own
An ESP, direct Amazon SES, and an open-source mail server move different responsibilities onto your team. For application email, compare the operating boundary before comparing the price per thousand.
Comparisons7 minSelf-hosted email server cost: budget the operation, not the VM
A mail server invoice is not a mail service budget. Separate outbound application sending from mailbox hosting, then count storage, recovery, network policy, maintenance, and the engineering time your design actually needs.
Engineering8 minSES bounces, complaints, and suppressions are a feedback loop
Bounce and complaint events should change future sending, not just update a chart. Here is the state model behind an SES feedback pipeline, including authentication, correlation, suppression scope, and uncertain outcomes.
Product7 minWhy we built SendHog: SES is transport, not your email operation
Amazon SES transports application email. Your application still needs to identify each logical send, handle an uncertain response, and act on feedback. We built SendHog to manage that boundary, not to make email guarantees SES cannot make.
