Exchange Server SE cost vs OX App Suite

Is Exchange Server SE cost higher than running OX App Suite yourself?

A renewal, a Subscription Edition licensing decision or a Windows Server refresh is probably forcing your cost review, and the honest answer depends on user count, mailbox and file volume, your existing Kubernetes skills and the support model you choose. No supplied figure gives a total for either side, so neither platform can be declared cheaper in general. Exchange Server Subscription Edition reached general availability on July 1, 2025, and Exchange Server 2019 extended support ended in October 2025, so many organizations are now deciding whether to stay on-premises, move to Exchange Online or change platform. Those three paths carry different cost structures, and the comparison only means something when each is priced for the same user population over the same period.

Self-hosting moves cost from licenses to infrastructure, storage, staff time and support. On the Exchange side, price the Subscription Edition or Software Assurance terms for the server and every client access license, the Windows Server hosts and their own licensing, and the work to keep configurations current under the Modern Lifecycle Policy. On the OX App Suite side, price the Kubernetes cluster, the Istio service mesh that the v8 requirements call for, the MariaDB and Redis footprint, and a distributed file system for OX Drive files and PIM attachments, which the requirements place on NFS for small to mid-size deployments or object storage such as S3, Ceph RadosGW or Scality RING for larger ones. Cluster and storage costs recur, while migration and hardening are largely one-time.

Ask each vendor or partner for line items, not totals. For OX App Suite, confirm with Open-Xchange whether the module set you need is covered by your license agreement, since its Operations Guide notes that some modules or features may carry separate fees, and confirm the support commitment and LTS dates before budgeting. Ask for the storage growth assumption behind every quote, and for the staff hours that cover upgrades, backups and on-call duties. A fixed-scope written estimate from DeployOpen follows the same logic: it shows the components, what each one assumes about your estate and what you must provide, so you can compare it with the Exchange renewal line by line.

How each OX App Suite and Exchange Server SE cost component breaks down

This table sets each Exchange Server SE cost component beside its self-hosted OX App Suite counterpart and marks whether it is paid once or recurs. Read it as a checklist for building two comparable quotes, not as a price comparison, because rates and quantities depend on your licensing agreement, hardware and staff.

Cost component	Exchange Server SE (commercial side)	OX App Suite (self-hosted side)	One-time or recurring
Server licensing	Exchange Server SE licence under subscription or Software Assurance	No product licence fee in the open-source core; check the OX licence agreement for modules	Recurring (Exchange); check OX terms
Host operating system	Windows Server hosts for Exchange roles	Linux nodes for the Kubernetes cluster	Recurring (subscriptions or support)
Client access licences	CAL for every user or device accessing the server	None for the open-source core; confirm per-user terms in OX quote	Recurring (Exchange); confirm (OX)
Compute and cluster	Exchange server hardware or virtual machines	Kubernetes cluster, Istio or ingress-nginx, Helm 3.17.0 or newer	One-time build, recurring run
Data services	Exchange database storage on server disks	MariaDB, Redis 7.4.x, NFS or S3-compatible object storage for attachments and Drive files	One-time build, recurring capacity growth
Support and upgrades	Microsoft support, cumulative updates and Extended Security Updates where applicable	Open-Xchange support subscription, LTS upgrade planning and internal patch testing	Recurring
Migration tooling and effort	Export and import work, partner or internal staff	Migration tooling, cutover testing and client configuration	One-time
Internal staff time	Exchange administration, patching and mailbox operations	Kubernetes, database and storage operations plus OX administration	Recurring

What changes in Exchange licensing and in the OX support model

