Stop renting. Own your email platform.

What is Jev?

A new AI model is posting numbers that look fake. They are not fake. Jev is a different kind of machine from ChatGPT or Claude, and the difference fits in two words.

SES says sent. Outlook never got it.

A bounded checklist that separates SES acceptance, SES post-accept drops, Microsoft SMTP accept, Message Trace, and when a dedicated pool changes nothing.

Before you give an AI agent your inbox

The two documented incidents, the rule the field converged on, and a permission design you can apply this afternoon.

Who owns your email list?

On paper, you do. In practice, whoever holds the rows, the consent records and the send button controls it.

The reality of a free self-hosted mail server

The rules from Google, Yahoo, Microsoft and AWS, with dates, and where Amazon SES fits.

Gmail's 0.3% spam rate

Google's daily spam rate, Yahoo's matching line, where each number lives, and a ten-minute Monday routine.

Coding agent send-only email

Send mail grants, scoped API keys, MCP versus REST, recipient discipline and a checklist for Claude Code, Cursor and Codex.

Email for SaaS founders

Wire onboarding, receipts and a newsletter through one install before a vendor review stalls your funnel.

Email for newsletter creators

Per-subscriber pricing turns growth into a cost problem. Here is what a creator's stack looks like without that tax.

Email for ecommerce stores

A profile-priced marketing cloud charges for every browser it fingerprints. Here is what a store's stack looks like billed by send instead.

Email for developers

Wiring receipts, resets and agent-triggered mail into an app: the request shape, the setup, and where a hosted API ESP still wins.

Email for agencies

Running email for many clients on one shared login turns every vendor review into your fire drill. An install per client changes who owns the risk.

Amazon SES vs SendGrid

Raw SES is cheap and bare. SendGrid adds a full hosted UI plus its own account review. SendBunny adds the UI without adding a second gatekeeper.

Amazon SES vs Resend

Raw SES is cheap infrastructure with no campaign UI. Resend rents you a polished layer on its own cloud. SendBunny installs that layer into your own AWS account instead.

SendBunny vs Sendy

Sendy is a one-time license for software you run yourself on a PHP host. SendBunny is a one-time license that installs as a serverless stack in your own AWS account.

SendBunny vs SendGrid

SendGrid bundles a hosted platform and a compliance review into one Twilio account. SendBunny installs the platform into your AWS account and leaves the review to AWS's own rules.

SendBunny vs Resend

Resend gives developers a clean send API on its own hosted stack. SendBunny gives you campaigns and a send API installed straight onto your own Amazon SES.

SendBunny vs Postmark

Postmark is polished, per-email transactional email with real support behind it. SendBunny is a one-time license that runs on your own Amazon SES.

SendBunny vs Mailgun

Mailgun's plan floors bill every month whether you send or not. SendBunny is $199 once, then Amazon SES pennies, in an account that is yours.

SendBunny vs Mailchimp

One platform installs into your AWS account and goes quiet on cost when you are not sending. The other lives on Mailchimp's servers and bills every contact whether you email them or not.

SendBunny vs Loops

Loops is a hosted all-in-one for product email. SendBunny installs the same job into your own AWS account as a one-time license.

SendBunny vs listmonk

listmonk is software you run yourself, free to download, and yours to assemble: database, app server, reverse proxy, upgrades. SendBunny is the same idea installed for you.

SendBunny vs Klaviyo

Klaviyo's ecommerce depth comes with pricing that climbs with every profile. SendBunny is a flat $199 license on your own Amazon SES.

SendBunny vs Brevo

Brevo bundles email, SMS and a sales pipeline on its own cloud. SendBunny is a one-time license that puts campaigns and a list in your AWS account.

A Sendy alternative that skips the VPS

Sendy is a genuinely good idea: pay once, send through your own SES. The part nobody prices in is the server you now maintain.

Tired of SendGrid freezing your sending?

SendGrid's automated risk systems can pause a production account mid-send. Here is what running the same job in your own AWS account changes.

A Resend alternative that skips the metering

Resend makes it easy to send your first email. What happens to the bill once your app actually has users is a separate question.

A Postmark alternative on your own SES

Postmark is a well-built transactional sender. The question is whether you want to keep renting the pipe once your volume climbs.

An OpenSend alternative you install, not rent

If you already have SES quota and reputation, the question is whether a hosted layer on top should be one you rent or one you own.

Mailgun alternative with no middleman markup

Mailgun sits between your app and the wire, and prices that seat separately from the actual delivery.

