E-mail transacional: comparação

KumoMTA vs Plunk

Preços, recursos documentados e limites de fontes oficiais datadas, lado a lado. O que é desconhecido continua desconhecido; unidades de cobrança diferentes não permitem comparar custos diretamente.

  • KumoMTA

    Última verificação das fontes: 9 de nov. de 2026

    Para quem é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.

  • Plunk

    Última verificação das fontes: 10 de nov. de 2026

    Para quem éPlunk describes a platform for transactional email, marketing campaigns and workflow automation.

O que as fontes respondem

Uma leitura da documentação oficial revisada de KumoMTA e Plunk. Não é um teste prático, um ranking nem a recomendação de um produto.

Perguntas de compra respondidas para os dois
3 requisitos
Documentado para um só
3 requisitos
Não verificado para nenhum
1 requisito
Preços
Ainda não comparáveis

Preço

  • KumoMTA

    Plano gratuito · preços pagos não verificados ·

    • Self-hosted: sem cobrança de assinatura ·
  • Plunk

    Preço documentado: 1,00 por 1,000 emails (excedente) (moeda não informada) · Plano: Pay-as-you-go · sem fidelidade mínima ·

    • Self-hosted: sem cobrança de assinatura ·
    • Free tier: sem cobrança de assinatura ·
    • Pay-as-you-go: 1,00 (moeda não informada) excedente por 1,000 emails, sem taxa básica mensal · sem fidelidade mínima ·

Ainda não há uma comparação de preços completa em condições equivalentes; os próximos passos dizem o que falta.

Perguntas de compra respondidas para os dois

Mesmo quando os rótulos coincidem, verifique em cada fonte as diferenças de planos, unidades e escopo.

Volume de envios
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.
Plunk Each recipient of a transactional send or campaign, each workflow send step and each received inbound email uses one credit toward monthly usage; an email with attachments uses two credits regardless of attachment size.
Webhooks e eventos
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.
Plunk Plunk sends real-time HTTP requests to your application through a workflow Webhook step, triggered by events such as email bounces, spam complaints or custom events.
Suporte
KumoMTA Community support, plus paid Professional Services and Commercial Support from the KumoMTA team.
Plunk The README lists the public Plunk documentation and a Discord server; no paid support plan is named in it.

Limites a verificar

  • 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.
  • Plunk Plunk documents a self-hosted deployment option.
  • Plunk Self-hosting needs Docker and Docker Compose, an AWS SES account for sending and a domain name with subdomains for each service.

Ainda não verificado

Não há fontes revisadas para nenhum dos produtos sobre: cobranças por excedente.

Documentado para um só produto, na tabela abaixo: KumoMTA: IP dedicado; Plunk: domínios e retenção de logs.

“Não verificado” significa que nossas fontes revisadas não estabelecem isso. Não significa que um produto não tenha o recurso nem que seja gratuito.

Evidências lado a lado

Valores documentados com fontes e datas de verificação; requisitos que as fontes não estabelecem continuam sinalizados.

  • Documentado como compatível
  • Documentado como não compatível
  • Não verificado As fontes não estabelecem isso
  • Não se aplica
Escopo e limites documentados; dimensões não verificadas continuam desconhecidas.
RequisitoKumoMTAPlunk
Preços
Plano gratuito · preços pagos não verificados

Preço documentado: 1,00 por 1,000 emails (excedente) (moeda não informada) · Plano: Pay-as-you-go · sem fidelidade mínima

Ver as 3 ofertas

Para quem
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.

Verificado em 6 de nov. de 2026 · KumoMTA: kumomta-project

Plunk describes a platform for transactional email, marketing campaigns and workflow automation.

Verificado em 3 de nov. de 2026 · Plunk: plunk-readme

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

Verificado em 6 de nov. de 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.
Plunk documents a self-hosted deployment option.

Verificado em 3 de nov. de 2026 · Plunk: plunk-readme

  • Self-hosted Self-hosting needs Docker and Docker Compose, an AWS SES account for sending and a domain name with subdomains for each service.
Volume de envios
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.

Verificado em 9 de nov. de 2026 · KumoMTA: kumomta-docs-hardware-project

Each recipient of a transactional send or campaign, each workflow send step and each received inbound email uses one credit toward monthly usage; an email with attachments uses two credits regardless of attachment size.

Plunk billing documentation (docs source at release v0.18.0), captured 9 November 2026. Applies to the hosted version; a per-category monthly cap can be set for transactional, campaign, workflow and inbound emails. Supplier statement, not a hands-on test.

Verificado em 10 de nov. de 2026 · Plunk: plunk-docs-billing-project

DomíniosNão verificado
Custom sending domains can be verified, with DKIM and SPF support.

Dated publisher project README at release v0.18.0, captured on 9 November 2026; supplier feature list, not a tested verification.

Verificado em 10 de nov. de 2026 · Plunk: plunk-project

Retenção de logsNão verificado
Rendered email HTML is kept for 90 days and API request logs for 30 days; email metadata and metrics are kept indefinitely.

Plunk data-retention documentation (docs source at release v0.18.0), captured 9 November 2026. The 90-day and 30-day windows are compiled in and run as scheduled jobs on the worker process in self-hosted deployments. No retention test was performed.

Verificado em 10 de nov. de 2026 · Plunk: plunk-docs-retention-project

Webhooks e 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.

Verificado em 9 de nov. de 2026 · KumoMTA: kumomta-docs-webhooks-project

Plunk sends real-time HTTP requests to your application through a workflow Webhook step, triggered by events such as email bounces, spam complaints or custom events.

Plunk webhooks documentation (docs source at release v0.18.0), captured 9 November 2026. Internal events listed there include email sent, delivery, open, click, bounce, complaint and received. No webhook delivery test was performed.

Verificado em 10 de nov. de 2026 · Plunk: plunk-docs-webhooks-project

IP dedicado
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.

Verificado em 9 de nov. de 2026 · KumoMTA: kumomta-docs-sendingips-project

Não verificado
Suporte
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.

Verificado em 9 de nov. de 2026 · KumoMTA: kumomta-docs-help-project

The README lists the public Plunk documentation and a Discord server; no paid support plan is named in it.

Dated publisher project README at release v0.18.0, captured on 9 November 2026; supplier statement, no support request was made.

Verificado em 10 de nov. de 2026 · Plunk: plunk-project

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.

Publisher project README captured 3 November 2026. Self-hosting and email delivery entail separate infrastructure, setup and service costs. No email, account, deployment, integration or deliverability test was performed.

1 requisito sem evidência revisada aqui

Não verificado significa que as fontes revisadas não estabelecem isso; não significa que o produto não tenha o recurso nem que ele seja gratuito.

  • Cobranças por excedente KumoMTA: não verificado · Plunk: não verificado

Próximos passos

  • Confirme os preços dos planos pagos, o prazo de cobrança e os impostos de KumoMTA na página oficial de preços; aqui só o plano gratuito está verificado.
  • Confirme no pagamento a moeda do preço exibido de Plunk.
  • Pergunte a KumoMTA sobre estes pontos: cobranças por excedente, domínios e retenção de logs. Nossas fontes ainda não os confirmam.
  • Pergunte a Plunk sobre estes pontos: cobranças por excedente e IP dedicado. Nossas fontes ainda não os confirmam.

Comissões nunca mudam custos, elegibilidade ou ordem.