Pricing guide · verified September 2026
MailerSend Pricing Guide for 2026
MailerSend is the developer-shaped transactional API in this site's 15-tool agentic email comparison: email API plus SMTP relay, inbound routing, bulk sending, suppression management, verification tooling, and an MCP server, priced in email-volume bands. This guide uses only figures verified on the official MailerSend pricing page on September 17, 2026. The Free plan allows 500 emails per month with the email API, SMTP relay, inbound-routing support, and a drag-and-drop builder. The Hobby plan for personal projects and side hustles costs $7.00 per month for 5,000 emails per month, with extra usage billed at $1.50 per 1,000 emails and yearly billing discounting the same tier to $5.60 per month billed annually. Starter and Professional tiers scale to 50,000 emails per month each with broader domain, template, webhook, and retention limits; confirm their current dollar prices on the live page before budgeting.
This guide keeps MailerSend's numbers neutral so infrastructure buyers can judge the API economics themselves. Always confirm live figures at MailerSend pricing before spending.
The billing model in one paragraph
MailerSend sells monthly email-volume allowances in stepped plans with overage billing per thousand emails, which makes it a pure infrastructure meter: the bill tracks sends, not contacts, seats beyond the included count, or feature gates. Exceeding a plan's quota never interrupts sending; extra emails simply bill at the plan's per-thousand rate, a forgiving shape for spiky transactional workloads where a hard cap would be an outage. Quotas reset every 30 days, plan changes apply immediately on upgrade and at cycle end on downgrade, and cancellation keeps the subscription active through the remainder of the billing month with a final charge for extra emails outside the allowance.
Two structural details complete the model. First, a 14-day free trial of the Professional plan opens every evaluation with full features, 500 emails per month, 100 API requests per day, and 1 day of log retention, then drops to the Free plan automatically with no charge and no automatic upgrade. Second, even the Free plan requires entering organization details and credit card information to activate, explicitly as an anti-abuse measure rather than a charge, with taxes possibly applying per the terms of use. Nonprofits can request a 30 percent discount on paid plans with documentation, though it does not stack with yearly prices.
Plan tiers, verified
The Free plan for occasional testing costs $0 and includes 500 emails per month, the email API and SMTP relay, email-threads support, and the drag-and-drop builder, bounded by 1 template, 1 domain, 1 user seat plus 1 accountant role, 1 API token, 1 webhook, 100 daily API requests, and 1-day activity data retention. This is an integration-proving tier, not a production tier: verify DNS records, exercise the trial domain to skip initial authentication ceremony, confirm webhooks and suppression behavior, then move on. The single-domain and single-template ceilings bind almost immediately in any multi-brand or multi-template program.
Hobby at $7.00 per month covers 5,000 emails per month with extra usage at $1.50 per 1,000 emails, adding user roles and permissions plus bulk emailing on top of Free, bounded by 5 seats, 1 domain, 10 templates, 1 webhook, 1-day activity data retention, and 1,000 daily API requests. Yearly billing discounts Hobby to $5.60 per month billed annually. Hobby fits side projects and indie transactional workloads with a single sending domain: receipts, invites, resets, and notifications for one product at modest volume. The single-domain limit is the structural tell that Hobby is single-product shaped; a second brand or client domain forces the next step.
Starter and Professional each cover 50,000 emails per month with extra usage billed per thousand, and both were verified on the page with feature limits though their dollar prices render dynamically and must be read live. Starter allows 5 seats, 10 domains, 250 templates, 50 webhooks, 100,000 daily API requests, 7-day activity data retention, sender identities, removal of the MailerSend logo, and SMS API access for the USA and Canada. Professional allows unlimited users and domains and templates within documented fair-use terms, 500,000 daily API requests, 30-day activity data retention with 7-day API log retention, a dedicated account manager, and deliverability consultation. Professional is the agency and white-label reseller tier: sender identities, unlimited seats and domains, and consultation support match multi-client sending operations. Add-ons available to paid tiers include WhatsApp messaging, email verification credits, extra domain spaces at $4.00 each, phone numbers at $2.00 each for US and Canadian SMS, extended activity retention from $5.00, extra DMARC monitors at $2.00 each, and dedicated IPs for high-volume senders by arrangement with support.
Limits, overages, and the fine print
MailerSend's limits form a ladder across four axes, so forecasting means modeling all of them: email volume against the quota plus per-thousand overage rate, daily API request ceilings from 100 on trial and Free through 1,000 on Hobby, 100,000 on Starter, and 500,000 on Professional, domain and template counts against program breadth, and retention windows against audit needs. Activity data retention steps from 1 day on Free and Hobby through 7 days on Starter to 30 days on Professional, with the official page's own example noting a Starter-scale overage shape where extra blocks bill per thousand. Transactional programs with bursty verification, notification, and receipt traffic should stress-test the daily API request ceiling first, since it binds before the monthly email quota in chatty integrations.
The overage design deserves attention because it never blocks sending: quota exhaustion converts to per-thousand billing without disruption, which protects deliverability during spikes but removes the natural circuit breaker a hard cap provides. Agent-run programs should therefore implement their own send budgets and anomaly alerts rather than relying on the vendor to stop the meter, a discipline our discussion scenarios on cost attribution and kill switches explore in depth. Deliverability instrumentation also scales with tier: blocklist monitors step from 2 on Hobby through 64 on Starter to 256 on Professional, DMARC monitoring covers 10 domains on Professional with a limited Starter trial, and dedicated IPs remain an Enterprise arrangement for senders above roughly 100,000 emails per week.
What the free tier really proves
The Free 500-per-month allowance plus the 14-day Professional trial together prove the full integration loop: authenticate a domain or start on the trial domain, send through API and SMTP, receive inbound mail, exercise bulk endpoints, confirm webhook delivery, and validate suppression and analytics behavior. Five hundred emails cover several days of a small product's receipts and notifications, enough to measure latency, inspect per-message timelines, and confirm the SDK and OpenAPI surface fits the codebase. The trial domain shortcut is genuinely useful when evaluating multiple delivery tools in parallel, since per-vendor DNS ceremony would otherwise dominate the evaluation.
The honest boundary is everything production needs at scale: one domain, one template, one webhook, one API token, and one day of retention cannot carry a multi-template product with staging and production environments, let alone an agency portfolio. Support is limited on Free against email support on Hobby and live-chat-backed tiers above, and the 100-daily-request ceiling throttles any serious load test. Treat Free as the integration spike and Hobby as the first production rung for single-domain workloads, with Starter the natural home once a second domain, a template library, or week-long retention enters the picture.
Who MailerSend is for
MailerSend fits developers and agencies buying email infrastructure by the thousand: transactional receipts, onboarding notifications, verification flows, and bulk operational sends driven through API or SMTP with webhooks feeding delivery state back into the app. Inbound routing, sender identities, suppression management, verification tooling, and seven SDKs with OpenAPI coverage give platform teams the primitives they expect, while the MCP server offers a governed path for assistants to inspect email state. SMS and WhatsApp APIs on paid tiers let transactional programs add channels without a second vendor.
MailerSend is a weaker fit for teams whose core need is lifecycle marketing depth. Billing-triggered SaaS playbooks, visual journey orchestration, and revenue attribution arrive thinner here than in lifecycle-native platforms, and multi-channel orchestration belongs to journey builders like Customer.io through our Customer.io pricing guide. SaaS teams wanting lifecycle plus transactional under one roof should treat MailerSend as the infrastructure alternative for API-pure workloads.
Agent and MCP fit
MailerSend lists an MCP server among its integration features, which gives it a stronger agent-operation story than API-only infrastructure peers: assistants can inspect domains, templates, activity, and delivery state through a governed server rather than raw key sprawl. Combined with documented APIs, SDKs, webhooks, and scoped user roles with custom permissions, the access-control primitives support a real supervision story: least-privilege tokens per environment, IP allowlisting, two-factor enforcement, and per-service separation between staging and production credentials. Agents are themselves API clients, so a predictable send endpoint with structured delivery events is far easier to govern than a UI-only tool.
The governance burden that remains is retention and budget scope. One-day activity retention on Free and Hobby means agent audit trails must be exported to team-owned storage rather than reconstructed from the vendor console, and never-blocking overages mean agents need explicit send budgets with anomaly tripwires. Run MailerSend agents inside the supervised sending pipeline from our 15-tool comparison: agents draft and dispatch within quotas, humans approve consequential bulk sends, suppression and kill switches stay armed, and delivery events flow back as evidence.
Where MailerSend fits
MailerSend wins infrastructure purity. Its Free 500 monthly, Hobby $7 for 5,000 with $1.50-per-thousand overages, inbound routing, verification tooling, and MCP-backed API access suit platform teams that want a focused pipe.
Many stacks pair a focused transactional pipe with a lifecycle platform, accepting two bills for best-of-breed fit. Teams whose email is code-owned infrastructure with strict per-environment key discipline should price MailerSend's ladder against Resend in our Resend guide and Postmark in our Postmark guide.
Verdict and checklist
Choose MailerSend when email is infrastructure your engineers own: prove integration on the free allowance with the trial domain, run single-domain production on the Hobby tier with overage math modeled, step to Starter or Professional at 50,000-email scale as domains, templates, webhooks, and retention demand, and export audit data on a schedule matching the tier's retention window. Confirm current tier prices and overage rate at MailerSend pricing, then return to the pricing index for the full verified set.