Skip to content
Back to Lumail Notes
9 min reademailtoolscomparison

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

Courier routes product notifications across channels through your own providers. Lumail sends newsletters and transactional email itself. Compare the fit.

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

Courier is a notification layer that routes product messages across email, SMS, push, chat, and an in-app inbox through delivery providers you connect and pay separately; Lumail is an email platform that sends your campaigns, workflows, and transactional email itself, and that AI agents can operate through 89 MCP tools.

The question is whether you need many channels or one channel done completely. A product that must reach users by SMS, push, Slack, and an in-app inbox needs something like Courier. A team whose messages are all email usually does not need a routing layer in front of a separate email provider. Courier facts in this comparison come from its official pricing page as of August 2026; verify current limits before purchasing, because plans change. For the compact version, see the side-by-side comparison table.

Lumail vs Courier at a glance

DecisionLumailCourier
Core focusCampaigns, workflows, transactional email, and AI-agent operationsMultichannel product notifications routed through your own providers
Pricing basisEmail volume, delivery included; unlimited subscribersPer notification sent; your providers bill delivery separately
Free plan3,000 emails per month, no credit cardDeveloper plan: 10,000 sends per month
Paid entryPremium: $20/month with 40,000 emails included$0.005 per send, no seat or channel fees
AI and developer access89 MCP tools, ChatGPT app, CLI, TypeScript SDK, REST APIHosted MCP with 145 tools, CLI, agent skills, SDKs
AutomationGraph workflows on every planVisual journeys with branches, delays, digests, and throttling
Transactional emailSent by Lumail through API or SMTPCore use case, delivered through your connected email provider
Best fitTeams running newsletters and product email through agents and codeProduct teams sending notifications across many channels

Lumail's current plans are on the Lumail pricing page.

Choose Lumail if AI agents should operate your email

Courier takes agents seriously. It runs a hosted MCP server with 145 tools, plus a CLI, agent skills, and server and client SDKs, so a coding agent can send notifications, manage templates, and debug deliveries. What those tools operate is a notification API: messages, profiles, lists, journeys, and preferences. Courier does not list a ChatGPT app.

Lumail's 89 organization-scoped MCP tools operate an email program instead: campaigns, subscribers, tags, segments, workflows, templates, analytics, and transactional sending. The same operations run in ChatGPT, Claude, Claude Code, and Cursor, and through a CLI, a TypeScript SDK, and a REST API.

In practice that means you can ask an assistant to:

  • draft this month's newsletter from your release notes and send a test;
  • segment subscribers by tag or engagement before a targeted send;
  • build a welcome workflow and explain why a subscriber took a specific branch;
  • send a transactional email from a template while you test a new flow;
  • summarize last month's campaign results without exporting a CSV.
ChatGPT plugin
Lumail connected inside ChatGPT as an email marketing app with a Try in chat action
ChatGPT can draft campaigns, inspect subscribers, and build workflow drafts through Lumail. Send, schedule, publish, and delete stay out of the plugin on purpose.

The second difference is who delivers the mail. Courier is not an email sender: it hands each email to SendGrid, Amazon SES, Postmark, Mailgun, Resend, or another provider you connect, and that provider bills you for delivery. Lumail is the sender. One vendor, one domain configuration, and one place to look when an email does not arrive.

Choose Courier if you send notifications across many channels

Courier's strength is breadth. One Send API reaches email, SMS, push, Slack, Microsoft Teams, WhatsApp, and Courier Inbox, an in-app notification feed you embed in your product. It enforces user preferences across all of them and fails over between providers when one is down. Lumail does none of that; it is email only.

Its pricing is also simple for a routing layer: no per-seat fees, no per-channel add-ons, and a free Developer plan with 10,000 sends a month.

Choose Courier if:

  • you need SMS, push, Slack or Teams, and an in-app inbox with preference controls and provider failover;
  • you already pay an email provider and want Courier only as the orchestration layer;
  • you need multi-tenant notification branding or an AI Agent step inside journeys, available on Business.

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

Compare the pricing models, not the starting prices

