Stop sending to addresses that already bounced.
Hard bounces and complaints come back from SES and suppress the contact before the next send. If complaints or bounces climb on a sender, sending pauses on its own before Gmail starts filtering you.
For teams sending through Amazon SES
Keep your Amazon SES. Lose the duct tape.
HeySender puts campaigns, automations, signup forms and a clean API on top of the SES account you already own. AWS keeps billing you for sending at AWS prices. HeySender adds nothing to that bill.
Not open for signups yet. When your invite arrives you start on the free plan, no card needed.
Tag addedcustomerTrigger
Plan is Pro?Profile fieldYes
Send the Pro welcome emailFrom your own SES accountEmail
Tested on a real contactEvery step shown before publishingPassed
Sound familiar?
You picked SES so you would own your email. Now you own the chores too.
Sending through Amazon SES is a smart call. It is cheap, the account is yours, and your domain's reputation is built on your own sending.
Then the list grows. Someone wants a signup form with double opt-in. Marketing wants a welcome series. A hard bounce has to stop the next send. Gmail and Yahoo want a one-click unsubscribe that actually works. And every newsletter still waits for the one person who knows where the scripts live.
So you bolt a front end on top. Or you pay for a platform that ignores your SES account and sends through its own servers anyway.
Either way, you are babysitting the one part of the business that should run itself.
The missing layer
HeySender is everything around the send. SES stays the engine.
You keep your SES account, your domain and your AWS price. HeySender adds the part SES never had: contacts and consent, campaigns, automations, forms, transactional email, bounce handling and reporting, in one place your whole team can use.
Connect your SES account once. After that, the only AWS screen you will open is the invoice.
That assumes your SES account is out of the sandbox. If it is not, HeySender tells you exactly which request to file with AWS and checks again on its own.
- Connect SES once. Launch the ready-made CloudFormation stack in your AWS account and paste the role it creates. HeySender never asks for AWS access keys.
- Bring your contacts. Upload a CSV with a dry run first, so you see what will change before anything does. Or send them through the API.
- Send and automate. Campaigns, automations and forms go out through your SES account. Bounces and complaints flow back and are handled for you.
What changes
Less babysitting. More sending.
Every point below is working in the product today. Nothing on this page is a roadmap item.
Press publish without the stomach drop.
Run any automation on a real contact first and see every email, wait and decision they would get. Published versions are locked, so a later edit never changes what people already in the flow receive.
Hand the newsletter to a colleague, not the keys.
Roles decide who can edit, who can send and who can only look. Sign-in supports two-factor codes, and consequential changes land in an audit log with who did what.
Clean the list before it costs you your reputation.
Verify addresses during import, through the API or one at a time with your own Reoon key. Invalid addresses are suppressed, and risky ones are tagged or held back from campaigns, whichever you choose.
Know every signup really opted in.
Double opt-in forms for your site, plus a permanent consent record of what each person agreed to, when and where. Preference topics let people turn down one kind of email without leaving entirely.
Receipts and password resets that never get caught in a marketing unsubscribe.
Transactional email has its own API, stream and rules on the same SES account. Someone who unsubscribes from your newsletter still gets their password reset.
Let an AI assistant do the routine work, on a leash.
Connect Claude or any MCP client. It can look things up, draft and prepare, but publishing, deleting, bulk changes and sends show you a preview first and wait for your yes.
An unsubscribe link that meets the Gmail and Yahoo rules.
Every marketing email carries one-click unsubscribe headers and a working link, and the unsubscribe takes effect immediately.
For the developer on the team
One API call and the welcome series starts.
Add a contact with a tag and every automation listening for that tag picks it up. The API, the app and the MCP server share the same permissions, so nothing gets a back door.
- Bearer keys with scopes, never tokens in a URL
- Idempotency keys, so a retry never creates a duplicate
- Signed webhooks with a delivery log you can replay
- Cursor pagination and one error format everywhere
POST /v1/contacts
curl https://app.heysender.io/v1/contacts \ -H "Authorization: Bearer hs_live_…" \ -H "Idempotency-Key: signup-8421" \ -H "Content-Type: application/json" \ -d '{ "email": "ada@example.com", "first_name": "Ada", "tags": ["customer"] }'
Straight talk
Three things we will never promise you.
If a platform promises you any of these, ask how.
Inbox placement
Nobody controls Gmail's filters. HeySender enforces the practices that help, and shows you the numbers so you can see it working.
Unlimited anything
Every plan has limits you can see. You get warnings at 70, 85 and 100 percent, so a limit never surprises you.
A cut of your sending
AWS bills you directly for SES. HeySender charges for your plan, and never adds a markup to what AWS charges you.
Be honest with yourself
HeySender is not for you if…
- You bought, rented or scraped your list. HeySender is for permission-based email only, and accounts that send to lists like that get shut down.
- You never want to touch AWS. You need your own SES account. A plain SMTP server also works, but it gives no bounce or complaint feedback.
- You need SMS or WhatsApp. HeySender is email only.
- You want someone else to own your deliverability. Your sending account means your reputation. HeySender makes looking after it easier, not optional.
Pricing
Start free. Pay for contacts, not for sending.
Developer is free with 500 contacts, 2,500 deliveries a month, the API and the MCP server. Starter is €29 a month for 5,000 contacts with forms, transactional email and webhooks. Your SES bill stays between you and AWS.
The cost of waiting. Every month on the patchwork is another month where one broken script or one missed bounce can put your domain in the spam folder. Protecting a sender reputation takes minutes a week. Rebuilding one can take months.
Early access
Get your invite.
HeySender is not open for signups yet. Here is exactly what happens:
- Fill in the form. It takes under a minute.
- A person reads your request and replies by email, usually with a question or two about your setup.
- When your invite arrives, you start on the free Developer plan. No card needed.
P.S. If you only remember one thing: you keep your SES account and your AWS price, and HeySender takes care of everything around the send. Request your early access.