Zimbra comes up regularly when MSPs are looking for an alternative to self-hosting a Linux mail stack or paying Google and Microsoft per seat. It runs on proven open-source components, it has a dedicated Business Service Provider program for resellers, and its open-source edition is technically free. What it does not advertise as prominently: the BSP program carries a $200/month spend floor before you bill a single client, licenses are sold in 25-mailbox minimums, and WHMCS integration requires a separate paid module from a third-party vendor.

This article works through what Zimbra actually costs an MSP billing 20-200 client mailboxes, where the BSP program math starts to strain, and where Zimbra remains a genuinely sensible choice.

Table of Contents

Key Takeaways

Point Details
BSP minimum spend starts at $200/month Zimbra's Authorized BSP tier requires a $200/month minimum commitment regardless of how many mailboxes you actually bill. Silver jumps to $1,000/month.
Network Edition licenses: 25-mailbox minimums Professional Edition for 25 mailboxes runs $963/year ($3.21/mailbox/month) for the software license alone, before any server or admin costs.
No native WHMCS or Blesta module Provisioning automation requires a third-party ModulesGarden module at $15.95/month or $129.95/year, adding to the overhead small MSPs feel immediately.
Self-hosted total at 50 mailboxes: roughly $485/month License ($160.50) plus VPS ($25) plus modest admin time at $75/hr (4 hours = $300). Atriomail's wholesale cost for the same 50 mailboxes: $69.50/month, all in.

Three Deployment Paths

When an MSP looks at Zimbra, there are three distinct products on offer, and they carry very different cost structures:

  • Zimbra Open Source Edition. Free to download and self-host, no license cost. Includes core email, calendar, contacts, and task management. Does not include Outlook Connector (MAPI sync), Exchange ActiveSync for mobile, or archiving and litigation hold. Community support only. The free tier still carries the full infrastructure and admin cost of running the software.
  • Zimbra Network Edition (Standard or Professional). A commercially licensed version with a subscription or perpetual license. Adds Outlook Connector, ActiveSync, and archiving (Professional only). Sold through Zimbra's partner channel in 25-mailbox increments. This is the product MSPs typically license when they want to self-host for clients.
  • Zimbra BSP Edition. Zimbra's hosted multi-tenant program designed specifically for Business Service Providers who want to resell managed Zimbra email without running the entire mail stack themselves. Pricing is not publicly listed per-mailbox; access is gated by a minimum monthly spend.

For a 1-15 person MSP billing 20-200 client domains, the relevant choice is usually between running Network Edition on a VPS or joining the BSP program. Either path involves tradeoffs that the sections below examine in full.

The BSP Program: Minimum Spend and Tier Structure

The BSP program targets hosting companies and MSPs who want Zimbra to handle the underlying infrastructure while they manage client branding and billing. Zimbra's published BSP Program Guide (updated February 2026) defines four tiers, with minimum monthly spend requirements updated as of January 2026:

BSP Tier Monthly Minimum Spend Notes
Authorized $200/month Entry level; access to partner portal and BSP pricing
Silver $1,000/month Priority support, MDF eligibility
Gold $5,000/month Dedicated account management, higher MDF
Platinum Custom Large telcos and hosting platforms; negotiated terms

The $200/month floor at Authorized tier is the one that matters most for small MSPs. At that level you are committing $2,400/year before a single client invoice is sent. If your client base is 30-40 mailboxes and you charge $5/mailbox, the minimum spend consumes more than your entire gross revenue on that product line. The math only works once you are billing enough volume that the monthly minimum is not the binding constraint.

BSP per-mailbox pricing is not publicly listed by Zimbra and is negotiated at the point of program onboarding. For context on the margin structure, some authorized Zimbra hosting partners set retail prices in the $4-6/mailbox/month range for a standard mailbox, which gives a window into what the market-level client charge looks like. Actual wholesale margin depends on the tier negotiated.

Self-Hosted Zimbra: License, Server, and Admin Math at 50 Mailboxes

For MSPs who prefer to own the infrastructure, Network Edition is the relevant path. The software requires Linux (Ubuntu or Red Hat-based distributions), with a minimum of 8 GB RAM for single-server deployments of up to 150 accounts. The stack it installs is not lightweight: Postfix, OpenLDAP, Amavis, ClamAV, nginx, and a JVM-based web application layer all run together on the same server.

Published Zimbra Network Edition pricing (Professional Edition, 25-mailbox minimum subscription) runs $963/year with Standard Support. That works out to $38.52/mailbox/year, or $3.21/mailbox/month, for the software license alone.

At 50 mailboxes, you need two 25-license packs: $1,926/year, or $160.50/month just for the license. Add the server and the admin time, and the total looks like this:

