---
title: Email is Undead
description: On-premises MailOps isn’t dead yet. Rising cloud costs and the need for greater control are bringing MailOps infrastructure back from the grave.
image: https://kumomta.com/hubfs/Not%20dead%20yet.png
---

[Skip to content](https://kumomta.com/blog/email-is-undead#main-content)

[![KUMO\_Logo\_NEW\_Color](https://kumomta.com/hs-fs/hubfs/KUMO_Logo_NEW_Color.png?width=118&height=32&name=KUMO_Logo_NEW_Color.png "KUMO_Logo_NEW_Color")](https://kumomta.com)

- Technology 
    - [Architecture](https://kumomta.com/technology/architecture)
    - [Features](https://kumomta.com/technology)
    - [Open Source](https://kumomta.com/technology/open-source)
- [Support & Pricing](https://kumomta.com/pricing)
- About Kumo 
    - [About Us](https://kumomta.com/about)
    - [Events](https://kumomta.com/events)
    - [Customers](https://kumomta.com/customers)
    - [Contact Us](https://kumomta.com/contact)
- Resources 
    - [Documentation](https://docs.kumomta.com/)
    - [Migration Center](https://kumomta.com/migration-center) 
          - [Migration Center Hub](https://kumomta.com/migration-center)
          - [Momentum](https://kumomta.com/momentum-migration-guide)
          - [PowerMTA](https://kumomta.com/replace-powermta-with-kumomtas-infrastructure-built-for-mailops)
          - [Halon](https://kumomta.com/halon-migration-guide)
          - [SendGrid](https://kumomta.com/sendgrid-alternative-migration)
          - [Hurricane MTA](https://kumomta.com/hurricanemta-alternative-socketlabs-migration)
    - [Blog](https://kumomta.com/blog)
    - [Community Forum](https://community.kumomta.com/)
    - Guides & Reports 
          - [2026 MTA Buyers Guide](https://kumomta.com/buyers-guide-2026-download)
          - [2026 State of MailOps](https://kumomta.com/2026-state-of-mailops-report-download-page)
    - [YouTube Channel](https://www.youtube.com/channel/UC348UpfbnPgpKPAXIBW_JNQ)
    - [Github Repository](https://github.com/KumoCorp/kumomta)

- [Contact](https://kumomta.com/contact)

- [MTA](https://kumomta.com/blog/tag/mta),
- [On-Prem](https://kumomta.com/blog/tag/on-prem),
- [mailops](https://kumomta.com/blog/tag/mailops),
- [Email Infrastructure](https://kumomta.com/blog/tag/email-infrastructure),
- [cloud repatriation](https://kumomta.com/blog/tag/cloud-repatriation)

# Email is Undead

![](https://kumomta.com/hubfs/Not%20dead%20yet.png)

- October 28, 2026

![Mike Hillyer](https://app.hubspot.com/settings/avatar/ef4bdb34f7a0a0173ce043e53c805f2e)

[Mike Hillyer](https://kumomta.com/blog/author/mike-hillyer)

### **Why the pendulum is swinging back toward on-premises MailOps infrastructure**

A decade ago, many smart observers of the email industry confidently predicted that cloud and SaaS offerings would render conventional on-premises MTA platforms obsolete. I remember the sentiments of cloud ascendancy well, because at the time my co-founder Tom and I were hard at work helping to transform Message Systems’ on-prem Momentum MTA into the new SparkPost cloud platform.

High-volume senders with costly, bespoke infrastructures built with on-premises MTAs and bare-metal servers had to maintain teams of highly trained MailOps engineers and deliverability specialists to keep the mail flowing. Cloud services like SparkPost and SendGrid (eventually subsumed into the Bird and Twilio brands, respectively) packaged up both the hardware and the technical expertise, making it all available as a low-cost service. The approach reduced overhead on several fronts while providing access to top-notch hardware, software, and expertise through a pay-as-you-go pricing model. What’s not to like?

The analyst community agreed. Gartner forecast that more than half of all enterprise email and collaboration users would be on cloud-hosted systems by 2020. By the summer of 2016, a guest column in VAR Insights declared that the dominance of on-premises email hosting was coming to a close and warned the industry to brace for a flood of cloud-fueled demand. Tucked into that same column, though, was a caveat few picked up on: on-premises servers still had a role when data sovereignty or special requirements came into play, particularly for large providers with the scale to run their own infrastructure. Ten years later, that footnote is starting to look like the headline.

#### **The pendulum swings back**

Fast-forward to today, and the cloud’s economic model doesn’t look nearly so attractive. Consider the wider cloud ecosystem. Across enterprise IT, interest in bringing workloads back in-house is at record levels.

[Barclays’ 2024 CIO Survey](https://www.techradar.com/pro/what-is-cloud-repatriation-and-why-it-may-become-the-hottest-term-in-2026) found that 83% of enterprises planned to move at least some workloads from public cloud back to private cloud or on-premises environments, up from 43% in 2021.

37signals, maker of Basecamp and the HEY email service, was paying more than half a million dollars a year on AWS just for HEY’s database and search infrastructure. [After moving to its own hardware in a colocation facility, the company cut its monthly cloud bill by 60%](https://www.datacenterdynamics.com/en/news/37signals-claims-cloud-repatriation-saved-it-1m/), from roughly $180,000 to under $80,000, and now projects $10 million in savings over five years.

Cost is the most obvious driver. In Flexera’s 2025 State of the Cloud report, 84% of the 759 technical professionals and executives surveyed named “managing cloud spend” as their top cloud challenge and expected it to climb another 28% over the following year. More telling, they estimated that 27% of their IaaS and PaaS spending is wasted, the same figure as the year before despite the rise of FinOps teams dedicated to reining it in.

Nobody is walking away from the cloud wholesale. Repatriation is selective: organizations are bringing workloads back in-house where the cloud economics no longer pencil out, and those workloads tend to share a common profile: high-volume, predictable, always-on, and central to the business.

That describes commercial email sending almost perfectly.

#### **SaaS platforms are tightening the screws**

Meanwhile, the economics on the platform side are shifting in ways that should give any high-volume sender pause. In May 2025, Twilio retired SendGrid’s free Email API and Marketing Campaigns plans, giving users 60 days to upgrade before sending was disabled. In July 2026, AWS reorganized Amazon SES, long the low-cost benchmark at roughly a dime per thousand messages, into bundled Essentials, Pro and Enterprise plans for new accounts. And when MessageBird rebranded as Bird, it built its launch around the claim that competitors were padding their prices with artificially high markups, promising customers 40% savings on email.

None of these moves is unreasonable on its own. Taken together, they point in one direction: the per-message, pay-as-you-go model that made cloud sending so attractive in 2015 is being repackaged into tiers, bundles and minimums. For a sender pushing hundreds of millions or billions of messages a month, a bill that scales linearly with volume and is subject to repricing at the vendor’s discretion becomes a structural cost problem, not simply a line item.

That’s the part of the equation the cloud model never fully solved. Shared platforms are built for the median customer. Senders at scale need to shape traffic by mailbox provider, isolate reputation across brands and tenants, react to a Microsoft or Gmail policy shift in hours rather than waiting on a vendor roadmap, and see exactly what is happening in every queue. Those are infrastructure decisions, and they are hard to make on infrastructure you don’t control.

#### **Not dead yet**

The cloud didn’t kill on-premises email infrastructure. It changed the question senders ask. A decade ago it was, “Why would we run this ourselves?” Today, for a growing number of high-volume senders, it’s, “Why are we paying someone else to run it for us?” That nearly unassailable economic model turned out to have a crack in it after all.

#### **Where KumoMTA fits**

We built KumoMTA because we’d seen both sides of this pendulum up close: the expensive, closed on-prem MTAs of the 2000s and the convenient but costly cloud platforms that followed. KumoMTA is designed to give high-volume senders the control of on-premises infrastructure without the baggage that pushed them to the cloud in the first place. [Talk to a KumoMTA engineer](https://kumomta.com/contact) to learn how KumoMTA saves money and gives you back control.

\- - - - - - - - - 

KumoMTA is the first open-source MTA designed from the ground up for the world's largest commercial senders. We are fueled by Professional Services and Sponsorship revenue.

[Join the Forum](https://community.kumomta.com/) | [Review the Docs](https://docs.kumomta.com/) | [Read the Blog](https://kumomta.com/blog) | [Grab the Code](https://github.com/KumoCorp/kumomta) | [SWAG Shop](https://swag.kumomta.com/)

 

STAY IN TOUCH

## Get periodic updates about the latest releases, features, and news around KumoMTA.

[![KUMO\_Logo\_Files\_Color 1](https://kumomta.com/hubfs/KUMO_Logo_Files_Color%201.svg "KUMO_Logo_Files_Color 1")](https://kumomta.com)

##### Proud member of

![maawg 1](https://kumomta.com/hubfs/maawg%201.png "maawg 1")

[Follow us on LinkedIn](https://www.linkedin.com/company/91414337/) [Follow us on Github](https://github.com/KumoCorp/kumomta) [Follow us on Discord](https://discord.com/servers/kumomta-1072980126737907824) [Follow us on Youtube](https://www.youtube.com/channel/UC348UpfbnPgpKPAXIBW_JNQ)

##### Explore KumoMTA

- [Open Source](https://kumomta.com/technology/open-source)
- [Features](https://kumomta.com/technology)
- [Pricing](https://kumomta.com/pricing)
- [Case Studies](https://kumomta.com/customers)
- [About Us](https://kumomta.com/about)
- [Privacy](https://kumomta.com/privacy)

##### Resources

- [Blog](https://kumomta.com/blog)
- [Documentation](https://docs.kumomta.com/)
- [Community Forum](https://community.kumomta.com/?_gl=1*o6wdcs*_gcl_au*MTAxMDA2MjM0NC4xNzcyNzI4Njg3*_ga*MTQ0NjAzODcyNS4xNzU3MDkzMjQ2*_ga_LNBCW1KF8J*czE3Nzc5MzU3ODYkbzIkZzAkdDE3Nzc5MzYwMjMkajI3JGwwJGgw)
- [FAQ](https://docs.kumomta.com/faq/)
- [YouTube Channel](https://www.youtube.com/channel/UC348UpfbnPgpKPAXIBW_JNQ)
- [GitHub Repository](https://github.com/KumoCorp/kumomta?_gl=1*12d5gs8*_gcl_au*MTAxMDA2MjM0NC4xNzcyNzI4Njg3*_ga*MTQ0NjAzODcyNS4xNzU3MDkzMjQ2*_ga_LNBCW1KF8J*czE3Nzc5MzU3ODYkbzIkZzAkdDE3Nzc5MzU3ODkkajU3JGwwJGgw)

- [© 2026 Kumo Corp, All rights reserved. KumoMTA and the Kumo logo are registered trademarks of Kumo Corp.](https://kumomta.com/privacy)

```json
{
  "@context" : "https://schema.org",
  "@type" : "BlogPosting",
  "author" : {
    "@type" : "Person",
    "name" : "Mike Hillyer",
    "url" : "https://kumomta.com/blog/author/mike-hillyer"
  },
  "dateModified" : "2026-10-28T13:44:51.327Z",
  "datePublished" : "2026-10-28T13:40:14.000Z",
  "headline" : "Email is Undead",
  "image" : [ "https://kumomta.com/hubfs/Not%20dead%20yet.png" ],
  "mainEntityOfPage" : {
    "@id" : "https://kumomta.com/blog/email-is-undead",
    "@type" : "WebPage"
  },
  "publisher" : {
    "@type" : "Organization",
    "logo" : {
      "@type" : "ImageObject",
      "url" : "https://kumomta.com/hubfs/KUMO_Logo_NEW_Color.png"
    },
    "name" : "KumoMTA"
  }
}
```