Bird vs Mailgun
Bird vs Mailgun para e-mail transacional
Deliver transactional emails and marketing broadcasts on sending infrastructure Bird owns and operates, with 30-day message retention, hosted MCP agent tooling, and email, SMS, WhatsApp, and voice in one API.
Arraste um ícone sobre os pontos. Use as teclas de seta para mover um ícone em foco. Pressione Escape para cancelar o arraste.
Trusted by engineering and product teams
shipping at global scale.
Em números
Rede Bird
Cerca de 40% do e-mail comercialCorpos de mensagens armazenados
Até 30 dias, com armazenamento ativadoQuem controla a infraestrutura de envio?
Mailgun: IPs, roteamento e validação
Mailgun provides dedicated IP pools, automated IP warm-up, and Automatic Sender Security to rotate DKIM keys via delegated CNAME records.
Mailgun’s bulk list validation cleans uploaded address lists, while Inbound Routes match incoming mail against filter expressions and forward or store messages. Mailgun fits workflows built around list uploads or regex-based inbound forwarding.
Mailgun Optimize adds inbox-placement testing and blocklist monitoring, with managed Deliverability Services available for enterprise senders.
Bird: infraestrutura e reputação
Bird runs its own global sending infrastructure and develops the underlying MTA software, including PowerMTA for on-premises sending. Bird’s SparkPost network delivers roughly 40% of the world’s commercial email.
Manage shared IPs, dedicated IPs, and IP pools with automated warm-up and shared-pool overflow. Bird’s Momentum MTA adapts delivery rates per mailbox provider in real time and automatically suppresses hard bounces and spam complaints to protect your sender reputation.
Check folder placement with Inbox Insights seed tests, inspect delivery metrics in Email analytics, and benchmark rival senders in Competitive Insights, backed by Bird’s deliverability specialists.
Como Bird e Mailgun se comparam?
Mailgun’s bulk list validation and inbound routing rules suit list-cleaning and forwarding workflows. Bird pairs its global SparkPost sending network with 30-day message retention, programmable agent mailboxes, hosted MCP tooling, and multi-channel messaging in one API.
| Recurso | Bird | Mailgun | Quem vence? |
|---|---|---|---|
| Envio transacional via API | Bird’s TypeScript SDK accepts JSON payloads, throws typed errors by default, and offers a result-tuple mode for explicit error branching. | Mailgun’s JavaScript SDK and Messages API submit multipart form-data payloads scoped to a sending domain. | |
| Relay SMTP | Bird SMTP supports implicit TLS on port 465 and STARTTLS on ports 587 and 2525, authenticated with your standard workspace API key. | Mailgun SMTP supports implicit TLS on port 465 and STARTTLS on ports 25, 587, and 2525 using per-domain SMTP credentials. | |
| Validação de endereço de e-mail | Bird email lookup verifies single addresses in real time, returning a deliverability verdict, confidence score, address risk flags, and typo suggestions. | Mailgun Validate supports both real-time single-address checks and bulk validation of uploaded address lists. | |
| Idempotência no envio | Bird retains completed send responses for 3 hours so retried requests with the same key never duplicate an email. | Mailgun’s inbox-placement test key deduplicates seed-list placement tests rather than deduplicating customer email sends. | |
| Retenção de mensagens armazenadas | Bird stores rendered message bodies for up to 30 days when content storage is enabled. | Mailgun’s published plans include 1 day of message body storage on Foundation and up to 7 days on Scale, tracked separately from event log retention. | |
| Preços publicados | Os planos e tarifas de e-mail da Bird são exibidos em tempo real na tabela abaixo. | Compare o plano selecionado com as tarifas publicadas do Mailgun, incluindo seu período de cobrança e recursos. | |
| IPs dedicados e pools | Bird dedicated IPs and pools automate IP warm-up and route excess volume through the shared pool. | Mailgun IP pools group dedicated IPs by stream, while automated warm-up caps stage volume and overflows to shared or sibling IPs. | |
| Histórico de entregabilidade | Bird acquired SparkPost in 2021, and its sending network delivers roughly 40% of the world’s commercial email. | Mailgun’s sending infrastructure runs across US and EU regions selectable from a single account. | |
| SPF, DKIM, DMARC e BIMI | Bird verifies DKIM, custom return-path, and DMARC, with BIMI configured through DNS and your brand logo. | Mailgun Automatic Sender Security rotates DKIM keys automatically, and its sending plans support SPF, DKIM, DMARC, and BIMI. | |
| Webhooks de eventos e assinatura | Bird signs webhook deliveries using Standard Webhooks so your handler can verify authenticity with any compliant library. | Mailgun webhook verification signs a timestamp and token using HMAC-SHA256 with your Webhook Signing Key. | |
| Canais além do e-mail | Bird’s API covers email, SMS, WhatsApp, voice, Verify, and Realtime in one workspace. | Mailgun provides an email API, while parent company Sinch offers separate SMS and voice APIs. | |
| Fornecedor e compras | Revise os termos legais e políticas publicados do Bird em relação ao seu contrato existente e requisitos de compras. | Revise os termos publicados do Mailgun em relação ao seu contrato existente e requisitos de compras. | |
| Caixas de correio | Bird’s agent mailboxes provide programmable inboxes, conversation threads, quote-stripped replies, and sender rules. | Mailgun Routes match incoming mail with recipient and header regex filters and trigger forward, store, or stop actions. | |
| Ferramentas para agentes | Bird’s hosted MCP server exposes 354 tools, and the Bird CLI manages domains, templates, webhooks, and sends with structured JSON output and semantic exit codes. | Mailgun’s open-source MCP server runs locally to send mail, inspect stored messages, and manage domains, routes, templates, and deliverability without a hosted endpoint. |
Como você envia um e-mail HTML?
Both SDKs send a transactional HTML email in a single call. Mailgun’s client passes the sending domain alongside a multipart message payload, while Bird’s SDK sends JSON and supports both thrown typed errors and result-object branching.
Mailgun
import Mailgun from "mailgun.js";
import formData from "form-data";
const mg = new Mailgun(formData).client({
username: "api",
key: process.env.MAILGUN_API_KEY!,
});
await mg.messages.create("yourdomain.com", {
from: "onboarding@yourdomain.com",
to: ["customer@example.com"],
subject: "Your March invoice",
html: "<p>Attached.</p>",
});
Bird
import { BirdClient } from "@messagebird/sdk";
const bird = new BirdClient({ apiKey: process.env.BIRD_API_KEY! });
const { data, error } = await bird.email
.send({
from: { email: "onboarding@yourdomain.com", name: "Acme" },
to: ["customer@example.com"],
subject: "Your March invoice",
html: "<p>Attached.</p>",
})
.safe();
if (error) console.error(error.message);
else console.log(data.id);
O que muda em torno da chamada de envio?
Como as Mailgun Routes mapeiam para caixas de correio do Bird?
Como devo evitar envios duplicados durante a migração?
Planos de e-mail publicados
Os planos pagos da Bird adicionam um depósito mensal a um saldo compartilhado. Os envios transacionais usam a tarifa do plano. A comparação abaixo considera que o saldo é usado apenas para email; outros usos e complementos têm custo adicional.
Veredito de preços: Bird. Em cada franquia concorrente, o valor mensal estimado exigido pela Bird é o maior entre o depósito do plano pago e o uso transacional pela tarifa publicada. O plano Free usa a franquia incluída, quando disponível. Os depósitos são saldo utilizável, não uma taxa extra. Apenas volumes correspondentes e moedas com tarifas completas influenciam o resultado.
| E-mails por mês | Plano da Bird e valor mensal exigido | Mailgun |
|---|---|---|
| 50,000 | Email Startup: $20 (USD) | |
| 100,000 | Email Startup: $40 (USD) | |
| 250,000 | Email Startup: $100 (USD) | |
| 500,000 | Email Startup: $200 (USD) | |
| 1,000,000 | Email Startup: $400 (USD) | |
| 2,500,000 | Email Startup: $1,000 (USD) |
Mailgun: Planos publicados
Como você deve comparar custos de e-mail?
O que as linhas de preço do Bird e do Mailgun incluem?
Custo de migração
O que envolve uma migração do Mailgun?
Start by mapping Mailgun’s multipart form parameters and recipient variables to Bird’s JSON send payload and batch entries. Verify your sending domains in Bird and export each Mailgun domain’s bounces, spam complaints, and unsubscribes into Bird’s workspace suppression list using our Mailgun migration guide.
Next, update Mailgun’s HMAC webhook verification to use Standard Webhooks, and map Mailgun’s temporary vs. permanent failure events to Bird’s deferred and bounced webhook events. Test your handlers in Bird’s mail sandbox before switching live traffic, and allow time for automated warm-up on new dedicated IPs.
Coloque em prática.
Continue com a documentação, guias e exemplos sobre este tópico.
Próximos passos
Comece pelo guia de migração para mapear a integração e testar a transição.
Fale com nosso time de e-mail
Veja como Bird se encaixa no seu fluxo de trabalho com Mailgun.
Teste seu remetente, templates e eventos de entrega antes de migrar o tráfego do Mailgun. Para uma migração maior, planeje a transição com um especialista em e-mail.
Crie sua conta e teste sua integração. Sua solicitação de migração incluirá o provedor que você está comparando.