NitroMTA: Rust‑Based Amazon SES Replacement for Small Businesses

What NitroMTA Is

NitroMTA is an open‑source mail transfer agent that serves as a drop‑in replacement for Amazon Simple Email Service (SES) v2. The project is hosted on GitHub (GitHub) and is released under the Apache‑2.0 license. It is written in Rust and ships as a single binary that stores its data in SQLite, runs as a systemd unit, and includes a command‑line interface for administration.

SES Compatibility and Migration

The engine implements the SES v2 API surface: SendEmail, SendBulkEmail, email templates, identities, configuration sets, tenants, the suppression list, dedicated IPs, and a subset of SES‑shaped events via SNS. Because the API is identical, moving an application from AWS to NitroMTA only requires changing the endpoint URL and the access keys. The official SDKs for Python (boto3) and other languages continue to work without code changes.

Performance and Reliability

Benchmarks run on an AWS c7gd.metal server with four CPUs show NitroMTA delivering 3,313 messages per second, or 1.169 ms per message. That rate is 3.16 times faster than KumoMTA (1,048 msg/s, 2.492 ms) and 4.11 times faster than Postfix with OpenDKIM (806 msg/s, 4.969 ms). Across nine test runs the engine sustained a median of 1.35 million 16 KiB messages, each DKIM‑signed and TLS‑encrypted, with every message delivered once and verified. Durability is built in: a submission is only acknowledged after it is committed to disk, allowing the queue to survive crashes, power loss, or host failure as long as the storage remains intact. The engine also includes automatic warm‑up per receiving domain, back‑off on complaints or throttling, per‑provider connection limits, and suppression of hard bounces and spam complaints. All outbound mail is DKIM‑signed, sent over TLS, and validated with MTA‑STS and DANE where available.

Running NitroMTA on Your Own Infrastructure

Installation is available as native packages for Debian/Ubuntu (.deb), RHEL/Fedora (.rpm), Arch (AUR), Docker images, Homebrew for macOS/Linux, and generic x86_64/arm64 archives. Each package is signed by GitHub, providing provenance. The setup process consists of six steps, ending with the “nitromta doctor” command that checks reverse DNS, SPF, DKIM, DMARC, and the bounce MX record, then tells you what DNS records to publish. A capture mode lets you run the full engine locally and view each message in a browser without needing DNS or public IPs, useful for testing. To migrate, you keep your existing SES v2 code, point the SDK endpoint at the local engine (e.g., https://127.0.0.1:4443), and use the access keys generated by the NitroMTA admin CLI. The engine handles SMTP delivery, so you still need outbound port 25 open and a reverse DNS name for each sending IP.

Cost, Control, and Suitability for Small Businesses

Because NitroMTA runs on your own hardware or cloud VM, you avoid per‑message fees charged by AWS. You also gain full control over the IP addresses used for sending, which can improve reputation and deliverability when managed correctly. The built‑in warm‑up logic removes the need for a separate IP‑warming service. The solution is most appropriate for businesses that already send a moderate to high volume of email and have the ability to manage a Linux host with port 25 access. For low‑volume senders, the operational overhead may outweigh the cost savings, but the open‑source nature means you can try it in capture mode at no cost.

Takeaways

• NitroMTA provides drop‑in SES v2 compatibility, so you can switch endpoints without rewriting code.
• Performance benchmarks show over 3,000 msg/s on modest hardware, with built‑in durability and deliverability features.
• Running the engine yourself eliminates per‑message AWS fees and gives you direct control over sending IPs and warm‑up.