Cost component Monthly estimate Basis
Zimbra Network Edition Professional (50 mailboxes, 2 × 25-pack) $160.50 $963/year per 25 mailboxes, from XMission/Zimbra partner pricing
Linux VPS (8 GB RAM, adequate for ~150 accounts) ~$25 Hetzner CX32 or equivalent
Admin time (4 hrs/month at $75/hr) $300 Zimbra's stack requires regular attention: LDAP, certificate, spam filter, Java heap tuning
Total ~$485/month For 50 mailboxes; does not include the WHMCS module (see below)

Four admin hours per month is a conservative estimate for an experienced operator managing a production Zimbra deployment. In practice, new-client onboarding, per-domain DNS configuration (all manual in Zimbra), and occasional JVM restarts push that figure higher. Our earlier comparison of self-hosted mail server versus managed white-label hosting found very similar dynamics across other Linux mail stacks, and Zimbra's administrative surface is broader than most.

The 20% late renewal penalty Zimbra charges on expired licenses is worth noting: if a billing cycle slips and support lapses, reinstatement costs more, not less, than staying current.

Zimbra Network Edition self-hosted (50 mailboxes) ~$485/mo Atriomail wholesale (50 mailboxes at $1.39) $69.50/mo $0 $100 $200 $300 $400+
Monthly cost for 50 mailboxes: Zimbra self-hosted (license + VPS + admin) vs. Atriomail wholesale. Admin time is calculated at $75/hr for 4 hours, which is conservative for a production Zimbra deployment.

The case for per-mailbox pricing in the context of a reseller business is that costs scale with revenue: you pay for exactly what you provision, no more. Zimbra's licensing structure inverts that for small books, because the 25-mailbox minimum means you buy capacity before you have clients to fill it.

WHMCS and Blesta: The Missing Native Module

Zimbra does not publish a native WHMCS or Blesta provisioning module. For MSPs who automate email billing through WHMCS or Blesta, that means evaluating third-party options.

The most mature option is ModulesGarden's Zimbra and Carbonio Email for WHMCS, which supports automated account provisioning, suspension, termination, password management, and client-area mailbox management. Pricing is $15.95/month, $129.95/year, or $899.95 as a one-time permanent license. At the monthly rate, a 12-month subscription adds $191.40/year to the operational cost before any mailboxes are provisioned.

Blesta compatibility for Zimbra is more limited: no ModulesGarden Blesta module exists for Zimbra at time of writing. MSPs running Blesta as their billing platform would need to handle provisioning manually or build a custom integration against the Zimbra admin API.

The module overhead is not prohibitive in absolute terms, but it is one more vendor relationship to manage, one more license to renew, and one more place for a provisioning failure to occur. For comparison purposes, a purpose-built white-label email platform typically ships native WHMCS and Blesta modules as part of the base offering, with no separate module cost.

DNS and Deliverability: Per-Domain Setup Overhead

Every client domain an MSP onboards into Zimbra requires manual DNS record creation at the registrar or DNS provider: SPF, DKIM (generated by Zimbra but not published automatically to external DNS), and DMARC. Zimbra generates DKIM keys and signs outbound mail correctly, but it has no built-in integration with external DNS providers to publish those records automatically.

For an MSP managing 20 client domains, that is 20 manual record-creation steps on day one, and another manual step for every domain added after that. Clients whose domains move registrars will need records recreated. Clients who let records expire while support tickets pile up become deliverability risks for the entire shared IP pool.

The cost of manual DNS at scale is mostly absorbed in support tickets. A client who cannot send email because DKIM is misconfigured does not open a "please fix my DNS" ticket; they open an "email is broken" ticket, which typically takes longer to diagnose. Managing a growing book of Zimbra-hosted domains is manageable, but the per-domain manual overhead is real and compounds with client count in ways that automated DNS publishing does not.

Atriomail admin panel Domains and DNS screen showing automated SPF, DKIM and DMARC record status per domain

The Atriomail DNS panel: SPF, DKIM, and DMARC publish automatically to 15 supported providers when a domain is added, not as a manual step for each one.

This matters particularly for the multi-client management workflow that separates a scalable email practice from one where client count creates linear support load growth. Automated DNS is one of the clearest differences between a mail server product and a managed email platform built for resellers.

When Zimbra Makes Sense

