Lumail vs Courier: Which Email Platform Fits How You Work?

Lumail is a Courier alternative for newsletters and agent-operated email, not for multichannel product notifications. Courier orchestrates email, SMS, push, chat, and in-app through your providers at $0.005 per send after a 10,000-send free Developer plan. Lumail is one org for campaigns, graph workflows, capture pages, and transactional SMTP/API, billed by email volume with delivery included.

Courier positions itself as the customer messaging platform for humans and AI agents: one API and dashboard to trigger, personalize, and deliver across email, SMS, push, Slack/MS Teams, and in-app. Official copy says it unifies notification infrastructure, visual Design Studio, Journeys, user preferences, and Courier Inbox so engineering and product teams share one system. You connect existing providers (SendGrid, Twilio, APNs, Firebase, Slack, and 50+ others); Courier handles routing, failover, templating, and analytics on top.

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.

ChatGPT plugin

Lumail vs Courier at a glance

Decision	Lumail	Courier
Core focus	Newsletters, workflows, transactional email, and AI-agent operations	Multichannel notification and customer messaging platform
AI and developer access	89 organization-scoped MCP tools, CLI, TypeScript SDK, REST API, AI editor	Hosted MCP at mcp.courier.com with 145 documented tools (144 default + 1 local diagnostic); CLI; agent skills; llms.txt. AI Translations and AI Agent node listed on Business. No public ChatGPT OAuth plugin catalog.
Pricing basis	Email volume, with unlimited subscribers on every plan	Per notification send across email, push, SMS, in-app, and chat; no per-seat or per-channel add-ons. Connected ESP/SMS providers bill delivery separately.
Free plan	3,000 emails per month, no credit card	Developer: free, 10,000 sends/month; Journeys and broadcasts; MCP server, CLI, and SDKs; Google/GitHub SSO; email support
Paid entry	Premium $20/month with 40,000 emails included	$0.005 per send
Automation	Graph-based workflows on every plan	Visual Journeys (directed graph) with API, webhook, Segment, and audience triggers; delays, branches, batching, digests, throttles, and an AI Agent node. Plus Automations API and single-channel broadcasts to lists or audiences.
Transactional email	Included in the same organization through API or SMTP	Core Send API use case (password resets, receipts, alerts). You connect your own ESP or SMTP (SendGrid, SES, Postmark, Mailgun, Resend, SMTP, and others). Courier is not a first-party sending MTA.
Publishing	Capture pages for subscriber acquisition	Design Studio templates and one-off broadcasts to a list or audience. Not a hosted newsletter publication and no capture pages.
Best fit	Teams operating email through agents, code, and a visual app	Product and engineering teams that already have (or want) their own email/SMS providers and need multichannel routing, preferences, and journeys on one API.

Courier's current plans come from its Courier 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.

Documented on https://www.courier.com/docs/tools/mcp (retrieved 2026-08-17): remote MCP at https://mcp.courier.com, authenticated with a Courier API key. Official count is 145 tools covering the full API: send (inline, template, list), messages, profiles, lists, audiences, notification templates, brands, automations, bulk jobs, tenants, preferences, routing strategies, journeys, providers, translations, inbound events, audit events, preference sections, digests, plus courier_installation_guide and a local-only get_environment_config diagnostic. Setup docs cover Claude Code, Cursor, Codex, VS Code, Antigravity, and Claude Desktop. Companion surfaces: @trycourier/cli, Courier Skills, REST API, server SDKs (Node, Python, Go, Ruby, Java, PHP, C#), client SDKs (React, JS, iOS, Android, React Native, Flutter), and llms.txt. ChatGPT OAuth plugin is not listed on these pages.

Choose Lumail when:

• You want campaigns, subscribers, capture pages, and transactional email in one org with Lumail delivering the mail
• You want graph workflows on every plan without bringing SendGrid/SES/Twilio (or similar) as a second vendor
• You want ChatGPT OAuth plus 89 org-scoped MCP tools aimed at running a newsletter, not only a notification API

Choose Courier if that product's model is the job

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

Choose Courier when:

• You need SMS, push, Slack/Teams, and an embeddable in-app inbox with preference enforcement and provider failover
• You already pay an ESP and want Courier only as the orchestration/routing layer
• You need multi-tenant notification branding or an AI Agent node inside journeys (Business+)