The first change to plan for is that Exchange Server SE has no fixed end date. Microsoft released Exchange Server Subscription Edition to general availability on July 1, 2025, and it follows the Modern Lifecycle Policy, so it stays supported for as long as your configuration stays current. Microsoft also plans no further year-based major versions. In practice, the budget line changes from a periodic upgrade project to an ongoing position: a subscription or Software Assurance arrangement covering the server and every client access license. Ask your Microsoft licensing partner to write down which entitlements apply to your server count, CALs and any Windows Server hosts, and how long those terms run before renewal. This contrasts with the Fixed Lifecycle that Exchange Server 2019 followed. Its extended support ended in October 2025, and Microsoft directs customers to Exchange Server SE or Exchange Online. If you are still on 2019, the cost of staying is no longer a matter of how long you can defer a upgrade. Each month on an unsupported release adds security and compliance risk that your auditors will ask about, so the comparison with OX App Suite should start from the date you intend to move, not the date you would like to upgrade. On the OX side, the App Suite middleware and UI are published as AGPL-3.0 mirrors on GitHub, but the license terms are not the whole story. The OX App Suite Operations Guide states that the right to use certain modules or features may depend on custom packaging, limitations or separate fees set in the license agreement. Before you model cost, get a written list of which modules, connectors and support tiers your agreement covers, including the Exchange ActiveSync connector and any features you need for calendars and delegates. The support model is also time-bound. 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 current LTS is v8.47 (FCS 2026-03-18), and v8.35 is discontinued, so your upgrade cadence and staffing must follow an LTS track or a paid support commitment.

Windows Server hosts or Kubernetes: where the platform cost sits

If you keep Exchange Server SE, the platform cost sits in the Windows Server estate that hosts it. Each Exchange server runs on a supported Windows Server operating system, so the operating system licences, the virtualization layer and the hardware or virtual machines must be sized for mailbox load, the database copies you keep and the maintenance windows you need. Exchange also depends on how the database availability group is designed, because the number of copies, the placement across sites and the witness server all determine how many servers you run and how much capacity sits idle.

Operating system licences: Windows Server is licensed separately from Exchange, and the edition and core count you need depend on your virtualization design. Confirm the current licensing terms with Microsoft or your reseller.
Hosts and virtual machines: Count the hosts, storage, backup capacity and networking for production, test and disaster recovery copies. These are usually the largest recurring infrastructure items.
Database and DAG design: Each database copy consumes storage and I/O. Decide how many copies you need in each site before you size the servers.
Backup agents: Exchange-aware backup software usually carries its own licence and agent cost, and it must be compatible with your Exchange version.
Upgrades and patching: Plan the staff time for cumulative updates and any upgrades to the Exchange Server SE configuration. Exchange Server 2019 extended support ended in October 2025, so confirm whether any legacy servers remain in service.

Ask your Microsoft partner or internal team to list each server role, operating system edition and backup product in one table so the on-premises total can be compared line by line.

Which factors move the Exchange and OX App Suite comparison most

Exchange Server SE and self-hosted OX App Suite have different cost structures, so the same mailbox count can produce very different totals. The cards below name the drivers that shift the comparison most, the direction each one pushes cost, and the question to answer internally before requesting a quote.

Mailbox count and concurrency

Licensing on the Exchange side scales with every user and device connection, while OX App Suite costs scale mainly with the Kubernetes capacity, database sizing and support tier needed for peak concurrent sessions. Cost rises on both sides as users grow, but the slope differs. Ask how many mailboxes are active daily, how many run mobile or Outlook sessions at the same time, and which peak hour sets the sizing.

Data volume and attachment growth

Mail archives, calendar attachments and OX Drive files grow over time and drive storage cost. OX App Suite requires a distributed file system for persistent data: NFS suits small to mid-size deployments, while object storage such as AWS S3, Ceph RadosGW or Scality RING fits larger ones. Ask how much data each user stores today, what the annual growth rate is, and whether storage must be replicated across sites.

Exchange edition and CAL mix

Exchange Server SE is licensed with server subscriptions or Software Assurance and client access licenses per user, so the mix of standard and enterprise editions and the CAL type shapes the recurring bill. Older Exchange 2016 or 2019 installations may also need an upgrade path before their support status changes cost. Ask which edition each server runs, how CALs are assigned today, and which licenses are already paid through an enterprise agreement.

Module and feature needs

Open-Xchange states that certain modules or features may be subject to custom packaging, limitations or separate fees in the license agreement. Features that teams treat as standard, such as specific mobile connectors or add-on modules, can therefore move the OX total. Ask which features are required on day one, which are nice to have, and get each one named in the written quote.

Availability and multi-site requirements

High availability on Exchange usually means additional servers, database availability groups and licensing for each node, while OX App Suite high availability depends on Kubernetes node counts, a clustered MariaDB setup such as Galera and replicated storage. Multi-site designs add network, storage replication and failover testing effort on either platform. Ask what recovery time and recovery point the business needs and how many sites must stay live during an outage.

In-house Kubernetes and database skills

