The zero-infra alternative to self-hosted SES wrappers.
Self-hosted and bring-your-own-cloud SES tools promise SES prices with a nicer API. The catch is that the backend runs in your AWS account, and so does the bill, the upgrade work, and the pager. MailEnv gives you the API without the infrastructure.
A self-hosted wrapper is still infrastructure you own.
The install might take one command. Running it takes forever. Depending on the tool, these are the costs that land on your team after day one.
Function executions
Every send, every SES event, and every webhook retry is a Lambda invocation on your AWS bill, along with the CloudWatch logs it writes.
Database storage
Message history, event logs, and suppression lists grow forever in DynamoDB or Postgres, unless you build retention yourself.
Runtime deprecations
AWS retires old Node.js Lambda runtimes on a schedule. When that happens, someone has to upgrade, redeploy, and retest the email pipeline.
CloudFormation drift
Someone changes a setting in the console, and the next stack update fails or quietly reverts it. Now email setup is part of your IaC review.
Security surface
IAM roles, queue policies, and webhook endpoints in your account are yours to audit, patch, and explain to your SOC 2 auditor.
On-call
When bounce rates spike at 2 a.m. or a queue backs up, the alert goes to your team, not the tool's maintainers.
Both get you SES delivery. The difference is who runs it.
Choose MailEnv if you want
- Zero infrastructure in your own cloud account
- No AWS account, IAM policies, or SES sandbox
- Suppression, throttling, and warmup that someone else operates
- A person to help with DNS, DMARC, and deliverability
- Predictable monthly pricing instead of a multi-line AWS bill
Choose a self-hosted wrapper if you want
- All email data to stay inside your own AWS account
- Raw SES per-message pricing at very high volume
- Source code you can fork and modify
- A platform team that already runs Lambda and SQS in production
Managed SES vs self-hosted, line by line.
| MailEnv | Self-hosted or BYOC wrapper | |
|---|---|---|
| Where it runs | MailEnv's infrastructure. | Your AWS account. |
| AWS account | Not needed. | Required, including your own SES production access. |
| What you pay | One monthly plan. | SES, plus Lambda, queues, database, logs, and data transfer. |
| Upgrades | Ours. | Yours: runtimes, dependencies, and stack updates. |
| Reputation limits | Throttled or paused before SES thresholds. | Depends on the tool. Your SES account is on the line. |
| Sender vetting | Every account reviewed. | Not applicable. You're the only sender. |
| Support | People who know deliverability. | GitHub issues, or your own team. |
Self-hosted tools vary. Some deploy a full serverless stack, and others run as a single container you host yourself. Check what a given tool installs before you compare costs.
Tear down the stack. Keep the reputation.
Moving from a self-hosted wrapper is mostly a URL and key change. You keep your domain, your DKIM keys, and your DMARC policy.
- Bring your suppression list. We import it so blocked addresses stay blocked.
- Swap one request. Point your send call at MailEnv and update your webhook handler.
- Delete the stack. Remove the functions, queues, and tables when you're ready.
await fetch('https://pub-api.mailenv.com/api/v1/send-mail', { method: 'POST', headers: { Authorization: API_KEY, 'Content-Type': 'application/json' }, body: JSON.stringify({ to, from, subject, message, email_type: 'tx' }), }); // Nothing to deploy. Nothing in your AWS account.
What is a self-hosted or BYOC SES wrapper?
It's a tool that deploys an email API into your own AWS account, in front of your own SES. Bring-your-own-cloud (BYOC) tools install the backend for you. Open-source tools give you the code to run. Either way, the infrastructure runs and bills in your account.
Managed SES vs self-hosted: which is cheaper?
Raw SES sending is cheap either way. The difference is everything around it: function invocations, queues, database storage, logs, and the engineering time to upgrade and monitor it all. For most teams sending critical transactional mail, that time costs more than a managed plan.
When does self-hosting make sense?
When you already have a platform team that runs AWS, you need email data to stay inside your own account for policy reasons, or you send enough volume that per-message costs dominate. If none of those apply, a managed service is usually the simpler choice.
Will I lose my reputation if I switch?
No. You send from your own domain with your own DKIM keys and DMARC policy, so your domain reputation moves with you. We help you bring your suppression list across so blocked addresses stay blocked.
Is MailEnv open source?
No. MailEnv is the managed option: we run the infrastructure and the on-call so you don't have to.
Get SES delivery with nothing to deploy.
We'll review what you send, help verify your domain, and bring your suppression list across.