Lumail does not try to be Courier. 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

Official public meter (pricing page + JSON-LD, retrieved 2026-08-17): Developer is free forever with 10,000 sends/month; Business is pay-as-you-go at $0.005 per send; Enterprise is custom volume pricing (RBAC, EU data residency, enterprise SLA, dedicated Slack, observability integrations). Hero copy: start free with 10,000 sends a month, then $0.005 per send; no per-seat or channel add-on fees. Pricing is based on notifications sent, not team size or channels. Courier's fee is the orchestration layer; email/SMS delivery is billed by the connected provider (docs: you keep provider pricing). Docs also say billing counts sends from all environments; Business mock API keys can simulate the lifecycle without send cost. Whether Business still includes a 10,000-send monthly allowance is not stated as a separate line item—Developer is the plan that includes 10,000. Do not treat $0.005 as all-in email cost. Worked Courier-only platform fee at the published Business rate: 20,000 billed sends × $0.005 = $100, plus ESP/SMS charges; check the live pricing page before buying.

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

Journeys are a visual directed graph (docs: journeys-overview). Triggers: API invoke, inbound webhook, Twilio Segment, audience join. Nodes include send (email/SMS/push/inbox), journey-scoped templates, conditional branches, delays, external data fetch, throttling, batching, and scheduled digests. Marketing pages add an AI Agent node that can run frontier models (copy names GPT-5.4 and Claude Opus) to score users, generate content, or enrich profiles—listed as a Business feature (AI Agent node / AI Translations). Separate Automations API for template and ad-hoc automations. Broadcasts are one-off single-channel sends to a static list or dynamic audience, send-now or scheduled. Not equivalent to Lumail capture-page acquisition or a hosted newsletter.

Transactional notifications are a first-class Courier solution (password reset, verification, receipts, usage alerts). Sending is POST to Courier's Send API (or CLI/MCP/SDK); Courier then delivers through your configured providers. Email providers documented: Amazon SES, SendGrid, Postmark, Mailgun, Resend, SMTP (NodeMailer to your host), Mandrill, SparkPost, Mailjet, MailerSend, Amply, Gmail, OneSignal Email. SMTP here means Courier connects outbound to your SMTP server; there is no documented Courier-hosted inbound SMTP relay comparable to smtp.lumail.io:587. You keep sender reputation and domain auth on the ESP. Inbox is Courier-native; email is not.

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 a Courier alternative?

Yes for email newsletters, capture pages, and agent-operated campaigns with delivery included. No if you need Courier's job: one notification API across SMS, push, Slack/Teams, and in-app with BYO SendGrid/Twilio/APNs. Both expose MCP and a CLI; Courier's 145 tools wrap its notification API, Lumail's 89 org-scoped tools operate subscribers, campaigns, workflows, and transactional email in one product.

Is Lumail cheaper than Courier?

It depends on volume and whether you already pay an ESP. Courier Developer is free to 10,000 sends/month; paid usage is $0.005 per send plus provider delivery. That Courier layer alone is $5 per 1,000 billed sends. Lumail Premium is $20/month for 40,000 emails included, then $0.60 per 1,000, with delivery in-plan and unlimited subscribers. A high-volume notification app can outspend Lumail on Courier's per-send meter; a newsletter that only sends email often will not. Model both live pricing pages plus any ESP/SMS contract.

What is the main difference between Lumail and Courier?

Courier is notification infrastructure you put in front of your providers: routing, templates, journeys, preferences, and an in-app inbox, billed per send. Lumail is an email operating system: unlimited subscribers, visual campaigns, graph workflows, capture pages, and transactional API/SMTP in one org, billed by emails sent with Lumail delivering. Courier wins at multichannel product messaging; Lumail wins at running a newsletter without a second ESP.

Can I migrate from Courier to Lumail?

Only the email slice. Export user profiles, lists, unsubscribes, and templates; point transactional email at Lumail's API or smtp.lumail.io:587; rebuild one Journey as a Lumail graph workflow. Keep Courier if you still need SMS, push, chat, or Inbox—Lumail does not replace those channels. Domain auth (SPF/DKIM) moves to Lumail because it becomes the sender, unlike Courier which sent through your existing ESP.

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.