Evaluate PowerMTA.
Evaluate virtual MTAs, identities, queues, provider responses, and the team that will operate the deployment.
Review the deployment choices ↗PowerMTA Email Delivery Software
PowerMTA.
Operate with control.
Run email delivery infrastructure on your own servers or cloud. Organise sending streams with virtual MTAs and keep queues and provider responses in view.
PowerMTA / Sending streamsVIRTUAL MTA / TRANSACTIONALReceipts & account messagesSource IP · 192.0.2.10
VIRTUAL MTA / CAMPAIGNSNewsletters & promotionsSeparate stream and delivery settings
- Deployment
- Your servers or cloud
- Configuration
- Your supported operating settings
Operator view / ExampleTRANSACTIONAL / RECEIVING PROVIDER
0Queued example messages
250Provider accepted
Follow the response from the destination provider.
PowerMTA / Sending streamsVIRTUAL MTA / TRANSACTIONALReceipts & account messagesSource IP · 192.0.2.10
VIRTUAL MTA / CAMPAIGNSNewsletters & promotionsSeparate stream and delivery settings
- Deployment
- Your servers or cloud
- Configuration
- Your supported operating settings
Operator view / ExampleTRANSACTIONAL / RECEIVING PROVIDER
240Queued example messages
451Temporary deferral
The queue retains work after temporary provider deferrals.
PowerMTA / Sending streamsVIRTUAL MTA / TRANSACTIONALReceipts & account messagesSource IP · 192.0.2.10
VIRTUAL MTA / CAMPAIGNSNewsletters & promotionsSeparate stream and delivery settings
- Deployment
- Your servers or cloud
- Configuration
- Your supported operating settings
Operator view / ExampleTRANSACTIONAL / RECEIVING PROVIDER
240Queued example messages
451Temporary deferral
Inspect provider response and configured retry/rate policy before changing the sending operation.
Example content and data. Explore the workflow below; nothing is sent or changed in a live account.
Connecting customers.
In good company.Meet Bird’s customers ↗Customers across the Bird platform.
In good company.Meet Bird’s customers ↗Customers across the Bird platform.
FIND YOUR WAY IN
Control that comes with an operating model.
Compare Momentum.
Evaluate the message-processing, routing-policy, and integration requirements your organisation needs to own.
Compare Momentum ↗POWERMTA / TRY IT YOURSELFA route. A queue.
A route. A queue.
A reason to investigate.
Select a sending stream and provider response. See how a temporary deferral changes the queue and the next operational decision.
Receipts & account messages · 250 accepted · Continue monitoring queues and provider feedback. Provider acceptance does not guarantee inbox placement.
Read the operational next step ↗APPLICATIONReceipts & account messages
→VIRTUAL MTAtransactional
→OUTBOUND IP192.0.2.10
→PROVIDER250 accepted
QUEUE / ILLUSTRATIVE OPERATION
0Queued example messages
ContinueOperational next step
Continue monitoring queues and provider feedback. Provider acceptance does not guarantee inbox placement.
CONFIGURATION / CONCEPTUAL MAP
stream: transactional virtual MTA: transactional source IP: 192.0.2.10 provider response: 250 queued example messages: 0 queue policy: your configured settings
Illustrative mapping, not configuration directives. Confirm supported syntax and operating limits with your licensed PowerMTA version and runbook.
Review deployment considerations ↗Interactive illustration. Fictional workload and results. No live configuration changes.
EmmaA connection worth building on.
CUSTOMER EXPERIENCE
375M / month
Bird’s historical Emma story lists an average of 375 million messages a month before its home-grown sending system was replaced. As volume approached 400 million a month, Emma selected PowerMTA. The story does not measure post-migration throughput. The historical Emma story describes a team running its own sending infrastructure as email volume grew. That operating model includes responsibility for configuration, queues, and reputation.
Read Emma’s story ↗Historical pre-migration workload, not a measured PowerMTA result or current capacity promise.WHAT IT MEANS FOR YOUR CUSTOMERYour infrastructure.
Your infrastructure.
Each stream, understood.
Give your sending team a clear view of identities, queues, and delivery settings. Operate the system where your business needs the control.
Run where your team operates.
Place the sending layer on your own servers or cloud, with capacity and monitoring your team manages.
Give the traffic its own identity.
Use virtual MTAs to organise the IPs, queues, and configuration appropriate to each sending stream.
Bring a provider response into focus.
Inspect the queue and delivery context so your team can investigate the stream and choose the next operational step.
THE COMPLETE BIRD PLATFORM
Choose control where it serves your business.
Use PowerMTA for the sending infrastructure you operate, and discuss how monitoring and other Bird products can fit around it.
POWERMTA
Your application
↓Sending stream & queue
↓Provider response
01
PowerMTA This step
Your infrastructure routes each configured stream.
YOUR OPERATING AGREEMENTResponsibilities,
made explicit.
made explicit.
- Sending model
- Hosted or self-operated
- Operations
- Named owners
- Migration
- Phased by workload
02
Enterprise ↗
Scope the operating and support agreement.
f.
FieldnotesTo: Alex Lee ⌄
A little room to discover.
fieldnotes.A PERSONAL INTRODUCTIONA little room
to discover.
Hi Alex,
Good things start here.
Explore your next moment ↗
to discover.
Hi Alex,Good things start here.
Explore your next moment ↗
03
Email API ↗
Consider hosted sending for workloads with different ownership requirements.
PLAN WITH OUR TEAM
Bring the workload. Plan the infrastructure.
- 01Map the streams ↗
Bring traffic classes, average and peak volume, regions, provider mix, and operating requirements.
- 02Scope the supported deployment ↗
Confirm the supported release, sizing, licensing, implementation, and support with the MTA team.
- 03Plan the transition ↗
Agree migration stages, monitoring, incident ownership, and provider-response handling.
LEARN / BUILD / OPERATEGo further with
FIELD GUIDE
Go further with
PowerMTA.
FIELD GUIDEControl that comes with an operating model.
A practical path through setup, implementation, and the choices that matter.
Read the field guide →01↗02↗03↗04↗05↗06↗07↗
PowerMTA product reference
Deployment and product capabilities.
Compare operating models
Hosted service or infrastructure your team runs.
Explore Momentum
Consider a programmable processing pipeline.
Scope an MTA deployment
Bring streams, volume, regions, and support requirements.
PowerMTA configuration considerations
Historical operations guidance; validate every setting against your supported release and workload.
Sending streams and ownership
Virtual MTAs and the responsibilities your team operates.
Trace a provider deferral
Follow a stream into its queue and an operational decision.
POWERMTA / LICENSING & DEPLOYMENTControl where it matters.
Control where it matters.
Support for the operation.
Scope licensing, the supported release, deployment, and support with the MTA team. Your team operates PowerMTA; recipient providers decide acceptance and inbox placement.
Discuss PowerMTA ↗YOUR POWERMTA SETUPA licensed deployment
Size the software and support around your workload.
- Infrastructure
- Your team operates servers, monitoring, capacity, upgrades, and reputation.
- The sending model
- Plan virtual MTAs, IPs, queues, and traffic separation.
- Support
- Confirm the supported release, implementation scope, and Bird support agreement.
A FEW USEFUL ANSWERSPowerMTA,
PowerMTA,
answered.
Does Bird host the MTA for us?
Your team deploys and operates PowerMTA on infrastructure it controls, including monitoring, queues, and reputation. Bird helps scope licensing, supported releases, and support. Bird Email API and SMTP are hosted sending alternatives.
Can I start with an Email API key?
No. PowerMTA has a separate deployment, licensing, and support conversation. Bring your workload, regions, traffic classes, and operating responsibilities to the MTA team.
Is the displayed configuration ready to deploy?
No. It is a conceptual stream and queue map. Use documentation for your supported version and scope production configuration with the MTA team. Read operating considerations.
Does provider acceptance guarantee an inbox result?
No. The recipient provider controls acceptance and placement. Your operation should inspect temporary deferrals, bounces, queues, reputation, and its own monitoring before changing rates or retries.
How do I get started or speak to sales?
Plan your rollout with our sales team, including the products and requirements your business needs. Plan your setup or talk to sales.
Can I run PowerMTA and hosted sending together?
Yes. Evaluate moving selected traffic to hosted Bird sending while other streams remain self-operated. Scope configuration, monitoring and IP responsibility with the MTA team before changing a production route.
Does a virtual MTA isolate every reputation risk?
Virtual MTAs let your team separate traffic policies and IP use. Streams can still share sending domains and remain subject to recipient-provider policies. Review the whole sending setup when investigating reputation or delivery.