OX App Suite v8 runs on Kubernetes, uses Istio or ingress-nginx, and relies on Redis and MariaDB, so the operating skills move from Windows administration to platform engineering. Teams without that experience pay for training, managed support or an implementation partner, while teams that already run these stacks may lower the total. Ask who will patch the cluster, own database backups and handle upgrades, and whether that work is already staffed.

How to build your own cost model before asking for quotes

This sequence turns a vague renewal or licensing concern into a spreadsheet of mailboxes, licenses, hosts and target components that you can price against written quotes. The output is a three-year comparison you can defend in front of finance and the people who will run the platform.

Inventory mailboxes, archives and shared objects
Export a list of user mailboxes, archive mailboxes, shared mailboxes, room and equipment resource calendars, and distribution groups from your Exchange environment. Your Exchange administrators can produce this from the Exchange management tools, and your identity team should confirm which accounts are active, disabled or service accounts. Count each object type separately, because shared mailboxes and resource calendars often carry no user license but still consume storage and migration effort. The step is done when every count ties back to a named source report that someone else on the team can rerun.
Measure current data volume and growth
Record total mailbox size, archive size and the monthly growth rate for the last 12 months, using the same reporting method for each. Note how much of the volume sits in attachments, since attachments drive storage sizing for OX App Suite, where PIM attachments live on a distributed file system. Ask your storage team how backups and replicas multiply the raw figure, because those copies are a recurring cost on either platform. The step is done when you have a current volume, a growth rate and a clear statement of the period it covers.
List every Exchange license line and Windows Server host
Gather every current invoice, agreement and contract line that touches Exchange, including server licenses, client access licenses, any Software Assurance or subscription terms, extended support or upgrade costs, and the Windows Server operating system licenses under the hosts that run Exchange. Include the hardware, virtualization, load balancers, archiving or journaling tools and backup agents that exist only to support the mail platform. Confirm with your licensing partner which terms renew and on what dates, because the Exchange Server SE licensing model differs from earlier perpetual versions. The step is done when each line has a cost, a renewal date and an owner.
Define the target OX architecture
Write down the components a self-hosted OX App Suite deployment needs in your environment: the Kubernetes cluster and its node sizing, the Helm 3 tooling, the service mesh or ingress choice, Redis for caching and sessions, MariaDB as the primary data store, and the distributed file system or object storage for attachments and drive files. Note whether you will run Galera Cluster and which MariaDB version line you plan to use, since those choices change the operational workload. Ask your platform team and the vendor which Kubernetes and Istio versions are supported before you commit. The step is done when a one-page diagram lists each component, who will operate it and where it runs.
Request written quotes for the support, implementation and migration scope
Send the architecture and inventory from the previous steps to Open-Xchange and to any implementation partner you are considering, and ask each for a written quote with separate lines for the support subscription, the software or license terms, implementation, migration of mailboxes and calendars, and training. Ask what the subscription covers, which release tracks it includes and how long each release is supported, and whether any modules carry separate fees under the license agreement. Ask the implementation partner what the scope excludes, such as directory integration or client rollout. The step is done when every quoted figure is in writing, dated and tied to a defined scope.
Run a three-year comparison and staff hours
Build one table per platform with three columns for one-time costs, recurring annual costs and internal staff hours, then total each across three years. One-time costs include migration, implementation and hardware purchases, while recurring costs include licenses, subscriptions, cloud or data center capacity, backup storage and upgrades. Estimate internal staff hours for administration, upgrades, incident response and client support, and state the basis for each figure. Test how the totals change if your mailbox growth or user count moves up or down. The step is done when the comparison shows both totals, the assumptions behind them and the figures that would change the result.
Label sources and keep the model editable
Keep the model in a spreadsheet that others can open, change and recalculate, with one tab for inputs, one for calculations and one for assumptions. Mark every figure with its source: a vendor quote with its date and reference, an invoice, a measured value from your environment, or an internal estimate with the person who made it. Review the model with finance and your security and compliance leads before you request final commitments, and update it when quotes change. The step is done when a reviewer can trace each total to a source and see which figures still need confirmation.

Costs teams forget on each side of the comparison

Licence line items are only part of the comparison. The costs below sit on both sides, often outside the original budget, and they tend to surface during renewal, audit or cutover. Check each one against your own environment before comparing totals.

