BYO-SES done two ways

Common ground

Two companies that both bet on SES — then diverged

EmailOctopus's origin story is the same argument this site makes: SES delivery at ~$0.10 per 1,000 emails is the best-priced infrastructure in email, and a good product layer on top beats paying an ESP's bundled markup. They built a genuinely polished product on that idea. Over time their center of gravity moved to a fully managed ESP — "email marketing made easy" — while the BYO-SES product became Connect, a legacy line their own docs de-emphasize for non-technical users. That's a reasonable business decision, and worth saying plainly: Connect still works if that's what you want.

SendOps made the opposite bet: your AWS account isn't a compatibility mode, it's the product. See how SendOps turns SES into a marketing platform for the full model — and if self-hosted tools like Sendy are also on your shortlist, the SendOps vs Sendy comparison rounds out the picture.

The credentials question

Pasted keys vs a role you can revoke

EmailOctopus Connect uses the connection model the whole BYO-SES category settled on: create SES credentials in AWS, paste them in, and the platform stores them to send on your behalf. In fairness, it's convenient and industry-common — setup takes minutes and EmailOctopus has run it responsibly for years.

But the model has a structural cost: long-lived credentials held by a vendor are a bigger blast radius than a scoped role in your own account. They sit in someone else's systems, remain valid until rotated, and revoking access is a chore you have to remember. SendOps connects through a CloudFormation stack that provisions a scoped IAM role in your AWS account, accessed via short-lived STS role assumption. No key is pasted or stored, the role's permissions are yours to read, its activity shows up in CloudTrail, and deleting the stack ends access completely.

The AWS onboarding gap is the other half. New SES accounts start in the sandbox, and like most of the category, EmailOctopus leaves the production-access request to you — their knowledge base helps, but you file it. SendOps automates the request as part of onboarding. Doing it yourself either way? The Amazon SES setup guide covers the sandbox exit step by step.

The platform-depth question

Polished and easy vs deep and yours

EmailOctopus's strength is polish: a clean editor, a strong template gallery, landing pages and forms, and automation that covers welcome sequences and time-based drips. For a marketer who wants campaigns out the door with minimal ceremony, it's one of the nicest tools in the category — that's true of the managed product and of Connect. The ceiling is the WYSIWYG medium itself: everything you build lives as editor state, so there's no file to diff, no query to review, and nothing an AI coding agent can operate on your behalf.

SendOps trades some of that immediate ease for depth. SendQL segments query contacts, events, and send activity — not just list fields. SendFlow workflows are multi-step and behavioral: event triggers, branching, frequency caps, written in a text DSL and visualized on a canvas. Templates are React Email components in git, compiled to SES-native Handlebars and served with an asset CDN, so email ships through the same review process as code. Analytics reach below campaign stats into deliverability — bounce and complaint trends with alerts before SES's thresholds bite. And because every one of those surfaces is text plus an API, coding agents can operate the platform end to end.

The pricing shapes are closer here than in most comparisons — both offer real free tiers, and Connect Pro at ~$8/mo billed yearly with unlimited subscribers is cheaper than SendOps Team at $29/mo (SendOps Free remains $0 with unlimited volume). The difference you're paying for is depth and the ownership model, not the delivery — which costs the same ~$0.10 per 1,000 on both; see the Amazon SES pricing breakdown.