Transactional email comparison

KumoMTA vs Larasend

Prices, documented capabilities and limits from dated official sources, side by side. Unknowns remain unknown; different billing units do not establish a cost winner.

  • KumoMTA

    Latest evidence check Nov 9, 2026

    Who it is forKumoMTA is an open-source message transfer agent designed for high-performance outbound email, comparable to commercial enterprise MTAs such as Momentum, PowerMTA and Halon.

  • Larasend

    Latest evidence check Nov 9, 2026

    Who it is forLarasend is a self-hosted transactional email platform for Laravel teams with an HTTP API, dashboard, activity log, API keys, delivery events, suppressions and a Laravel mail transport, sending through your own Amazon SES account.

What the evidence answers

A reading of reviewed official documentation for KumoMTA and Larasend. It is not a hands-on test, a ranking or a recommendation of one product.

Common buyer questions answered
2 requirements
Documented for one
4 requirements
Not verified for either
1 requirement
Prices
Not like-for-like yet

Price

A complete like-for-like price comparison is not established; the next steps say what is missing.

Common buyer questions answered

Even when labels match, check each source for differences in plans, units and scope.

Sending volume
KumoMTA Throughput depends on the hardware you deploy: for many millions of messages per hour the publisher advises the largest server you can, on bare metal or public or private cloud, with or without Kubernetes.
Larasend Larasend syncs your Amazon SES sending quota but accepts API sends even when that sync is stale or temporarily unavailable; SES remains the final authority for provider-side send rejection.
Webhooks and events
KumoMTA Message events can be sent as webhooks to a user-defined HTTP endpoint, with queuing built in for durability if the receiving HTTP service has an error.
Larasend Amazon SES delivery, bounce, complaint, open and click events come back to Larasend through an SES webhook; Larasend then updates its activity dashboard, metrics, suppressions and webhook deliveries.

Limits to check

  • KumoMTA KumoMTA is intended for experienced email operations professionals who are used to high-performance sending environments and familiar with DevOps practices.
  • KumoMTA At least 4 CPU cores, 4 GB of RAM and 20 GB of storage. For high-performance systems the guide advises storage with the fastest IOPS and lowest latency, where local disk is much better than NAS or SAN; the same guidance applies to the Docker image.
  • Larasend Larasend requires an Amazon SES account with a verified sending domain, PostgreSQL 17 or newer, Docker and Docker Compose for production-style installs, and Redis 7 or newer with the bundled Compose stack.

Not verified yet

No reviewed evidence for either product on overage charges.

Documented for one product only, shown in the table below: KumoMTA: dedicated IP and support; Larasend: domains and log retention.

Not verified means our reviewed sources do not establish it. It does not mean a product lacks the capability or that it costs nothing.

Side-by-side evidence

Documented values with their sources and check dates; requirements the sources do not establish stay marked.

  • Documented as supported
  • Documented as unsupported
  • Not verified Sources do not establish it
  • Not applicable
Documented scope and limits; unverified dimensions remain unknown.
RequirementKumoMTALarasend
Pricing
Free plan · paid prices not verified

Free plan · paid prices not verified

Who it is for
KumoMTA is an open-source message transfer agent designed for high-performance outbound email, comparable to commercial enterprise MTAs such as Momentum, PowerMTA and Halon.

Verified Nov 6, 2026 · KumoMTA: kumomta-project

Larasend is a self-hosted transactional email platform for Laravel teams with an HTTP API, dashboard, activity log, API keys, delivery events, suppressions and a Laravel mail transport, sending through your own Amazon SES account.

Verified Nov 6, 2026 · Larasend: larasend-project

Coverage limits
KumoMTA is intended for experienced email operations professionals who are used to high-performance sending environments and familiar with DevOps practices.

Verified Nov 6, 2026 · KumoMTA: kumomta-project

  • Self-hosted At least 4 CPU cores, 4 GB of RAM and 20 GB of storage. For high-performance systems the guide advises storage with the fastest IOPS and lowest latency, where local disk is much better than NAS or SAN; the same guidance applies to the Docker image.
Larasend requires an Amazon SES account with a verified sending domain, PostgreSQL 17 or newer, Docker and Docker Compose for production-style installs, and Redis 7 or newer with the bundled Compose stack.

Verified Nov 6, 2026 · Larasend: larasend-project

Sending volume
Throughput depends on the hardware you deploy: for many millions of messages per hour the publisher advises the largest server you can, on bare metal or public or private cloud, with or without Kubernetes.