eDiscovery export licensing

Exporting mailbox items as PST or .msg files through Microsoft Purview eDiscovery requires a Microsoft 365 E3 or E5 license. Legal hold, litigation and records requests often trigger exports that the Exchange Server budget never covered. Ask your Microsoft account team which license tier your export roles need, and price that tier into the Exchange side of the model if you rely on eDiscovery for exports.

Search export expiry

Search export packages expire 14 days after creation, so a download that slips past that window must be rerun. Repeat exports add labor for legal and compliance staff and can recreate the same licensing question. Build the download, verification and hand-off steps into your retention process, and record who approved each export.

Outlook and mobile client licensing

Exchange CALs and Outlook client access are often counted separately from the server line, and mobile access adds its own licensing questions. Confirm with Microsoft which client access licenses each user class needs under your agreement, including shared mailboxes and devices. On the OX side, plan time to test the Outlook client options you intend to keep, since those choices change which users need which connector.

Kubernetes and Istio operator upkeep

OX App Suite v8 runs on Kubernetes through Helm charts and requires Istio, with ingress-nginx as a basic option where Istio cannot be used. Someone must own cluster upgrades, Istio version moves and operator changes, and those tasks recur with every platform release. Ask whether your team has in-house capacity for this stack or whether it needs a retainer for ongoing operations.

Redis and MariaDB restore testing

OX App Suite stores data in MariaDB with InnoDB and uses Redis 7.4.x for caching and session storage. A backup that has never been restored is not a recovery plan, and Galera or Redis failover setups need their own test cases. Budget for periodic restore drills that cover both databases together, and record the recovery time you actually measure.

Storage growth and upgrade rehearsal

Persistent OX Drive files and PIM attachments must sit on NFS or object storage such as S3, Ceph RadosGW or Scality RING, and that volume grows with every user. Each standard release is supported for 12 weeks, so staying current means rehearsing upgrades on a staging copy in each cycle. Ask Open-Xchange which release line your contract covers, and size storage growth from your own mailbox data rather than a generic estimate.

How migration effort adds to the first-year cost

Migration is usually the largest one-time item in the first year, and its size depends on the export method, mailbox count, how many users rely on archive mailboxes and how complex the calendars are. Shared calendars, delegates, resource mailboxes and recurring meetings with exceptions take more mapping and testing than plain inbox mail. Before any quote, ask the implementation partner which export method they will use for each data type and how each one is validated after import. Those answers are the main levers on effort. If your team uses Microsoft Purview eDiscovery to pull mailbox items out of Exchange, confirm your licensing first. The researched facts state that exporting requires a Microsoft 365 E3 or E5 license, and that exports can be saved as PST or .msg files. Search export packages expire 14 days after creation, so a large export has to be scheduled, downloaded and checked inside that window. Plan a retry path for packages that expire before transfer. Ask your Microsoft account team to confirm which of your current licenses cover this, because the answer changes whether the export cost is a new line item.

Ask the implementation partner for a fixed scope that lists export, import, coexistence during cutover, Outlook client testing and rollback as separate deliverables with acceptance criteria for each. Coexistence needs its own line, because mail routing, free/busy lookups and calendar visibility between the old and new systems have to work during the transition. Rollback needs a named trigger and a tested procedure. The written scope drives the quote, so a vague scope usually returns a vague price and open-ended change requests later. Exchange Server SE and OX App Suite will run in parallel during cutover, and that overlap adds running cost. You pay for the Exchange licenses and servers until the last mailbox moves, and for the OX platform, storage and support from the first day of deployment. Ask the partner to state how long each user group stays on both systems and who pays for the extra capacity during that period. Shortening the overlap usually lowers the first-year total more than negotiating any single line item.

Questions buyers ask about self-hosted OX App Suite cost and effort

How much does OX App Suite cost to run compared with Exchange Server SE?

No total cost figure is supplied here, and a fair comparison depends on your own user count, hardware and staff. Exchange Server SE costs are driven by Windows Server host licensing, Client Access Licenses for every user and the subscription or Software Assurance terms that now apply to servers and CALs. OX App Suite costs are driven by the Kubernetes cluster, Istio, MariaDB, the distributed file system for OX Drive files and PIM attachments (NFS for small to mid-size deployments, or object storage such as AWS S3, Ceph RadosGW or Scality RING for larger ones), backups, staff time and any Open-Xchange support subscription. Ask Open-Xchange for a written list of licensed modules, and ask for quotes that separate one-time migration work from recurring infrastructure, support and operations.