Done overpaying Mailchimp?

Mailchimp bills by the row whether you send to it or not. What switching actually costs, what carries over, and who should stay.

A Loops alternative for growing SaaS teams

Loops is a smooth way to send product email until your contact count pushes you into the next tier.

A Listmonk alternative that skips the stack build

Listmonk gives you real ownership if you enjoy assembling the stack. Not everyone who wants ownership wants that part.

Klaviyo bill too high for your list?

Klaviyo counts every popup signup and checkout as a billable profile, whether or not you ever email them. Here is the actual gap, and who should not close it.

Kit alternative without subscriber tiers

Kit's Creator Pro pricing climbs with subscriber count, whether or not you actually email that many people.

A FreeResend alternative with more than an API

FreeResend gets mail out of your app cheaply. Lists, campaigns and the ops around them are still your project to build.

A Customer.io alternative without the quote call

Customer.io does sophisticated journeys well. The pricing conversation gets harder right as your product email starts to matter.

A Brevo alternative you actually own

Brevo already prices close to send volume, so the case for leaving is not the invoice, it is who runs the app underneath it.

Grow your list without renting the platform

beehiiv's own terms say your content is yours. The platform, the send infrastructure and the subscriber tier ladder are still theirs.

ActiveCampaign power, no contact bill?

ActiveCampaign's automations run against your contact list, and the bill scales with that list, not with what the automations do.

What if your email vendor disappears?

SaaS senders sunset products, raise prices past what you can pay, and freeze accounts. What that actually costs you, and what to keep ready.

Shared IPs are hurting your deliverability

A shared IP pool spreads risk across strangers as much as it spreads cost. What mailbox providers actually check, and when a shared pool is fine anyway.

Cheap VPS mail feels free until it's spam

The VPS wins on the invoice. Amazon SES wins on whether the email arrives. A direct look at what each one actually costs.

The SES suppression list, explained

The AWS account-level list versus your own, what each one actually catches, and how to make sure no send path skips the check.

Stuck in the SES sandbox

What the sandbox limits mean, what AWS checks before approving production access, and the order to prepare things in.

SES production access denied

The likely reasons behind a vague denial, what to fix before you write another word, and how to reapply without repeating the mistake.

Tracking opens and clicks on SES

How SES event tracking actually works under the hood, why a DIY setup often reports zero opens, and what to trust once it is running.

SES warm-up, without a dedicated IP

On standard SES you send from Amazon-managed shared IPs. What you actually build during warm-up is domain reputation, and it needs a schedule, not a guess.

SES bounce rate climbing

What counts as a bounce AWS acts on, the threshold territory, and the order to fix a rising rate in before it triggers a review.

Amazon SES paused your sending

Why the pause notice went unseen, what to fix before you reply, and how to write a remediation plan AWS can check.

Sending a newsletter on SES

SES handles delivery cheaply and reliably. Everything a newsletter needs beyond that, an editor, a list, unsubscribe, is a separate build or a separate bill.

Resend was fine until volume hit

Developer-friendly pricing stays cheap at low volume. The numbers that change once sends compound.

Per-contact pricing is the trap

Contact-tier pricing charges you for people you may never email again. The mechanism, the honest exceptions, and what sending actually costs when it is billed by the send.

Still paying for unsubscribed contacts

An unsubscribe should shrink your bill. On a contact-tier plan, it usually does not, because the row still counts toward the tier that sets your price.

Own your email list, for real

Ownership on paper is a terms clause. Ownership in practice is a specific export, a consent record, and a domain that re-verifies cleanly somewhere else.

Mailchimp raised prices again?

Contact-tier pricing means growth is the trigger. The numbers, who it still suits, and the move that fixes the mechanism.

Your ESP can see your list

A hosted platform storing your contacts is not a policy choice you can opt out of by asking nicely. What the access actually looks like, sourced from the terms.

Open rates lied. What should you watch?

Open rate is a noisy proxy metric. The numbers that actually predict whether your next send gets seen.

Your email platform suspended you

Suspension is written into the terms you agreed to. Here is what to do right now, and how to stop one vendor's compliance desk from deciding whether your revenue ships.

What running your own email stack costs

Ownership was the goal. A second full-time job answering pages was not part of the deal.

Campaigns, transactional and inbox

Marketing picks an ESP, engineering picks an API, support picks an inbox tool. None of it was wrong in isolation.

Amazon SES needs a dashboard

SES is superb sending infrastructure. It was never meant to be the place you build a campaign.