Publisher hardware guide (docs/userguide/installation/hardware.md) at release 2026.09.29-b90d8bc1 (commit b90d8bc) captured 8 November 2026; supplier sizing guidance, not a measured throughput or performance test.

Verified Nov 9, 2026 · KumoMTA: kumomta-docs-hardware-project

Larasend syncs your Amazon SES sending quota but accepts API sends even when that sync is stale or temporarily unavailable; SES remains the final authority for provider-side send rejection.

Publisher project README at release v0.1.0 (commit 0995381) captured 8 November 2026. Sending volume and charges are those of the buyer's own Amazon SES account, which were not captured. Supplier description, not a test.

Verified Nov 9, 2026 · Larasend: larasend-project

DomainsNot verified
Sending domains are your own SES-verified domains: you add each in Larasend and publish the DKIM records it shows in Route 53 or another DNS provider.

Publisher project README at release v0.1.0 (commit 0995381) captured 8 November 2026; recommended setup, not a tested installation. The README states no limit on the number of domains.

Verified Nov 9, 2026 · Larasend: larasend-project

Log retentionNot verified
Because you self-host the control plane, email logs and metadata stay in infrastructure you control; the README states no retention window.

Publisher project README at release v0.1.0 (commit 0995381) captured 8 November 2026; supplier description. Log storage, backups and any pruning were not tested.

Verified Nov 9, 2026 · Larasend: larasend-project

Webhooks and events
Message events can be sent as webhooks to a user-defined HTTP endpoint, with queuing built in for durability if the receiving HTTP service has an error.

Publisher documentation (docs/userguide/operation/webhooks.md) at release 2026.09.29-b90d8bc1 (commit b90d8bc) captured 8 November 2026. Webhooks are set up in the Lua policy script, with the log_hooks helper recommended. Supplier documentation, not a tested integration.

Verified Nov 9, 2026 · KumoMTA: kumomta-docs-webhooks-project

Amazon SES delivery, bounce, complaint, open and click events come back to Larasend through an SES webhook; Larasend then updates its activity dashboard, metrics, suppressions and webhook deliveries.

Publisher project README at release v0.1.0 (commit 0995381) captured 8 November 2026; supplier description, not a tested integration. Event publishing needs an SES configuration set; the README does not describe outgoing webhook payloads, retries or endpoint limits.

Verified Nov 9, 2026 · Larasend: larasend-project

Dedicated IP
By default mail leaves through the host's default interface; IPs can be grouped into pools, and a queue tied to a pool spreads its sends across the pool's IPs by weighted round robin. Separate IPs per mail stream are recommended to isolate reputation.

Publisher documentation (docs/userguide/configuration/sendingips.md) at release 2026.09.29-b90d8bc1 (commit b90d8bc) captured 8 November 2026. The sending addresses are configured on the operator's own hosts. Supplier guidance, not a deliverability test.

Verified Nov 9, 2026 · KumoMTA: kumomta-docs-sendingips-project

Not verified
Support
Community support, plus paid Professional Services and Commercial Support from the KumoMTA team.

Publisher FAQ (docs/faq/how_can_i_get_help_with_kumomta.md) at release 2026.09.29-b90d8bc1 (commit b90d8bc) captured 8 November 2026. Paid support and services are arranged by contacting the KumoMTA team; the FAQ gives no prices or response times. Community support is described on the user guide's How To Get Help page.

Verified Nov 9, 2026 · KumoMTA: kumomta-docs-help-project

Not verified
Coverage note

Dated publisher project README captured on 5 November 2026; supplier description, not a deployment or independent test. Infrastructure, accounts, third-party services and managed offerings have separate costs and terms.

Dated publisher project README captured on 5 November 2026; supplier description, not a deployment or independent test. Infrastructure, accounts, third-party services and managed offerings have separate costs and terms.

1 requirement without reviewed evidence here

Not verified means the reviewed sources do not establish it; it does not mean a product lacks it or that it costs nothing.

  • Overage charges KumoMTA: not verified · Larasend: not verified

Next steps

  • Confirm KumoMTA's paid plan prices, billing term and taxes on its official pricing page; only its free plan is verified here.
  • Confirm Larasend's paid plan prices, billing term and taxes on its official pricing page; only its free plan is verified here.
  • Ask KumoMTA about overage charges, domains and log retention; our sources do not establish them yet.
  • Ask Larasend about overage charges, dedicated IP and support; our sources do not establish them yet.

Commissions never change costs, eligibility or rankings.