SES will send a million emails for about $100 and give you no way to write one. That gap is a whole product category: campaign tools that supply the editor, the list management and the scheduling, and hand the actual sending to an SES account you own.
The useful axis between them is not features, it is how much you operate. Everything below is described by deployment shape for that reason. Plans and prices in this category change often — treat any number you find, here or elsewhere, as a prompt to go look.
Sendy
sendy.coThe original of this category and still the most literal version of it. You buy a license, install the application on your own server, point it at your SES credentials, and it is entirely yours after that. No subscription, no vendor holding your list.
You want the cheapest possible long-run cost and you are comfortable running and updating a PHP app, including the server it sits on and the backups.
EmailOctopus
emailoctopus.comA hosted campaign product with a friendly editor, historically offered both on its own sending infrastructure and in a mode where you supply SES credentials and pay less. Check which mode a given plan is on before assuming your sending runs through your account.
You want a hosted tool with a gentle learning curve and are happy to let somebody else host the app as long as the sending is on your SES.
MailBluster
mailbluster.comBuilt specifically as a front end for SES sending. You connect your AWS credentials, it runs the campaigns, segmentation and subscriber management, and the mail leaves through your account.
You are running list-based marketing at volume and want SES economics without operating anything yourself.
Mailblast
mailblast.ioThe same shape as MailBluster: a hosted campaign layer that sends through the SES account you connect. Positioned tightly around SES rather than as a general ESP.
Same audience as above. Worth pricing both, since the two compete directly and the difference is mostly UI and plan structure.
Wraps
wraps.devOurs, so weigh it accordingly. The difference from everything above is that the others connect to SES you already set up; Wraps deploys the sending infrastructure — SES, EventBridge, SQS, Lambda, DynamoDB, IAM — into your account with one CLI command, and on the Production and Enterprise presets the raw delivery events land in a DynamoDB table you own. Templates are React Email components in your repo. Contacts, templates, workflows and a per-message send record live in our database, not yours, so this is a copy in your account rather than the only copy.
You have engineers, you are already on AWS, and you want transactional and marketing on one pipeline you own. Not for you if nobody wants an AWS account.
The question that separates them
Ask where the delivery events go, and specifically whether you get a copy or the only copy. Most of this category connects to your SES for sending and then keeps the opens, clicks and bounces in the vendor's own database, which means the economics are yours but the data is not. Wraps writes them to a table in your account and keeps its own copy to render the dashboard, which is better than one but is not the same as sole custody. That is a perfectly reasonable trade either way, and it is worth making knowingly.
Second question: what happens to your campaigns if the vendor goes away. A self-hosted install keeps running. A hosted UI over your SES stops, though your domain reputation and suppression list survive because those live in your AWS account either way. That last part is the real benefit of this whole category over a conventional ESP.
If you want the Wraps one
The marketing page covers what the campaign side does and, more usefully, three things it does not.