Transactional email comparison

KumoMTA vs Loops Transactional Email

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

What the evidence answers

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

Common buyer questions answered
1 requirement
Documented for one
4 requirements
Not verified for either
2 requirements
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.

Dedicated IP
KumoMTA 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.
Loops Transactional Email The Loops API can return Loops’ dedicated sending IP addresses, which the SDK README says is intended for rare cases where you need to whitelist them.

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.
  • Loops Transactional Email The selected Loops Ruby SDK documentation says the package requires an API key.

Not verified yet

No reviewed evidence for either product on log retention and overage charges.

Documented for one product only, shown in the table below: KumoMTA: sending volume, webhooks and events and support; Loops Transactional Email: domains.

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.
RequirementKumoMTALoops Transactional Email
Pricing
Free plan · paid prices not verified

Price 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

The publisher describes an official Ruby SDK for Loops, an email platform for software companies.

Verified Nov 4, 2026 · Loops Transactional Email: loops-source

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.
The selected Loops Ruby SDK documentation says the package requires an API key.

Verified Nov 4, 2026 · Loops Transactional Email: loops-source

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

Not verified
DomainsNot verified
When an email message’s sender is set through the API, Loops takes only the sender username and appends the team’s sending domain automatically.

Supplier-maintained Node.js SDK README at release v7.4.0 captured on 9 November 2026; documentation of the API client, not a tested sending result or current plan entitlement. This parameter belongs to the email-message update endpoint; domain verification and the number of sending domains are not described in the README.

Verified Nov 10, 2026 · Loops Transactional Email: loops-js-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

Not verified
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

The Loops API can return Loops’ dedicated sending IP addresses, which the SDK README says is intended for rare cases where you need to whitelist them.

Supplier-maintained Node.js SDK README at release v7.4.0 captured on 9 November 2026; documentation of the API client, not a tested sending result or current plan entitlement. The README does not say that a customer can reserve a dedicated IP of its own, or on which plans.

Verified Nov 10, 2026 · Loops Transactional Email: loops-js-project

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.

Supplier-maintained Ruby SDK README at a pinned revision, captured 4 November 2026. Examples describe the selected client, not complete service coverage, current plan entitlements or a tested sending result.

2 requirements 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.

  • Log retention KumoMTA: not verified · Loops Transactional Email: not verified
  • Overage charges KumoMTA: not verified · Loops Transactional Email: 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 Loops Transactional Email's current prices, billing term and taxes on its official pricing page.
  • Ask KumoMTA about log retention, overage charges and domains; our sources do not establish them yet.
  • Ask Loops Transactional Email about log retention, overage charges and sending volume; our sources do not establish them yet.

Commissions never change costs, eligibility or rankings.