What does email server cost depend on before you choose build, partner or SaaS?
The answer depends mostly on mailbox count, retention obligations, deliverability work and who carries the administration time. Open-source mail software such as Stalwart, mailcow or OX App Suite is usually not the largest line in the budget. The larger items are the infrastructure that runs it, the work needed to keep outbound mail trusted, and the people who keep it running. Before comparing against a per-mailbox hosted service, a team should write down its mailbox count (including shared, resource and service mailboxes), how long each mailbox class must keep messages, and whether it already has staff who understand SPF, DKIM, DMARC and mail queue behavior.
The cost differences come from who pays for each component. With a hosted service, the provider carries the servers, filtering, reputation management and most of the backup. With a self-hosted build, the organization pays for compute, storage with its own growth curve, an outbound relay or clean IP path, spam and malware filtering, a separate archive where retention rules require one, backup copies that are tested, and the migration project itself. Some of these are one-time (migration, initial design, archive setup) and others recur (infrastructure, licenses, patching, monitoring and the hours spent on blocklisting or false positives). A partner quote should separate these and state which items are included.
Confirm three things before requesting numbers. First, whether the chosen edition or module carries a license fee, since the OX App Suite Operations Guide states that the right to use certain modules or features may be subject to custom packaging, limitations or separate fees set in the license agreement. Second, which parts of the service a partner will operate after go-live and at what support level. Third, what the partner assumes about storage growth, peak mailbox load and archive volume. Ask for each assumption in writing so that the quote can be compared line by line with a per-mailbox hosted price. DeployOpen does not publish a price list, and any figure should come from a written scope.
Email server cost components: in-house, partner and SaaS
This table compares who pays for each email cost component under an in-house build, a fixed-scope partner engagement and per-mailbox SaaS, and marks each row as one-time or recurring. Read it as a checklist for asking what a quote or SaaS fee includes, because most of the recurring cost sits in deliverability, filtering, archiving and administration rather than in the server itself.
| Component | In-house | Partner | SaaS |
|---|---|---|---|
| Server and storage (recurring) | Your team pays for compute, storage growth, redundancy and capacity planning, and the time to size them | Fixed-scope build of the hosting design, then recurring hosting in your cloud or data center under agreed scope | Covered by the per-mailbox fee; storage limits and overage terms need confirmation |
| Outbound relay or clean IP addresses (recurring) | You pay for IP space, relay service if used, and staff time to manage reverse DNS, TLS and reputation | Relay selection and configuration scoped up front; relay subscription and IP costs remain yours | Usually included in the fee; confirm sending limits and whether dedicated IPs cost extra |
| Spam and malware filtering (recurring) | You pay for filtering software or subscriptions, rule tuning and false positive handling | Setup of the filtering layer is one-time; tuning and monitoring can be a retainer | Included in the fee; confirm filter tuning access and quarantine retention |
| Archiving for regulated retention (recurring) | Separate archive platform or storage, legal hold tooling and search, plus the records work to meet retention rules | Archive design and integration scoped separately; archive storage and licenses stay with you | Often an add-on tier; confirm whether it meets the retention period your regulator requires |
| Backup and restore testing (recurring) | Backup software, offsite copies, restore tests and the recovery runbook | Backup design and first restore test are one-time; ongoing testing can be a retainer | Vendor backup terms apply; you still own proof of restore for your own retention needs |
| Migration from current provider (one-time) | Staff time for mailbox, calendar and contact moves, testing and cutover planning | Fixed-scope migration project with agreed mailbox counts and cutover window | Migration tools may be included or charged separately; confirm data export format |
| Deliverability monitoring (recurring) | Staff time to watch DMARC reports, blocklists and provider postmaster data, and respond to incidents | Monitoring set up in scope; ongoing reviews available under retainer | Often provided as a dashboard; incident response and sender reputation remedies may be extra |
| Administration time (recurring) | The largest hidden cost: patching, user lifecycle, incidents, on-call coverage and upgrades | Runbooks, documentation and handover are one-time; support hours are set in the retainer | Lower admin effort for the platform; you still manage users, domains, aliases and policies |
| Licensing (one-time or recurring) | Open-source licenses cost nothing to acquire, but commercial editions, such as a Stalwart Enterprise License or an OX App Suite agreement, carry fees set in the contract | Partner passes through third-party license fees as agreed in scope; confirm which party holds the license | Per-mailbox fee covers the platform license; confirm feature tiers, user caps and annual terms |
| Support and upgrades (recurring) | Your staff track release cycles. For OX App Suite, standard releases have a 12-week support window and LTS releases run to the next LTS plus six months | Upgrade and support windows included in a retainer; scope the release policy in writing | Provider handles platform upgrades on its schedule; you control timing only where the contract allows |
What moves the email server cost up or down
Self-hosted email cost is set less by the server itself than by how many mailboxes you run, how long you must keep messages, how much uptime you promise, and how much sending and integration work sits around the mail server. Each driver below shifts either the one-time build cost, the recurring run cost, or both, so ask for each one to be priced separately in any quote.
Mailbox count and growth
Mailbox count drives storage, backup volume, filtering load and the size of any per-user license you pay for groupware. Growth matters as much as the starting count, because storage and backup capacity must be sized for the year-three mailbox footprint, not today's. Ask the partner to model storage growth per mailbox, including attachments and calendar data, and to state which parts scale with users and which scale with message volume. Mailbox growth mostly raises recurring cost, with a smaller one-time cost for initial sizing and migration.
Retention period and legal hold
Retention is the largest cost lever for regulated firms. Where a rule sets a minimum keep period, such as the three-year minimum in SEC Rule 17a-4(b)(4) for broker-dealers, every message must sit in a separate, searchable archive for that duration, and legal holds can extend it further. That means archive storage, journaling configuration, search tooling and eDiscovery support recur for years. Confirm whether the archive is part of the quote or left to a third party, and who keeps the records for the full period.
High availability and multi-site design
A single mail server is cheaper to build but leaves you without mail during an outage, which regulated buyers often cannot accept. Highly available designs add a second node or site, shared or replicated storage, load balancing, and tested failover. These raise one-time build cost for the architecture and test runs, and recurring cost for duplicate infrastructure, replication capacity and periodic failover exercises. Ask whether the quote includes a documented recovery test.
Outbound volume and sender reputation work
Sending volume and the reputation of your sending IP addresses decide whether you need a clean relay or smarthost, dedicated IP addresses, and ongoing monitoring of blocklists and mailbox provider feedback. Higher outbound volume, such as newsletters, notifications or citizen correspondence, increases relay fees and the time spent on warm-up and complaint handling. Reputation work is mostly recurring. Ask who owns SPF, DKIM and DMARC maintenance and who answers when a blocklisting occurs.
Integrations with directory, archive and clients
Each system the mail platform must talk to adds build effort and later maintenance. Directory integration for single sign-on and provisioning, archive connectors, calendar and contact sync, mobile device access, and ticketing or document systems all need configuration, testing and updates after every release. Integration cost is mostly one-time at build, then recurring as each connected system changes. List every integration in the scope before pricing, and note which ones your identity provider or archive vendor must support.
Release cadence the team will maintain
How often you upgrade the mail platform, the operating system and the filtering components sets the labor you carry every year. Mail software ships updates on its own cycle, and some groupware such as OX App Suite runs on support windows with long-term release branches, so the supported release and its end date should shape your upgrade calendar. Ask the partner to state the release you will start on, how long it is supported, and what upgrades are included in a retainer versus charged separately. Upgrade work is recurring, and a major platform change can add one-time migration cost.
Why OX App Suite and Stalwart licensing are separate line items
Open-source licenses change what you pay for, but they do not remove the license line from the budget. Stalwart is licensed under AGPL-3.0 and is offered with an optional Enterprise License from Stalwart Labs, so the community edition carries no per-mailbox fee while a commercial agreement can add one. mailcow-dockerized is licensed under GPL-3.0, which likewise permits use without a per-mailbox fee. Confirm in writing which edition, feature set and support tier you are pricing, because the license decision and the support decision are separate costs. OX App Suite needs a different check. Open-Xchange's Operations Guide states that the right to use certain modules or features may be subject to custom packaging, limitations or separate fees set in the license agreement. Ask the vendor or partner to list every module you need (mail, calendar, contacts, drive, and any groupware extras) and to state in the agreement whether each one is included, limited or separately priced. The public AGPL-3.0 mirrors of the App Suite UI and middleware on GitHub do not settle that question on their own.
Support dates are also a cost driver, because they set how often you must upgrade. Open-Xchange's support commitment says a standard release is supported for 12 weeks, ending with the availability of the third following release. An LTS release is supported until the next LTS release plus six months. The commitment page lists v8.35 as the first v8 LTS, now discontinued, and v8.47 as the current LTS, so plan upgrade effort against those windows. Ask for the support end date of the exact version you will deploy, and price the upgrade cycle, testing and change windows into your three-year model rather than treating them as a one-time setup cost. Before comparing totals with a hosted per-mailbox bill, put each license, support tier and upgrade commitment on its own line with its source and renewal date. Ask your implementation partner and the vendor to confirm each item in writing, including any feature gates that would force a later upgrade in license tier.
Where administration time and deliverability work actually go
The recurring work that is easiest to leave out of a budget is the sender-reputation and security upkeep that keeps mail flowing. Once mail is self-hosted, someone must watch SPF, DKIM and DMARC alignment for every sending domain, confirm that reverse DNS and TLS still match what receiving servers expect, and read DMARC aggregate reports for new or unauthorized senders. When a sending IP appears on a DNS blocklist, someone must identify the cause, fix it, and request delisting, which is slow and depends on the list operator. Spam tuning is never finished either: false positives on invoices, vendor replies and calendar invitations are reported by users and must be traced to Rspamd rules, DNS blocklist hits or ClamAV results, then corrected without reopening the door to phishing.
Security patching follows the vendors' schedules, not yours. The Zammad 7.2.2 release of October 8, 2026 was published as a security update, which illustrates that fixes can arrive outside any planned window. The same applies to the mail server, the webmail or groupware layer, the antivirus signatures, the spam rules and the operating system beneath them. Each update needs someone who can read the release notes, test against your configuration, and roll back. Mailbox migration and tenant retirement add a bounded but skilled project: planning domains and address lists, moving mailboxes and calendars without loss, running coexistence routing, and deciding when the old tenant's DNS records, connectors and retention holds can finally be removed.
Ask each partner to describe who performs these tasks, how often, and how each is billed. Ask whether monitoring of DMARC reports, blocklists and postmaster data is included in a retainer or charged per incident, who holds the skills to tune filtering and handle delisting requests, and who patches the stack when a security release lands outside a scheduled window. Ask how migration is scoped, whether rollback is part of the fixed price, and what happens to the old tenant. Confirm these answers in writing, because a partner that cannot name the staff and the billing unit for each task has not priced the recurring work that determines how the system performs in production.
How to build your own email cost estimate
This sequence turns a vague sense that self-hosted mail might be cheaper into a like-for-like comparison of build, partner and per-mailbox SaaS costs, with each figure traced to a written source. Work through it in order so the final totals rest on the same mailbox counts, retention rules and period.
Count mailboxes and project their growth
Start with a current count of active mailboxes, shared mailboxes, resource calendars and external aliases, split by department and site. Add a growth assumption for the planning period and record who approved it, usually the IT lead with input from HR. Done when you have one table that every later step uses, so each candidate is priced against the same number of accounts. Confirm with each vendor or partner how they bill shared mailboxes and aliases, because some hosted plans count them as full licenses.
Document retention and legal hold obligations
Ask legal, compliance and records management which rules apply to business email, such as a regulator's preservation period, a contractual hold or an internal retention schedule. Record the period, the message types covered and who can place a hold. Done when the requirement is written down with its source, because archiving, journaling and storage volume all follow from it. Regulated sectors have their own rules, so confirm the exact obligation with counsel rather than assuming a generic period.
Choose the delivery model for each component
Split the service into parts: mail and calendar server, storage, outbound relay or sending IP addresses, spam and malware filtering, archiving, backup, monitoring and migration. For each part, mark whether your team builds and runs it, a partner runs it under contract, or a SaaS provider supplies it. Done when every component has one owner. Mixed models are common, for example an in-house mail server with a managed filtering service, so note where responsibility changes hands.
List infrastructure requirements for each candidate
For OX App Suite v8, list the Kubernetes cluster, Helm 3.17.0 or newer, Kubernetes versions N-1 and N-2, and either Istio (the latest release plus two prior versions) or the basic ingress-nginx option where Istio cannot be used. Add Redis 7.4.x, a MariaDB version from 10.6.x, 10.11.x, 11.4.x or 11.8.x, and a distributed file system for attachments: NFS for small to mid-size deployments or object storage such as AWS S3, Ceph RadosGW or Scality RING for larger ones. For self-hosted alternatives such as Stalwart or mailcow, list the host sizes, storage, backup target and high availability design. Done when each requirement has a line item and a cost source.
Separate one-time costs from recurring costs
Divide every line into one-time items, such as design, migration, initial configuration, hardening and integration with the directory, and recurring items, such as hosting, storage growth, licensing, filtering subscriptions, support, patching and administration time. Include the staff hours that deliverability work takes, such as DNS record maintenance, DKIM key rotation, DMARC report review and blocklist response. Done when each total shows its one-time and annual components separately, so the first year does not hide the run cost.
Request written scope and quotes from each candidate
Send the same written requirements to each candidate, including the mailbox count, retention rule, infrastructure assumptions and support hours you expect. Ask for a fixed scope with deliverables, exclusions and the licensing terms that apply, such as any fees for modules or features that the vendor's documentation says may be packaged or charged separately. Done when every quote is traceable to the same requirements and each exclusion is listed. Ask the vendor or partner to confirm every figure in writing rather than relying on published list prices or your own estimates.
Compare totals over the same period
Place each candidate's one-time and recurring costs on the same time horizon and the same mailbox count, then add the costs that quotes often omit: exit or migration costs if you later move, and the effort to keep the platform on a supported release. Done when you have one comparison sheet with every assumption visible and a note on which figures are confirmed and which are still open. Present the result as a range that reflects the open items, not a single number, and share it with finance and security before a decision.
What do buyers ask before they hire outside help for email?
How much effort does a self-hosted mail platform take to run each month?
The monthly effort depends less on the mail server itself and more on the layers around it: spam and malware filtering, sender authentication monitoring, blocklist checks, patching, backup verification, and user administration. Stalwart and mailcow both ship as actively maintained releases, with Stalwart v0.16.26 published on October 11, 2026 and mailcow-dockerized release 2026-09a published on October 6, 2026, so a team should plan for regular upgrade windows. Ask any partner to list the recurring tasks in writing, with a named owner and a frequency for each. If you add an archive, a relay for outbound mail or a commercial gateway, each adds its own administration load and vendor contract.
Can a small IT team run self-hosted email without an outside partner?
A small team can run a single-domain mail platform in-house if it already administers Linux, DNS, TLS certificates and containers, and if it can give deliverability problems dedicated attention. The harder cases are sender reputation recovery, a blocklisting that stops outbound delivery, and a regulated archive that must be defensible in an examination. Before deciding, confirm who will watch DMARC reports, who responds to a blocklisting within hours rather than days, and who holds on-call duty during an outage. A partner can cover the build and then hand over documentation and runbooks, or support the team through a retainer.
How long does migration from a hosted mail tenant take, and what does it need from us?
Migration duration depends on mailbox count, total data volume, the number of domains, and how much coexistence routing is needed during cutover. No researched timeline applies to every estate, so ask for the duration in the written scope rather than a generic figure. Plan to provide DNS access for MX, SPF, DKIM and DMARC records, a current mailbox and alias inventory, shared mailbox and distribution list details, and a named approver who signs off each cutover stage. Expect a test mailbox pass before any production move, and ask how mail is queued during the switch.
Does open-source licensing mean self-hosted email has no software fees?
No. Open-source licensing removes per-mailbox subscription fees for the core server, but it does not remove every cost or license term. OX App Suite is delivered with Helm charts under the vendor's own support and packaging terms, and Open-Xchange's Operations Guide states that certain modules or features may be subject to custom packaging, limitations or separate fees set in the license agreement. Stalwart is licensed under AGPL-3.0 with an optional Enterprise License from Stalwart Labs. Confirm in writing which components are covered by the open-source license and which carry separate terms, and budget for the infrastructure, storage and administration either way.
How is a partner's fixed-scope quote structured for an email project?
DeployOpen works from a written scope, and most engagements are fixed-scope, with scope, deliverables and timelines agreed in writing before work starts. A quote should separate the build (architecture, installation, configuration, filtering, authentication records, migration waves, and testing), the handover (documentation, runbooks and training), and any optional items such as archiving integration or a commercial gateway. DeployOpen does not publish a price list, so ask each bidder to state assumptions about mailbox count, domains, hosting location, and which parts the client performs. Compare quotes on the same scope definition, not on headline totals.
What do ongoing retainers cover after a self-hosted email build?
DeployOpen offers ongoing support, upgrades and continuous testing as retainers, and a retainer is the usual way to keep a mail platform current after go-live. Typical retainer scope covers platform upgrades, monitoring follow-up, filter tuning, backup restore checks, and responses to deliverability incidents, but the exact terms are set in the written agreement. Ask which response windows and service levels are included, since no SLA applies by default. Check how upgrades are scheduled against vendor release cycles, such as the Open-Xchange support commitment for standard and LTS releases.
When is hosted email the cheaper choice than self-hosting?
Hosted email is usually the cheaper choice when the organization is small, has no in-house mail or security staff, has no retention or data residency obligation that forces control of the mail store, and does not need custom routing or branded platforms. Self-hosting adds fixed costs for servers, storage, relay or IP reputation management, filtering, archiving and backup, and a recurring administration load. Build a comparison for your own mailbox count and cost categories, then include the hidden items: migration effort, outage handling, blocklisting response and the cost of a compliance audit trail. Ask any partner to show the break-even assumptions behind its comparison.
What should we check first before comparing email vendors and quotes?
Start with the requirements that change the cost: mailbox count, domains, retention period, whether mail carries regulated data, whether outbound mail needs a relay, and the existing directory and identity setup. Then confirm the platform's supported database, storage and Kubernetes prerequisites where they apply, since OX App Suite v8 requires Helm 3.17.0 or newer and uses MariaDB with InnoDB. Ask each bidder to state which items are in scope and which are client responsibilities. This keeps the comparison based on the same facts rather than on marketing claims.
How DeployOpen scopes and delivers a fixed-scope email implementation
DeployOpen plans, implements, integrates, hardens, backs up, documents and supports self-hosted open-source platforms inside your own cloud accounts, data centers or air-gapped networks. For email, that means turning a build, partner or SaaS cost question into a written scope that names every cost component before any work starts.
How we scope
- Count mailboxes, shared mailboxes, resources and external relay volume so the scope reflects real sizing inputs
- List which cost lines are in scope: servers, storage, relay, filtering, archiving, backup, migration and administration
- Agree in writing which items are one-time work and which recur, and who pays for each
How we build
- Deploy the chosen mail platform, such as Stalwart, mailcow or OX App Suite, inside your infrastructure
- Configure SPF, DKIM and DMARC records and test deliverability before any mailbox moves
- Integrate filtering, archive and backup components, and test restores against the agreed design
How we hand over
- Document the cost model, sizing assumptions and ongoing task list so your team can compare options later
- Deliver runbooks for mailbox provisioning, blocklist response, update cycles and backup restores
- Walk through the written handover with your administrators and record what they have confirmed
How we support
- Engagements are fixed-scope, so changes to mailbox counts or features are agreed in writing first
- Ongoing support, upgrades and continuous testing are available as a retainer
- Ask any partner, including us, to put every recurring fee and administration hour in the quote