How long does a migration to OX App Suite take?

The duration depends on scope and data volume, and no fixed timeline is supplied here. The main factors are the number of mailboxes, the size of mail stores and attachments, how many calendars, contacts and shared resources need to move, the number of clients and devices to reconfigure, and how many change windows your organization allows. Plan a coexistence period in which mail still flows between old and new systems. Ask any implementation partner for a written schedule tied to a defined scope, and confirm which phases (pilot, bulk migration, cutover and rollback) are included.

Can our own team run OX App Suite without outside help?

Yes, many teams can, but only if they already operate the underlying platforms. OX App Suite v8 is delivered as Helm charts and requires Helm 3.17.0 or newer, so you need Kubernetes operations skills for upgrades within the supported N-1 and N-2 versions. Istio is required, with ingress-nginx as a basic option where Istio cannot be used. The stack also needs MariaDB administration (InnoDB, Galera Cluster if clustered), Redis 7.4.x operations, distributed storage administration and mail operations such as Dovecot, SMTP relay, anti-spam and client support. Assess these skills honestly, and consider a fixed-scope engagement for the initial build and handover.

What does a self-hosted groupware project need from our organization?

The project needs decisions, access, change windows and staff time. Decisions include the target architecture, storage type, identity integration, retention rules and which users move first. You will need access to the cloud accounts or data centers where the platform runs, directory and identity administrators for authentication, and mail administrators who understand current mail flow and DNS. Schedule change windows for cutover and rollback, and assign a named owner for testing, user communication and helpdesk readiness. Ask your provider to list these dependencies in the written scope so each one has an owner and a date.

Do we need a paid support subscription for OX App Suite?

Open-Xchange's support commitment defines how long each release is supported, so your choice of release drives your support exposure. 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 current LTS named in the commitment is v8.47 (FCS 2026-03-18), and v8.35 is discontinued. Whether you need a paid subscription depends on your risk tolerance and staff capacity. Confirm in the agreement which releases receive fixes, the response channels, the upgrade path between LTS versions and whether security patches are included.

What if our license agreement includes module fees for OX App Suite?

Ask for the full list of included features in writing before you sign. 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. Request a feature-by-feature statement covering mail, calendar, contacts, drive, documents, tasks, ActiveSync or other connectors, and administrative tooling you plan to use. Compare that list with your requirements, and ask how fees change if your user count grows or if you add modules later. Keep the statement with the contract so the scope you priced is the scope you receive.

How DeployOpen works on this

DeployOpen plans, implements, integrates, hardens, backs up and documents self-hosted open-source platforms inside your own cloud accounts, data centers or air-gapped networks. For an Exchange Server SE cost comparison, we start by turning your current licensing and hosting figures into a written scope that a quote can follow.

How we scope

We inventory current Exchange licensing, Windows Server hosts, CAL counts and any archive or compliance tooling before estimating the change.
The written scope lists the OX App Suite components, Kubernetes platform, storage, database and integrations that will be delivered.
Engagements are fixed-scope, so deliverables, timelines and responsibilities are agreed in writing before any work starts.

How we build

We deploy OX App Suite v8 from Helm charts onto your Kubernetes cluster, with Istio or ingress-nginx chosen to match your standards.
We configure MariaDB, Redis, and a distributed file system such as NFS or S3-compatible object storage sized to your mailbox and file volumes.
We test directory login, mail flow, calendar sharing and client connections, then document the results for your reviewers.

How we hand over

We deliver runbooks for installation, upgrades, backup and restore, and the Redis, MariaDB and storage components.
We prepare the controls and evidence your compliance team will need for an assessment, without issuing any audit opinion ourselves.
Knowledge transfer sessions walk your platform and operations staff through the environment before the engagement closes.

How we support

Ongoing support, upgrades and continuous security testing are available as retainers after the fixed-scope work ends.
We can plan upgrades against the Open-Xchange support commitment, so your LTS release path stays inside its supported window.
Ask any implementation partner to confirm how support, upgrade effort and Open-Xchange subscription fees are split in the quote.

Exchange Server SE cost vs self-hosted OX App Suite