Elastic Email: Transactional email service
Elastic Email is a Transactional email service founded in 2010, headquartered in Canada. Pricing: Free · Email API from $19/mo. It targets resellers who need their own CNAME on the interface, the SMTP host and the API endpoint. Our verdict: Four SMTP ports, twelve SDKs, and $19 for 50,000 emails. Watch for: Three days of log history free, seven paid, the shortest on this site. Rated 6.7/10 overall across ease of use, deliverability, and pricing value.
What is Elastic Email?
Elastic Email predates Amazon SES. Its founders — Joshua Perina, Michał Bochnak and, a year later, Michael Findlater — started it in 2010, and by their own account because there was then no safe way to send mail from an EC2 instance: SES only launched in January 2011.
It still runs on what they wrote: its own MTA behind mxout.mta1.net, and IP ranges allocated directly to it by ARIN in Canada and by RIPE under its Polish subsidiary in Szczecin. The other half of the business is invisible — a reseller programme that lets a partner put its own CNAME on the login page, the interface, and the SMTP and API endpoints.
Explore Elastic Email on SMTPedia
Frequently asked questions
Is Elastic Email worth it in 2026?
Our full editorial review covers pricing, deliverability, ease of use, support quality, and API/MCP maturity. Read the Elastic Email review →
How much does Elastic Email cost?
All pricing tiers, hidden fees, refund policy, and the true cost per email are broken down in the pricing tab. See Elastic Email pricing →
What are the best alternatives to Elastic Email?
Elastic Email compared with its closest competitors by use case, pricing, and switching cost. See alternatives →
What are the SMTP settings for Elastic Email?
Hostnames, ports, authentication, rate limits, and DKIM/SPF configuration for Elastic Email. See SMTP settings →
Does Elastic Email have an official MCP server?
Our API tab covers Elastic Email's REST API version, SDKs, rate limits, and MCP server support (official, community, and commercial wrappers). See API + MCP →
This review follows our email infrastructure testing methodology. We disclose affiliate relationships in our editorial independence policy.