Courier charges per notification sent, across every channel. The Developer plan is free for 10,000 sends a month. Business is pay-as-you-go at $0.005 per send, or $5 per 1,000, and Enterprise is custom. That fee pays for orchestration only: your email and SMS providers bill delivery on top.

Lumail prices by emails sent, with delivery included and unlimited subscribers on every plan:

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

A worked example

Say your product sends 20,000 emails a month: a newsletter plus receipts, password resets, and account alerts. No SMS, no push.

At Courier's published Business rate, 20,000 sends is $100 in Courier fees, before your email provider charges for delivering them. On Lumail, 20,000 emails fits inside Premium, so the month is $20 with delivery included.

The comparison changes if you truly need other channels. Lumail cannot send an SMS or a push notification, so a multichannel product would still need Courier or something like it. The honest question is whether your email volume should flow through a per-send routing layer at all. For many teams, the answer is to keep email on a platform that sends it directly and use a router only for the channels that need one.

Compare automation and transactional email

Courier's journeys are a visual graph built for product events. They can start from an API call, an inbound webhook, Segment, or a user joining an audience, then send on any channel, branch, wait, fetch outside data, throttle, batch, and roll messages into digests. Broadcasts cover one-off sends to a list or audience. There is no hosted newsletter and no capture page.

Lumail's workflow engine is graph-based and included on every plan: subscriber, tag, event, schedule, and manual triggers; email, wait, action, and webhook steps; condition and weighted branches; goals and exit rules. It is narrower than Courier's (email only) and deeper on the email side, with capture pages feeding the audience that workflows act on.

Transactional email is Courier's core use case, but the email itself goes out through your connected provider, which also holds your sender reputation. Lumail sends transactional messages directly through the REST API or the SMTP relay at smtp.lumail.io:587 with STARTTLS, from the same organization as your campaigns.

Migrating from Courier to Lumail

Only the email slice moves. Decide first whether Courier stays for other channels.

  1. Decide what moves. List which notifications are email only. Keep Courier for SMS, push, chat, and Inbox if you still need them.
  2. Export profiles and preferences. Export user profiles, lists, and unsubscribe preferences so opted-out users stay opted out in Lumail.
  3. Authenticate your sending domain in Lumail. Lumail becomes the sender, so SPF and DKIM move from your old email provider to Lumail. Keep the old path live while DNS propagates.
  4. Re-point email sends. Send transactional email from your app through Lumail's API or smtp.lumail.io:587, and test every template before switching production traffic.
  5. Rebuild email journeys as workflows. Recreate each email-only journey as a Lumail graph, test it with test subscribers, then connect Lumail's MCP tools to your assistant and hand it one real task.

Frequently asked questions

Is Lumail a Courier alternative?

For email, yes: newsletters, capture pages, workflows, and transactional email with delivery included. For multichannel notifications across SMS, push, chat, and an in-app inbox, no; that is Courier's job.

Is Lumail cheaper than Courier?

For email-only sending, usually. At Courier's Business rate, 20,000 sends is $100 before your email provider's delivery charges, while 20,000 emails on Lumail Premium is $20 with delivery included.

What is the main difference between Lumail and Courier?

Courier is notification infrastructure that sits in front of your providers and routes messages across channels. Lumail is an email platform that stores your audience, runs your campaigns and workflows, and delivers the email itself.

Can I migrate from Courier to Lumail?

Only the email slice. Export profiles and preferences, authenticate your domain in Lumail, point email sends at Lumail's API or SMTP, and rebuild email journeys as workflows; keep Courier for any other channel.

Which one should you choose?

Choose Courier if your product needs to reach users on many channels, with preferences, provider failover, and an in-app inbox, and you are happy to keep paying an email provider underneath it.

Choose Lumail if your messages are email: newsletters, lifecycle sequences, and transactional mail in one organization, delivered by Lumail, operated by your agents through 89 MCP tools, and billed at $20 for 40,000 emails a month.

You can start Lumail free with 3,000 emails per month and no credit card, review the pricing plans, or browse the full comparison hub.