Amazon SES reliability, without the infrastructure headaches.
SES is one of the most reliable and cost-effective ways to send email. It's also a pile of console settings, DNS records, SNS topics, and sending limits. MailEnv gives you SES delivery behind one API key and handles everything around it.
import MailEnv from '@mailenv/sdk'; const mail = new MailEnv({ apiKey: process.env.MAILENV_API_KEY }); await mail.send({ from: 'billing@acme.com', to: ['dana@example.com'], subject: 'Receipt #10482', html: receiptHtml, tags: ['receipt', 'billing'], }); // Authentication, suppression, throttling and // bounce handling all run on MailEnv's side.
What "just use SES" actually involves.
Every item in the middle column is something your team has to build, monitor, and get right. With MailEnv, it's already done.
| Raw Amazon SES | MailEnv SES Send API | |
|---|---|---|
| Getting started | Request production access out of the sandbox and wait for AWS review. | We review your use case and get you sending on an established account. |
| Domain setup | Create identities, publish DKIM CNAMEs, write SPF and DMARC by hand, set up a custom MAIL FROM domain. | Exact records generated for you and alignment confirmed before go-live. |
| Bounces & complaints | Wire SNS topics to an endpoint, parse notifications, and build your own suppression logic. | Handled and suppressed automatically across every send. |
| Reputation limits | Watch the dashboards yourself. Exceed the thresholds and your account goes under review or gets paused. | Throttling and pauses kick in before you get near the limits. |
| Warmup | Plan and run your own ramp schedule. | Managed ramp schedules, with automated warmup on dedicated IPs. |
| Events | Configuration sets, event destinations, and more AWS services to glue together. | Signed webhooks for delivery, bounce, and complaint events. |
| Support | AWS support plans and forums. | Real people who know email deliverability. |
A REST API wrapper for Amazon SES, fully managed.
MailEnv sits between your app and Amazon SES. Your code makes one authenticated HTTP call. We run the SES identities, event pipelines, and safety checks behind it.
- No AWS account or IAM. No AWS credentials in your app and no SES sandbox to get out of.
- Events without the plumbing. SES bounce and complaint notifications become suppression entries and signed webhooks.
- Guardrails on every request. Suppressed and unverified addresses are blocked before they reach SES.
Everything between your app and the inbox.
One API key
A clean REST endpoint plus Node, Python, and Go SDKs. No IAM policies, no AWS credentials in your app.
Domain & DNS setup
SPF, DKIM, DMARC, and custom MAIL FROM, configured and checked so your mail authenticates on day one.
Automatic suppression
Hard bounces and complaints are blocked from future sends before they can damage your sender score.
Rate limits & warmup
Sending ramps at a pace mailbox providers trust, with throttling during spikes.
Signed webhooks
Delivery, bounce, and complaint events pushed to your endpoint and signed for verification.
Monitoring
Bounce and complaint trends tracked continuously, with alerts before they become account problems.
Your login flow shouldn't depend on your last newsletter.
When transactional and bulk mail share a sending reputation, a bad campaign can delay password resets and sign-in codes. MailEnv keeps those risks apart.
- Tag every message by type so you can see exactly how auth, billing, and alert mail is performing.
- Isolated environments on dedicated plans give transactional traffic its own IPs and infrastructure.
- Regional routing and failover on dedicated plans for teams that can't afford a gap.
Is MailEnv an Amazon SES API wrapper?
Yes. MailEnv is a managed REST API wrapper for Amazon SES. You send with one API key and a JSON request, and MailEnv handles the SES side: domain identities, DKIM, bounce and complaint notifications, suppression, and sending limits.
What is a managed SES proxy?
A managed SES proxy sits between your app and Amazon SES. Your app calls the proxy instead of the AWS API, and the proxy adds the parts SES leaves to you, such as suppression lists, throttling, warmup, monitoring, and signed delivery webhooks.
Do I need an AWS account to use MailEnv?
No. You don't need an AWS account, IAM policies, or AWS credentials in your app. We review your use case and you send on established MailEnv sending infrastructure.
Why use a REST wrapper instead of the AWS SDK?
Calling SES directly works, but you still have to request production access, publish DNS records, wire SNS topics for bounces and complaints, build suppression logic, and watch reputation thresholds. A managed wrapper does that work for every message.
Can I still send from my own domain?
Yes. You send from your own domain with your own DKIM keys and DMARC policy. The reputation you build stays with your domain.
Get the deliverability of SES without the setup.
Tell us what you send. We'll review your account, help verify your domain, and get you an API key.