[Email](/email) Enterprise # Enterprise email. Built around your operation. Choose the sending model, migration plan, and operating responsibilities your business needs. Bring hosted email and specialist infrastructure into one conversation. [Talk to sales ↗](/demo?product=enterprise) [Try hosted email ↗](/dashboard/signup?returnTo=%2Fdashboard%2Fw%2Femail%2Fonboarding) REQUIREMENTS / YOUR OPERATING MODEL ## Your requirements. A deliberate architecture. Choose the operating model that fits your team. Compare hosted delivery and infrastructure you manage, then build a brief around your workload and support needs. Who operates the sending layer? Bird-operated Email API & SMTP Your team · PowerMTA Your team · Momentum Peak monthly messages · planning assumption Operating capacity No dedicated MTA team Named MTA team Regions and data handling Traffic and peak volume Migration and IP reputation Access and security Support and recovery Prepare requirements brief ↗ Enter a whole-number planning volume from 1 to 1,000,000,000. No brief was prepared. YOUR APPLICATION Business logic Recipients, content, permission and outcomes BIRD OPERATES YOUR TEAM OPERATES RECEIVING PROVIDER Delivery response Acceptance is separate from inbox placement Prepare the current selection to create a discussion brief. Changing a requirement clears the previous brief. A self-operated model needs a named operations owner. Add that owner or evaluate hosted sending before deployment. Unresolved: region, capacity, data handling, security evidence, SLA/support, current release, license/usage terms and migration rollback. This worksheet submits nothing. [Prepare a migration plan ↗](/docs/guides/email/migrate) **Interactive illustration with fictional records. No account is queried, no DNS is checked and no message is sent. Changing inputs clears any previous observation.** Companies that trust Bird across their communications. - [Airwallex](/customers/airwallex) - Uber - [Zillow](/customers/zillow) - [Glovo](/customers/glovo) - PayPal - Adobe [Read Bird customer stories](/customers) CHOOSE / BUILD / OPERATE ## Plan the workload before the deployment. ### Hosted Email API and SMTP. Keep application logic, recipient policy and outcome handling in your application. Bird operates the hosted sending service; your team still owns its integration and traffic decisions. [Explore hosted Email ↗](/email-api) ### PowerMTA or Momentum. A self-operated model needs deployment, capacity, reputation management and recovery ownership. Evaluate the current release, license and support scope against a representative workload. [Evaluate PowerMTA ↗](/powermta) ## Who will operate your email infrastructure? Choose the [Bird Email API](/email-api) or SMTP relay when you want hosted sending. Choose PowerMTA or Momentum when your team needs to operate the MTA itself. Inbox Insights and Competitive Insights address monitoring and market intelligence. Each path has its own setup and commercial requirements. ## Prepare your enterprise rollout. Give engineering, security and procurement the information they need to evaluate your email service. 01 ### Security and data processing. Review security information and request available reports in the [Bird Trust Center](https://trust.bird.com). Your procurement team can review the [Data Processing Agreement](/legal/dpa) and [subprocessor list](/legal/subprocessors) before agreeing the scope of service. 02 ### Availability and support. Check current operations on the [service status page](/status). Discuss required availability, support coverage, response targets and escalation with our team, and confirm the commitments that apply to your service in your agreement. 03 ### A migration you can verify. Map your API calls, templates, domains and recipient restrictions before moving traffic. Our [migration guides](/docs/guides/email/migrate) cover provider differences, sandbox testing and cutover checks. Bring your current volume and peak traffic to the migration discussion. 04 ### Capacity and commercial terms. Compare included volume, domain limits, webhook endpoints and overage in the [published email plans](/products/email/pricing). Discuss dedicated IPs, peaks and invoicing with our team. Hosted sending, self-managed MTAs and monitoring products have their own setup and commercial requirements. 161% Increase in email open rates reported in Zillow’s customer story. [Read the Zillow story](/customers/zillow) ## When the right home appears, the email needs to arrive. Zillow brought time-sensitive property alerts to Bird, with the capacity to handle sending surges and the analytics to understand engagement. Its team reported a 161% increase in open rates in the first month. Planning a migration or a higher-volume send? [Contact sales](/demo?product=enterprise) ## Questions about enterprise email ### Can we use the Email API without operating our own infrastructure? Yes. Bird operates the sending infrastructure for the hosted Email API and SMTP relay. Your team integrates the service, configures sending domains and manages recipient permissions. PowerMTA and Momentum are separate options for teams that want to operate an MTA. ### How do we evaluate availability and support? Discuss the availability, response targets, support hours and escalation your application needs with our email team. Confirm the agreed commitments and any remedies in your service agreement before moving production traffic. The service status page reports current operations. ### Where can our security team review data protection information? Use the Bird Trust Center for security information and available reports. Review the Data Processing Agreement and subprocessor list, then confirm processing locations, retention and access requirements for your selected services with our team. ### What's the difference between Momentum MTA and PowerMTA? Both are on-prem MTAs you run yourself instead of sending through our managed API. Momentum MTA is built around customizable workflows and routing for high-volume sending. PowerMTA is built to run on your own servers or any public cloud, such as AWS or Azure. ### Who is this for, and do I need to run my own MTA to use Inbox Insights or Competitive Insights? Teams with infrastructure or compliance requirements that call for running their own MTA, and teams that want independent visibility into inbox placement and competitive benchmarking rather than relying on their own send metrics alone. The first group runs Momentum MTA or PowerMTA. The second group uses Inbox Insights, which estimates inbox placement and supports campaign seed tests, or Competitive Insights, which benchmarks your program against other brands, and neither of those requires you to self-host anything. LEARN / BUILD / OPERATE ## Choose your operating model Explore hosted sending, self-managed infrastructure and monitoring. [Momentum MTA Customize message processing and delivery policies on infrastructure you operate.](/momentum-email) [PowerMTA Control virtual MTAs, sending IPs and queues on your own servers or in a public cloud.](/powermta) [Inbox Insights Seed-measured inbox placement and campaign tests for your verified domains.](/inbox-placement-testing) [Competitive Insights Benchmark your email program against other brands in your industry.](/competitor-email-monitoring) [SparkPost SparkPost is now Bird Email: same deliverability engine, one API.](/products/email/sparkpost) [Email API overview Explore sending, delivery events, SDKs and integration guides.](/email-api) Talk to our email team ## Plan email around your infrastructure. Talk through your sending volume, operating requirements and migration. We’ll help you evaluate managed sending, PowerMTA or Momentum for your team. [Talk to sales ↗](/demo?product=enterprise) [Explore the Email API](/email-api) Send your requirements. Our team will follow up by email to discuss deployment and commercial terms. ## Related resources - [Choose your email infrastructure](/guides/choose-email-infrastructure) (docs)