Email transaccional: comparación
KumoMTA vs Loops Transactional Email
Precios, funciones documentadas y límites de fuentes oficiales fechadas, lado a lado. Lo desconocido sigue siendo desconocido; con unidades de facturación distintas no se pueden comparar los costes directamente.
Última comprobación de fuentes: 9 nov 2026
Para quién esKumoMTA is an open-source message transfer agent designed for high-performance outbound email, comparable to commercial enterprise MTAs such as Momentum, PowerMTA and Halon.
Última comprobación de fuentes: 10 nov 2026
Para quién esThe publisher describes an official Ruby SDK for Loops, an email platform for software companies.
Qué responden las fuentes
Una lectura de la documentación oficial revisada de KumoMTA y Loops Transactional Email. No es una prueba práctica, una clasificación ni la recomendación de un producto.
- Preguntas de compra respondidas para ambos
- 1 requisito
- Documentado solo para uno
- 4 requisitos
- Sin verificar para ninguno
- 2 requisitos
- Precios
- Aún no comparables
Precio
KumoMTA
Plan gratuito · precios de pago sin verificar ·
- Self-hosted: sin cuota de suscripción ·
Loops Transactional Email
Precio no verificado
Aún no hay una comparación de precios completa en igualdad de condiciones; los próximos pasos indican qué falta.
Preguntas de compra respondidas para ambos
Aunque las etiquetas coincidan, revisa en cada fuente las diferencias de planes, unidades y alcance.
- IP dedicada
- 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.
Límites que revisar
- 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.
Aún sin verificar
No hay fuentes revisadas para ninguno de los productos sobre: retención de registros y cargos por exceso.
Documentado solo para un producto, en la tabla de abajo: KumoMTA: volumen de envíos, webhooks y eventos y soporte; Loops Transactional Email: dominios.
«Sin verificar» significa que nuestras fuentes revisadas no lo establecen. No significa que a un producto le falte la función ni que no cueste nada.
Evidencia lado a lado
Valores documentados con sus fuentes y fechas de comprobación; los requisitos que las fuentes no establecen quedan marcados.
- Documentado como compatible
- Documentado como no compatible
- Sin verificar Las fuentes no lo establecen
- No aplica
| Requisito | KumoMTA | Loops Transactional Email |
|---|---|---|
| Precios | Plan gratuito · precios de pago sin verificar | Precio no verificado |
| Para quién | 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. Comprobado el 6 nov 2026 · KumoMTA: kumomta-project | The publisher describes an official Ruby SDK for Loops, an email platform for software companies. Comprobado el 4 nov 2026 · Loops Transactional Email: loops-source |
| Límites de cobertura | KumoMTA is intended for experienced email operations professionals who are used to high-performance sending environments and familiar with DevOps practices. Comprobado el 6 nov 2026 · KumoMTA: kumomta-project
| The selected Loops Ruby SDK documentation says the package requires an API key. Comprobado el 4 nov 2026 · Loops Transactional Email: loops-source |
| Volumen de envíos | 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. Comprobado el 9 nov 2026 · KumoMTA: kumomta-docs-hardware-project | Sin verificar |
| Dominios | Sin verificar | 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. Comprobado el 10 nov 2026 · Loops Transactional Email: loops-js-project |
| Webhooks y eventos | 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. Comprobado el 9 nov 2026 · KumoMTA: kumomta-docs-webhooks-project | Sin verificar |
| IP dedicada | 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. Comprobado el 9 nov 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. Comprobado el 10 nov 2026 · Loops Transactional Email: loops-js-project |
| Soporte | 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. Comprobado el 9 nov 2026 · KumoMTA: kumomta-docs-help-project | Sin verificar |
| Nota de cobertura | 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 requisitos sin evidencia revisada aquí
Sin verificar significa que las fuentes revisadas no lo establecen; no significa que el producto no lo tenga ni que no cueste nada.
- Retención de registros KumoMTA: sin verificar · Loops Transactional Email: sin verificar
- Cargos por exceso KumoMTA: sin verificar · Loops Transactional Email: sin verificar
Próximos pasos
- Confirma los precios de los planes de pago, el plazo de facturación y los impuestos de KumoMTA en su página oficial de precios; aquí solo está verificado su plan gratuito.
- Confirma los precios actuales, el plazo de facturación y los impuestos de Loops Transactional Email en su página oficial de precios.
- Pregunta a KumoMTA por estos puntos: retención de registros, cargos por exceso y dominios. Nuestras fuentes aún no los confirman.
- Pregunta a Loops Transactional Email por estos puntos: retención de registros, cargos por exceso y volumen de envíos. Nuestras fuentes aún no los confirman.
- KumoMTAIr a KumoMTAPerfil y planes
- Loops Transactional EmailIr a Loops Transactional EmailPerfil y planes
Las comisiones nunca cambian los costes, la idoneidad ni el orden.