Lumail vs Amazon SES: Which Email Platform Fits How You Work?

Lumail is an Amazon SES alternative when you need a newsletter platform agents can operate, not only AWS sending infrastructure. Amazon SES is a pay-as-you-go email API and SMTP service billed per message. Lumail is one organization for campaigns, workflows, subscribers, and transactional email, billed by volume with a visual editor and MCP tools SES does not ship.

Amazon Simple Email Service (Amazon SES) is a cloud-based email service provider that can integrate into any application for high-volume email automation. AWS says you can send transactional, marketing, or newsletter emails and pay only for what you use, with dedicated, shared, or owned IP options plus sender statistics and deliverability tools. The developer guide describes SES as an email platform for sending and receiving using your own addresses and domains, including marketing offers, order confirmations, and newsletters, plus inbound pipelines such as autoresponders. Mail Manager adds inbound ingress, traffic policies, SMTP relay, archiving, and security add-ons.

This comparison uses public product information checked on 2026-08-17. Check each pricing page before purchasing because plans, limits, and catalogs change. For a condensed version, see the side-by-side comparison table.

Workflow graph

Lumail vs Amazon SES at a glance

Decision	Lumail	Amazon SES
Core focus	Newsletters, workflows, transactional email, and AI-agent operations	Cloud email sending infrastructure (API and SMTP)
AI and developer access	89 organization-scoped MCP tools, CLI, TypeScript SDK, REST API, AI editor	SESv2 MCP Server is an official AWS sample (GitHub), not recommended for production; it exposes public SES v2 API actions. Separate open-source Agent Skills (aws-ses, aws-mail-manager) teach coding agents the V2/Mail Manager APIs. AWS MCP Server (preview) is a general AWS agent surface, not an SES-specific tool catalog. No published SES MCP tool count.
Pricing basis	Email volume, with unlimited subscribers on every plan	Per email sent or processed, with optional monthly plan fees and add-ons. Charged per recipient for outbound SES. New accounts default to Essentials as of 21 Jul 2026 unless switched to à la carte.
Free plan	3,000 emails per month, no credit card	No standing SES-only free sending allotment on the live pricing page. New AWS customers get up to $200 Free Tier credits (free plan option lasts 6 months). New SES accounts start in the sandbox: 200 messages per 24 hours, 1 per second, verified recipients only.
Paid entry	Premium $20/month with 40,000 emails included	$0.10 per 1,000 outbound emails (à la carte, no monthly minimum)
Automation	Graph-based workflows on every plan	No visual campaign journeys in SES. Inbound automation via Mail Manager rules and classic receipt rules (Lambda, S3, SNS). Outbound automation is your application, EventBridge, or another AWS service. Amazon Pinpoint campaigns/journeys used SES for delivery; Pinpoint console support ends 30 Oct 2026.
Transactional email	Included in the same organization through API or SMTP	Core product. Send via SES API v2 (SendEmail/SendBulkEmail) or SMTP (STARTTLS on 25/587/2587; TLS Wrapper on 465/2465). Same per-email rates as marketing mail. Omit ListManagementOptions so transactional mail is not unsubscribable via SES list management.
Publishing	Capture pages for subscriber acquisition	No hosted newsletter publication, visual campaign editor, or capture pages. Console manages identities, configuration sets, and test sends. Templates (Handlebars, stored or inline) and contact lists exist as APIs, not a CMS.
Best fit	Teams operating email through agents, code, and a visual app	Engineering teams on AWS who need high-volume transactional and bulk sending (and optional inbound processing) at the lowest public per-email rates, and who will build lists, editors, and journeys themselves.

Amazon SES's current plans come from its Amazon SES pricing. Lumail's plans are on the Lumail pricing page.

Choose Lumail if agents should operate your email

Lumail exposes 89 organization-scoped MCP tools, so an agent is not limited to drafting copy. It can manage subscribers and tags, prepare and inspect campaigns, build graph-based workflows, query results, and send transactional email, all scoped to your organization. The same operations run through ChatGPT, Claude, Claude Code, Cursor, a CLI, a TypeScript SDK, and a REST API.