Zimbra is a genuinely capable platform, and there are MSP situations where it is clearly the right tool:

  • Data sovereignty requirements. Regulated industries in some jurisdictions require that email data reside on infrastructure the organization controls. A self-hosted Zimbra Network Edition deployment on a VPS in a specific geography satisfies that requirement in a way a managed cloud platform cannot. If a client's compliance team has written "on-premises or dedicated hardware" into their requirements, Zimbra is one of the credible answers.
  • Clients that need MAPI-native Outlook with full sync. Zimbra Professional Edition's Outlook Connector provides native MAPI connectivity, giving desktop Outlook the same calendar and contacts sync it has with Exchange. For clients who have standardized on Outlook and will not use webmail or IMAP, that matters. The SmarterMail comparison covers the same consideration on a Windows-based stack.
  • Archiving and litigation hold at a lower total cost than Exchange. Zimbra Professional Edition includes email archiving and litigation hold natively. For legal or compliance-heavy clients who need these features but cannot justify Exchange Online Archive ($3/user/month on top of an Exchange Online plan), Zimbra is worth evaluating.
  • Large ISPs and regional hosting providers. The BSP program's economics improve substantially at Silver tier ($1,000/month minimum) and above, where the per-mailbox wholesale cost becomes competitive and a dedicated account manager is included. Operators with 1,000 or more mailboxes under management are the intended target for the BSP tier structure.
  • Existing Zimbra deployments. If an MSP already manages several clients on Zimbra and has the stack running reliably, migrating for the sake of a cost comparison is rarely worth the disruption. The switching cost is real, and a well-managed Zimbra deployment compounds in operational knowledge over time.

The Atriomail Alternative

The gaps this article has documented in Zimbra's reseller path -- the $200/month BSP minimum, the 25-mailbox license floor, the third-party WHMCS module, the per-domain manual DNS -- are precisely where a purpose-built managed white-label platform sits differently.

Atriomail's wholesale price is $1.39 per mailbox per month, 15 GB included, with no minimum commitment and no per-25-block license structure. One mailbox or two hundred: billing starts at the first mailbox provisioned and stops the month a mailbox is removed. For an MSP whose client base is still growing, that means costs scale with revenue rather than requiring a fixed floor commitment in advance.

Addressing the specific gaps from this comparison:

  • No minimum spend floor. 10 mailboxes costs $13.90/month. 50 costs $69.50/month. There is no minimum that consumes margin before any client revenue exists.
  • Native WHMCS and Blesta modules, no third-party vendor required. Provisioning, suspension, and termination are automated through the billing platform an MSP already runs, at no additional module cost.
  • Automated DNS for 15 providers. SPF, DKIM, and DMARC publish automatically when a domain is added, across Cloudflare, Route 53, GoDaddy, Namecheap, and 11 others. No per-domain manual step, no DNS error ticket.
  • No admin overhead. The infrastructure is fully managed. Postfix configuration, JVM heap tuning, certificate renewal, and spam filter updates are not an MSP's problem to schedule.

The tradeoff is that Atriomail is a managed platform: you do not own the server, and data sovereignty requirements that demand physical control of hardware are not satisfied here. For the majority of small-business email clients, that is not a requirement anyone has actually stated, and the operational difference is the $415/month cost gap at 50 mailboxes.

Frequently Asked Questions

Can I use Zimbra Open Source to avoid the license cost entirely?

Yes, and some MSPs do. Zimbra Open Source is free to self-host and includes core email, calendar, and contacts. What it does not include is Outlook Connector (MAPI sync), Exchange ActiveSync for mobile devices, or the archiving features. The infrastructure and admin cost of running the stack is identical to the Network Edition: the server, the complex process tree, and the manual DNS per domain all apply. For clients who only use webmail or IMAP-based clients and do not need mobile ActiveSync or native Outlook sync, the open-source edition is a legitimate option. For clients who depend on ActiveSync for their phones, or on Outlook's native calendar sync, it is not.

Does Zimbra publish per-mailbox pricing for the BSP edition?

Not publicly. BSP per-mailbox pricing is negotiated at program enrollment and varies by tier. What is published is the minimum monthly spend floor: $200/month at Authorized, $1,000/month at Silver. Some BSP-authorized Zimbra partners publish retail pricing in the $4-6/mailbox/month range, which gives a reference for what the market-level client charge looks like, but the wholesale rate an MSP pays Zimbra is disclosed through the partner portal, not on the public pricing page.

Does the ModulesGarden Zimbra module handle per-mailbox billing in WHMCS?

Yes, it supports WHMCS Metric Billing for per-mailbox usage tracking, and it handles provisioning, suspension, and termination. What it does not do is replace a native integration: it is a third-party product with its own release cycle, its own support queue, and its own renewal cost. If ModulesGarden discontinues or breaks compatibility with a WHMCS version, the MSP is responsible for the remediation.

What does migrating clients off Zimbra look like?

IMAP migration works well for Zimbra-hosted mailboxes: Zimbra exposes a standard IMAP interface, so any IMAP migration tool (including the free two-way migration built into Atriomail) can pull existing folders and messages and deposit them into a new mailbox. Calendar and contacts migration requires a separate step, typically CalDAV/CardDAV export from Zimbra and import into the new platform. For clients who only used email, the migration is straightforward. For clients who relied on Zimbra's shared calendars or task lists, the migration checklist is longer.

Latest from the blog