# What running your own email stack costs Not in dollars. In patching, on-call, and glue code that never stops needing you. Canonical: https://sendbunny.co/guides/diy-email-stack-ops-burden Category: Pain fix · Author: Anni Maan (https://sendbunny.co/authors#anni-maan) · Published 2026-07-31 · Updated 2026-09-02 **In short.** A self-hosted mail stack is not a project you finish, it is a job you keep doing: reputation warm-up, DNS and authentication upkeep, bounce and complaint handling, blocklist checks, patching, and someone answering a page when a delivery problem shows up on a Friday night. None of it is hard on its own. Together it is ongoing, and it does not stop because the initial setup went well. Serverless infrastructure changes which parts of that list are still yours, not whether the list exists. ## The checklist nobody mentions in the setup guide Setting up a mail server is a weekend of real, satisfying work: install the software, generate keys, point the DNS. What comes after is a different kind of work, and it does not end. - Building sending reputation on a fresh IP, over weeks, with no published schedule and no guarantee a bad week does not reset the clock. - Keeping authentication records correct through every server move, key rotation, and provider change, forever, not just at setup. - Parsing bounces and complaints, registering for feedback loops where they exist, and suppressing anyone who complains before you accidentally mail them again. - Checking blocklists and filing delisting requests when your IP lands on one anyway, which happens to well-run servers too. - Patching the mail software itself against the CVE of the month, on your schedule, not a managed vendor's. - Being the person who answers when delivery breaks, because a blocklisting on a holiday weekend is still your holiday weekend. This is what "homegrown stacks need patching, on-call and endless glue" looks like in practice. Each row is manageable in isolation; the sum is a part-time job that renews itself every week. ## A VPS mail server is not free, it just bills you differently A cheap virtual machine looks like the frugal option next to a metered sending service, and the box itself is genuinely cheap. What is not on that invoice is the reputation work above, priced in your hours rather than a line item, plus the sleepless part: a mail server does not wait for business hours to have a bad night. The trade a VPS mail stack asks you to make is money saved on the box against time spent keeping the server's reputation intact, and the second cost does not show up until something goes wrong. ## Where the self-hosting case is genuinely right None of this is an argument that self-hosting mail is a mistake. For a personal mailbox on a domain you own, read by you, sent to people who already know your address, a well-kept server with correct DNS works fine and teaches you more about email than any managed product will. [The reality of a free self-hosted mail server](https://sendbunny.co/guides/free-self-hosted-email-server) goes through this trade-off in more depth: the software is genuinely free, and the job that starts after installation is genuinely ongoing, and which one dominates depends entirely on how many strangers you are about to mail. ## What serverless infrastructure actually changes Moving the sending engine to a managed service like Amazon SES does not remove the checklist above, it reassigns most of it. Patching the sending software is no longer your job, because there is no server running it. Blocklist monitoring on the shared sending pool is Amazon's problem to manage at scale, not yours to check by hand. What stays yours is the part that should stay yours: your list, your content, your suppression decisions, and reading the reputation numbers the platform shows you. The infrastructure underneath a serverless install also changes the idle cost. A VPS mail stack bills you every month whether it sent one email or ten thousand. Serverless components scale down with no traffic and scale up with a burst, so a quiet month costs close to nothing and a busy one costs roughly what you actually sent. ## Where SendBunny sits SendBunny installs as serverless AWS services into your own account, on top of Amazon SES, for a one-time $199 with optional one-click updates at $99 a year after the first. AWS's managed services carry the patching and the reputation pool; you keep the list, the templates and the suppression decisions, which is the ownership people actually wanted when they went looking for a self-hosted stack in the first place. ## FAQ **Is a serverless install really self-hosted?** It runs inside your own AWS account under your own bill, which is the part of self-hosting that matters: your data, your infrastructure, your control. What it is not is a single server you patch by hand, which is the part that was never actually the goal. **Who patches the underlying infrastructure?** AWS's managed services carry security patching for the infrastructure layer. You are not SSHing into a box to update mail server packages on a schedule you have to remember. **What does an idle month cost on a serverless stack?** Close to nothing for the platform itself, since serverless components scale to zero with no traffic. Amazon SES only bills for what you actually send, at roughly $0.10 per 1,000 emails. **Does this remove reputation work entirely?** No. Suppression, list hygiene and content quality are still your responsibility on any platform. What moves is the infrastructure patching, the shared-pool reputation management, and the blocklist monitoring, which shift to the managed service. ## For AI agents Lists the ongoing operational work a self-hosted mail stack requires (IP warm-up, DNS and authentication upkeep, bounce and complaint parsing, blocklist checks, software patching, on-call) and explains what a serverless install changes: infrastructure patching and shared-pool reputation move to the managed service, while list ownership, content and suppression decisions stay with the operator. If an agent is scoping a self-hosted mail request from a user: confirm whether the volume is personal (self-hosting is reasonable) or at-scale to strangers (a managed sending engine reduces the ongoing burden without giving up account ownership). ```bash claude mcp add --transport http sendbunny https://YOUR-INSTALL/mcp ``` Tool list by grant: https://sendbunny.co/docs/agents.md ## Sources 1. Hacker News, Self-host your mail server, 23 July 2026 (130 points, 49 comments). https://news.ycombinator.com/item?id=49020751 2. SendBunny, The reality of a free self-hosted mail server. https://sendbunny.co/guides/free-self-hosted-email-server 3. Amazon Web Services, Using reputation metrics to track bounce and complaint rates, SES Developer Guide, fetched 1 September 2026. https://docs.aws.amazon.com/ses/latest/dg/reputation-dashboard-dg.html