Not a production SES MCP product. AWS published a SESv2 MCP Server sample (https://github.com/aws-samples/sample-for-amazon-ses-mcp, blog 5 Jun 2025) that exposes all public SES v2 API actions (send, identities, templates, contact lists, suppression, VDM recommendations). AWS states it is a sample, Smithy Java / Java 21, and not recommended for production. Example uses listed: send simple or templated mail, dedicated IP pools, deliverability metrics, contact lists, suppression lists. No official published tool count. Amazon SES Agent Skills (blog 4 Jun 2026, GitHub amazon-ses/skills, Apache-2.0) add aws-ses (sesv2 sending) and aws-mail-manager (inbound) context for Kiro, Claude Code, and Agent Skills-compatible clients — skills, not a hosted MCP catalog. AWS MCP Server (preview) is a managed general AWS MCP (docs, skills, IAM-authenticated API execution) and can reach SES only as part of AWS APIs; it is not documented as an SES-specific 89-tool surface. Programmatic access that is production-supported: SES API v2, SMTP, AWS SDKs, and AWS CLI. ChatGPT OAuth plugin for SES is not documented.

Choose Lumail when:

• You want a newsletter platform (editor, capture pages, graph workflows, subscribers) rather than a sending API you have to productize
• You want 89 organization-scoped MCP tools plus ChatGPT OAuth, CLI, SDK, and REST so agents operate campaigns and workflows, not only SendEmail
• You do not want AWS sandbox approval, IAM, regional quotas, or to assemble Pinpoint/Lambda/EventBridge for journeys

Choose Amazon SES if that product's model is the job

Amazon SES is built for a different operator. That is not a slight; it is the comparison.

Choose Amazon SES when:

• Raw delivery cost dominates and you can live with $0.10–$0.16 per 1,000 emails plus AWS operational overhead
• You already build email in application code on AWS and only need API/SMTP, events, and deliverability tooling
• You need inbound gateway, archiving, dedicated IP pools, or multi-region SES features (Global Endpoints, tenants) that Lumail does not sell

Lumail does not try to be Amazon SES. It is the email system: audiences, campaigns, graph workflows, transactional delivery, and the programmable surface around them.

Compare the pricing model, not the sticker price

Live pricing (retrieved 2026-08-17) is pay-as-you-go with no contracts. À la carte outbound email is $0.10 per 1,000 emails plus $0.12 per GB of outgoing mail data in official examples (footnote describes attachment data). Inbound email is $0.10 per 1,000 plus $0.09 per 1,000 incoming chunks. Three plans launched 21 Jul 2026: Essentials $0.16 / $0.14 / $0.11 per 1,000 at 0–10M / 10–100M / >100M emails (no monthly fee); Pro $0.22 / $0.17 / $0.12 plus $105 per account per region per month; Enterprise $0.23 / $0.18 / $0.13 plus $500. Tiers are marginal and apply separately to outbound vs Mail Manager processing. New SES accounts with no metered activity since 1 Jun 2025 start on Essentials unless switched to à la carte. Official Example 1: 250,000 Essentials emails at 32KB = $40.00 + $0.96 data = $40.96. Example 4 à la carte 2M outbound with VDM, managed dedicated IPs, Global Endpoints, and Mail Manager = $1,963.31. Add-ons (à la carte): dedicated IP standard $24.95/IP/month; managed dedicated IPs $15/account/month plus per-email fees; VDM SES deliverability $0.07/$0.05/$0.02 per 1,000 by volume; VDM global $1,250/month; Mail Manager open/mTLS ingress $50/endpoint/month; Mail Manager processing $0.15 per 1,000. Other AWS services (EC2, S3, SNS, CloudWatch) can add charges. Check https://aws.amazon.com/ses/pricing/ before buying; the SES FAQ still mentions 3,000 free message charges/month for 12 months, which the live pricing page no longer lists.

Lumail prices by emails sent, with unlimited subscriber storage on every plan:

• Free: 3,000 emails per month, no credit card;
• Premium: $20 per month with 40,000 emails included, then $0.60 per 1,000;
• Business: $200 per month with 400,000 emails included, then $0.40 per 1,000.

List growth alone never raises the Lumail bill. Only sending does. Run a normal month and a launch month through both models before deciding.

Compare automation and transactional email

SES is not a visual automation platform. Outbound journeys, wait steps, and branching are not SES features; you implement them in your app or with Lambda/EventBridge/Step Functions. Mail Manager provides inbound automation: ingress endpoints, traffic policies, rule sets (sort/route/archive/relay), SMTP relay, address lists, and add-ons (Trend Micro, Spamhaus, etc.). Classic SES receiving uses receipt rules to S3, SNS, or Lambda. Contact lists and topics plus ListManagementOptions add one-click unsubscribe and SES-hosted preference pages, which is list hygiene, not workflow automation. Stored/inline Handlebars templates and SendBulkEmail support personalized bulk sends. AWS historically pointed marketers needing campaigns, segments, and multi-step journeys to Amazon Pinpoint, which used SES for email; AWS documents Pinpoint console and resources (endpoints, segments, campaigns, journeys, analytics) as ending support on 30 Oct 2026. Do not treat Pinpoint journeys as a current SES product surface.

Transactional mail is a first-class SES use case (purchase/shipping notifications, status updates) at the same outbound rates as marketing. Send with SES API v2 SendEmail or the SMTP interface; production sending requires leaving the sandbox (AWS Support typically responds within 24 hours; approval is not guaranteed). SMTP needs region-specific credentials distinct from IAM console keys; TLS is required. Message size: 40MB on API v2/SMTP, 10MB on API v1; >10MB may be bandwidth-throttled. Max 50 recipients per message (quotas doc). Events (bounce, complaint, delivery, open/click if configured) go to SNS, CloudWatch, Firehose, or Pinpoint event destinations via configuration sets. Mailbox simulator tests bounces/complaints and is billed like real outbound. For transactional mail you do not want unsubscribe links, omit ListManagementOptions. Inbound is separate: SES receiving and/or Mail Manager, not required for outbound transactional.

Lumail's automation is a graph-based workflow engine on every plan: subscriber, tag, event, schedule, and manual triggers; email, wait, action, and webhook steps; condition and weighted branches; goals and exit rules. Transactional messages go through the REST API or smtp.lumail.io:587 with STARTTLS, inside the same organization as campaigns.

Questions people ask ChatGPT

Is Lumail an Amazon SES alternative?

Yes if you want a hosted newsletter and automation platform instead of AWS sending infrastructure. SES is a pay-as-you-go API and SMTP relay for transactional, marketing, and newsletter sends you build yourself, plus optional inbound Mail Manager. Lumail includes unlimited subscribers, graph workflows, capture pages, transactional SMTP in the same org, and 89 organization-scoped MCP tools. SES remains the fit when you only need to send from code on AWS.

Is Lumail cheaper than Amazon SES?

Usually not for raw sending. SES à la carte is $0.10 per 1,000 outbound emails with no monthly minimum; Essentials is $0.16 per 1,000. AWS’s official 250,000-email Essentials example totals $40.96 including mail data. Lumail Premium is $20/month for 40,000 emails then $0.60 per 1,000; Business is $200/month for 400,000 then $0.40 per 1,000. SES is cheaper per send. Lumail prices the editor, workflows, and agent surface you would otherwise build on SES.

What is the main difference between Lumail and Amazon SES?

SES is email infrastructure: API, SMTP, IAM, sandbox quotas, deliverability add-ons, and optional inbound gateway. You own lists, editors, journeys, and how agents call SendEmail. Lumail is the operating surface: campaigns, graph workflows, capture pages, and transactional mail in one org, billed by volume. AWS pointed campaign/journey UX at Pinpoint, which ends console support on 30 Oct 2026; SES does not replace that with a Lumail-style canvas.

Can I migrate from Amazon SES to Lumail?

Yes for subscribers and sending. Export contacts from SES contact lists or your own database and recreate campaigns and workflows in Lumail; SES has no hosted newsletter publication to import. Point app mail at Lumail’s API or smtp.lumail.io:587 STARTTLS, or keep SES for transactional and use Lumail for the newsletter. Re-verify the sending domain (SPF/DKIM) on Lumail. Production SES quotas and dedicated IPs do not transfer.

Try the workflow that matters most

Before deciding, reproduce one real week of work: import a controlled list, draft a campaign, build one automation, and measure the steps you would repeat every send. Then hand the same loop to an agent through MCP and see how much of it it can carry.

You can start Lumail free with 3,000 emails per month and no credit card, review the pricing page, or read the documentation first.

Still evaluating? Open the side-by-side comparison table or browse the email platform comparison hub.