OX App Suite vs IceWarp

Deployment Flexibility: Cloud, On-Prem, or Both at Once

Deployment flexibility is the single biggest differentiator in this comparison, since both products explicitly market themselves against pure cloud-only competitors rather than directly against each other’s deployment models.

Why Deployment Model Is the Real Decision Point Here

Buyers evaluating OX App Suite against IceWarp are rarely comparing feature checklists first; they’re comparing where the mail server itself is allowed to sit, because a compliance team, a data-residency clause, or a hardware investment already made the call before pricing entered the conversation. OX App Suite’s middleware ships with different optional adapters to support object storage and for single-node setups.

A local file system mount point can be used. In contrast, small-to-mid-scale setups can be powered by NFS, with object storage recommended for large-scale deployments; that range, from local disk to distributed object storage, is what lets a reseller-hosted instance and a fully self-managed instance run the same middleware. IceWarp’s hybrid deployment model instead runs an on-premises server core for data storage, email, calendars, contacts, and chat history, alongside cloud-based microservices for processing and user interfaces, treating the hybrid as two cooperating servers rather than a single architecture with a choice of storage backend.

Where Each Model Breaks Down in Practice

A hybrid setup that spans two mail systems introduces coordination overhead that an admin team must own indefinitely, not just during a migration window; routing rules, shared calendars, and directory sync all need to keep working across both platforms every day the hybrid state persists.

OX App Suite’s single-middleware approach avoids that dual-system coordination burden, but it shifts the decision earlier: an organization has to pick its storage backend (local, NFS, or object storage) up front based on projected mailbox count, since Open-Xchange does not plan to support MySQL 8 or higher and is standardizing future releases on MariaDB. For a buyer who already knows they want full control and isn’t running a parallel legacy system, that upfront decision is simpler to reason about than an ongoing dual-system setup, while a buyer actively mid-transition off Microsoft 365 and wanting to preserve email history without a hard cutover is exactly who IceWarp’s hybrid design targets instead.

Where the Data Lives: Sovereignty and Self-Hosting Trade-offs

Data sovereignty is the specific angle that separates this comparison from OX App Suite’s other battlecards, since IceWarp is the rare competitor genuinely built for on-prem control rather than cloud-first with an on-prem afterthought.

What Self-Hosting Actually Buys a Compliance Team

A compliance officer asking “can we prove exactly which jurisdiction our mail data sits in” needs an architecture answer, not a policy answer, and OX App Suite’s persistent data, OX Drive files, PIM attachments, and temporary attachment data, needs to be stored in a distributed file system registered as a file store that’s available from all server nodes, meaning a fully self-hosted instance can keep every byte of that store inside a customer-controlled data center with no vendor-operated component in the path: nothing routes through Open-Xchange’s own infrastructure in a self-hosted deployment.

IceWarp’s cloud tier, by contrast, runs in vendor-selected data centers rather than customer-controlled ones for organizations that don’t opt into self-hosting. Hence, the sovereignty conversation applies only to IceWarp’s self-hosted or hybrid tiers. Even IceWarp’s hybrid deployments, which combine an on-premises server core for data storage with cloud-based microservices for processing and interface delivery, still route some processing through cloud components.

The Honest Limitation on Both Sides

Neither vendor publishes a single unified data-residency certification that covers every deployment mode uniformly; self-hosting shifts the compliance burden onto the customer’s own infrastructure team rather than eliminating it, and that’s true whether the customer picks OX App Suite or IceWarp’s on-prem tier.

Where OX App Suite has a real gap: because Hiya Digital resells and implements the platform rather than operating its own data centers for it, a customer choosing self-hosted OX App Suite through a reseller still needs its own infrastructure or a hosting partner to run the Kubernetes cluster the platform now depends on, not a weakness unique to OX App Suite, but not free of setup work either. IceWarp has a comparable gap on the other side: its SOC 2, GDPR, and ISO/IEC 27001 certifications are documented, but a HIPAA Business Associate Agreement is not publicly confirmed, so a healthcare buyer needing a signed BAA should verify that directly with IceWarp rather than assuming cloud-tier compliance parity with a HIPAA-focused competitor.

Collaboration Beyond the Inbox

Both products are positioned as full collaboration suites rather than pure mail servers, which is worth confirming directly since a buyer coming from a mailbox-only competitor might assume otherwise.

What Ships Inside the Core Suite

Neither platform treats email as a standalone product anymore; the comparison that matters is which collaboration modules ship natively versus which require a separate add-on or third-party integration to reach parity, and OX App Suite encompasses cloud storage, document editing, email, and calendar management through a modular approach that provides core functionality via its various components. OX Drive specifically provides file and folder synchronization across multiple devices, optimized for each device type, with quota control and upload-limit management built into the sync layer. At the same time, OX Documents is delivered as a fully integrated office suite covering document, presentation, and spreadsheet editing within the same interface as mail and calendar.

IceWarp positions itself as an all-in-one collaboration platform bringing email, messaging, video conferencing, file sharing, and real-time document collaboration together in a single interface, with its WebClient centralizing email, chat, calls, contacts, calendars, tasks, files, and journals without switching between tabs. IceWarp’s Business tier specifically bundles integrated TeamChat, video conferencing supporting up to 1,000 attendees, and document co-authoring.

Where the Depth Actually Differs

The genuine difference isn’t presence versus absence of collaboration tools on either side; both ship real ones. It’s about how deeply each module is built out and how much configuration a modular architecture demands, compared to a unified client that delivers everything by default. OX App Suite’s modular structure means an implementation partner can enable exactly the components a customer needs, email plus calendar without the full document suite, for example, which suits organizations that want a lean deployment rather than every module running by default.

It lets Hiya Digital scope a rollout to what a business actually uses. IceWarp’s video conferencing capacity for up to 1,000 attendees, by contrast, is a specific, citable capability OX App Suite’s core suite doesn’t natively match at the same scale, a fair point in IceWarp’s favor for large all-hands meetings. However, for most day-to-day collaboration outside of broadcast-style meetings, the two platforms cover comparable ground.

Locking Down Access: Security and Encryption Controls

Security architecture is where a self-hosted or hybrid competitor set must be evaluated differently from a pure SaaS comparison, since the customer’s own infrastructure choices directly affect the security posture that either platform can deliver.

Encryption and Access Control Built Into Each Platform

The question that matters here isn’t “does this platform support encryption”; both do. It’s which layer the encryption lives at. OX Guard is a fully integrated security add-on to OX App Suite that provides end users with a flexible email and file encryption solution. Encryption is available as a native module rather than a bolted-on third-party tool, simplifying key management for an admin team that wants it in the same console as mail administration. Because OX App Suite is commonly self-hosted, the customer’s infrastructure team also controls TLS termination, database encryption at rest, and network segmentation directly rather than trusting a shared multi-tenant cloud boundary.

IceWarp is documented as SOC 2 and GDPR compliant and ISO/IEC 27001 certified, third-party-audited standards covering organizational security controls rather than a single product feature, a genuine, citable advantage for a buyer whose procurement process specifically requires vendor certification evidence rather than architecture claims alone.

The Fair Trade-off Neither Side Should Overstate

Certifications and native encryption modules answer different buyer questions. Neither platform’s approach is strictly superior. A procurement team asking “show me your SOC 2 report” gets a faster answer from IceWarp’s published certifications, while a technical team asking “can we control the encryption keys ourselves” gets a more direct answer from OX Guard’s self-hosted model.

It would be an overstatement to claim OX App Suite is more secure simply because it’s self-hostable, since self-hosting only improves security posture if the customer’s own team actually configures it correctly, and equally unfair to claim IceWarp’s certifications make OX App Suite’s encryption approach inadequate, since OX Guard addresses message-level confidentiality. In contrast, SOC 2 addresses organizational control maturity and two different threat models. Buyers with a hard compliance-audit requirement should weight IceWarp’s certification set more heavily; buyers who need direct key custody should weight OX Guard’s native encryption model more heavily.

Feature-by-Feature Comparison

Moving Mailboxes: Migration Friction in Both Directions

Migration is where most switching decisions are actually made or abandoned, since a technically superior platform that’s painful to migrate to loses to an adequate platform with a smooth onboarding path more often than buyers expect.

What a Move Into Each Platform Actually Involves

Every migration to a new mail platform must move the same four things: messages, calendars, contacts, and folder structure, but the available tooling and who operates it differ between a reseller-supported rollout and a vendor-published tool list. IceWarp publishes migration tools specifically for moving from Exchange, Microsoft 365, Google Workspace, and Zimbra, covering the most common incumbent platforms a buyer is likely migrating away from, a legitimate, citable strength, since a buyer coming from Zimbra, for instance, has documented tooling rather than a generic IMAP-migration workaround.

Moving into OX App Suite through Hiya Digital as an Authorized Reseller and Implementation & Migration Partner adds a layer IceWarp’s self-serve tool list doesn’t include by default: a migration project actually staffed and managed by people who’ve run the cutover before, rather than software the customer’s own IT team has to operate unassisted. For a business without a dedicated migration engineer on staff, that difference in who’s driving the migration is often the deciding factor.

Migration Friction Going the Other Direction

Migration friction isn’t only about what pulls a buyer in; it’s also worth being honest about what happens if a business later needs to move off either platform, since lock-in risk is a legitimate part of any switching decision.

OX App Suite’s use of standard protocols and modular data stores means that exported mail and calendar data generally follow common formats. Still, a self-hosted deployment’s specific configuration (object storage backend, custom domain routing) can make a later export more involved than a pure cloud mailbox would be, a real limitation worth naming rather than glossing over. IceWarp’s own migration tooling is similarly built to pull data in from other platforms more than to push data out, which is typical of the category rather than an IceWarp-specific weakness, but buyers drawn to IceWarp’s hybrid “keep your options open” pitch should confirm export tooling before assuming symmetry with the import side, just as an OX App Suite buyer should confirm export planning with their implementation partner up front.

Running the Show: Admin Controls and Day-to-Day Management

Admin experience rarely shows up in a feature comparison chart. Still, it’s what an IT lead actually lives inside every day once the migration is finished and the platform is in production use.

The Console an Admin Actually Opens Every Day

The real test of an admin console isn’t whether it can do something in theory; it’s how many clicks and how much documentation reading it takes to do the routine tasks an admin repeats weekly. IceWarp’s WebAdmin is built for basic server management using responsive web design so pages adapt to the device being used, with functionality for resetting an expired account, changing limits or permissions, and managing client applications, plus a dashboard giving immediate visibility into server activity such as emails sent and total storage utilized, a genuinely convenient single-pane view for a smaller IT team without a dedicated messaging specialist on staff.

OX App Suite’s middleware integrates with pre-existing infrastructure, including authentication, provisioning, and billing systems. It exposes Java RMI and SOAP APIs for user creation and modification, as well as command-line provisioning tools. That API-first design is more powerful for an organization that wants to fold mailbox provisioning into an existing internal system. Still, it assumes the implementation team building that integration knows what they’re doing.

Who the Admin Experience Actually Suits

IceWarp’s WebAdmin is the better fit for a lean IT team that wants a single, self-contained console with visible day-to-day metrics and doesn’t need to wire the mail platform into a separate internal billing or provisioning system.

OX App Suite’s API-driven provisioning is the better fit for a larger organization, or a reseller managing many customer tenants, that wants mailbox creation and permission changes to happen automatically through an existing system rather than manually through a web console every time, precisely the model Hiya Digital operates on behalf of its OX App Suite customers, with provisioning handled through the reseller relationship rather than left entirely to the end customer’s own admin time. Neither approach is objectively better in isolation; a five-person company and a two-hundred-mailbox reseller-managed deployment have different admin needs.

Scaling Past a Few Hundred Mailboxes

Scalability questions surface differently depending on whether growth means more mailboxes on the same platform or a platform that needs re-architecting as the mailbox count climbs.

How Each Platform Handles Growing Mailbox Counts

A platform that works cleanly for fifty mailboxes doesn’t automatically work the same way at five thousand, and the architecture each vendor built for scale tells you what growth looks like operationally. Open-Xchange publishes separate deployment tutorials for up to 10,000 users and for up to 100,000 users. The current OX App Suite Software Subscription generation has been containerized for use in a Kubernetes cluster, built specifically for horizontal scaling as mailbox counts grow, which matters most to a reseller or larger enterprise adding mailboxes in batches rather than one at a time.

IceWarp’s cloud-hosted deployment instead scales through managed services without requiring on-premises infrastructure, with cloud deployments hosted in user-selected data centers to help meet compliance requirements as an organization grows. For a business that wants scale handled entirely by the vendor’s cloud, the managed-scaling model removes a layer of operational responsibility, leaving OX App Suite’s self-hosted path with the customer.

The Trade-off Between Managed Scale and Owned Scale

The honest comparison here isn’t which platform scales further; both are proven at meaningful mailbox counts. It’s who does the scaling work as the organization grows.

OX App Suite’s Kubernetes-based scaling gives a technically capable team, or a reseller like Hiya Digital managing infrastructure on the customer’s behalf, direct control over how resources get added as mailbox counts climb, valuable for predictable performance at scale but requiring someone competent operating that cluster. IceWarp’s cloud-managed scaling removes that operational burden entirely for a customer on its cloud tier, a legitimately lower-friction path for a growing business without in-house infrastructure expertise, while a business planning to scale into the thousands of mailboxes with a reseller actively managing the deployment gets a more explicitly documented path from OX App Suite’s published tutorials.

Working From a Phone: Mobile and Cross-Device Access

Mobile access is table stakes for both platforms at this point, so the comparison worth making is about depth of the mobile experience rather than presence or absence of a mobile app.

What Mobile Access Looks Like on Each Platform

Almost every buyer in this comparison is going to check email on a phone before a desktop, which makes mobile sync quality a more practical factor than it gets credit for. OX Drive is accessible via OX App Suite directly or downloadable to a smartphone, tablet, laptop, or desktop PC, with the sync layer designed to adapt to each device type’s specific limitations such as battery life, screen size, and bandwidth, meaning a phone client isn’t just a shrunk-down desktop interface but is built to behave differently on a constrained connection.

IceWarp’s plans include mobile synchronization for iOS and Android as a standard feature across its cloud tiers, and it also offers a desktop client for Windows and macOS, providing native coverage across desktop operating systems.

Where Cross-Device Experience Actually Diverges

The meaningful difference isn’t whether either platform syncs to a phone; both do. It’s how much configuration a self-hosted OX App Suite deployment needs before mobile sync performs as smoothly as IceWarp’s more turnkey mobile setup.

Because OX Drive’s device adaptation is built into the middleware itself, a properly configured self-hosted OX App Suite instance delivers a comparably native-feeling mobile experience; a reseller-managed deployment through Hiya Digital handles that configuration as part of implementation. In contrast, a fully self-managed deployment leaves that tuning to the customer’s own team. IceWarp’s mobile sync, bundled consistently across its cloud tiers with native desktop clients on both major operating systems, requires less deployment-specific tuning to reach a solid baseline out of the box, a fair, specific point in IceWarp’s favor for a buyer who wants mobile access working well on day one without an implementation partner tuning the sync layer first.

Who Answers When Something Breaks: Support Models Compared

Support structure is the part of a battlecard that’s easiest to overlook until the first outage or misconfigured DNS record, at which point it becomes the only thing that matters.

The Support Path for Each Platform

The question a buyer actually needs answered isn’t “does this vendor offer support”; it’s “when my mail server goes down at 6 pm on a Friday, who do I call, and what’s their relationship to the software itself?” IceWarp’s support model is vendor-direct: a 30-day free trial with full feature access gives a buyer a chance to test IceWarp’s support responsiveness before committing, and support tickets for both cloud and self-hosted deployments route back to IceWarp’s team, since it’s the platform’s original developer.

OX App Suite’s support path through Hiya Digital works differently, as an Authorized Reseller, Implementation & Migration Partner, and Licensing & Support Partner, Hiya Digital sits between the customer and the underlying Open-Xchange middleware, so day-to-day support questions get answered by a partner who already knows the customer’s specific deployment rather than a general support queue.

Which Support Model Actually Serves Which Buyer

Vendor-direct support suits a buyer who wants a single point of accountability tied directly to the software vendor and is comfortable navigating a general support process for their specific configuration questions.

Reseller-based support suits a buyer who wants a support contact already familiar with their specific setup, their domain configuration, their migration history, and their user counts, rather than re-explaining context to a new agent each time, which is the structural advantage Hiya Digital’s Licensing & Support Partner role provides: continuity of context across every interaction. Neither model is universally better; a large enterprise with its own internal messaging team may prefer direct vendor escalation paths. In contrast, a small- to mid-sized business without dedicated messaging staff generally gets more value from a partner who already knows its environment.

Pricing & Plan-Structure Comparison

Counting the Real Costs: Contracts, Add-Ons, and Seat Minimums

Sticker price aside, the structural shape of a pricing model, contract length, seat minimums, what’s bundled versus billed separately, often matters more to total cost than the headline tier name.

How the Two Pricing Structures Are Actually Built

Looking past the tier names themselves, the real cost driver in either platform is what’s bundled into the base tier versus what becomes a separate add-on as needs grow. IceWarp structures its plans around a Core tier, an Essential tier, and a Business tier, with email and total storage allowances increasing at each tier, and both annual and other subscription-term options available, plus cloud and self-hosted deployment options, all available directly with a 30-day free trial before committing to any tier.

OX App Suite through Hiya Digital is structured around named plan tiers reflecting what’s included at each level, mailbox storage allowance, OX Drive quota, and which collaboration modules (Documents, Guard encryption) are bundled versus optional, with contract-term and seat-minimum terms set through the reseller relationship rather than a single global self-serve checkout.

What Actually Drives Total Cost Over Time

The structural detail that matters more than either tier name is what happens as an organization adds seats or needs additional modules mid-contract, since that’s when a pricing structure’s real shape shows up.

IceWarp’s tiered storage allowances mean an organization needing more per-user storage has to move to a higher named tier rather than buying storage as an isolated add-on, simple to reason about. Still, it can mean paying for other tier-level features an organization doesn’t need to get more storage, with a fixed upfront commitment length rather than an adjustable seat-by-seat one. OX App Suite’s modular architecture, by contrast, generally allows specific components- encryption, document editing, extra storage- to be scoped independently rather than forcing an all-or-nothing tier upgrade, and through Hiya Digital, seat minimums and contract terms are negotiated as part of the reseller relationship, giving a growing business more room to adjust its commitment than a fixed self-serve annual tier typically allows.

Decision-Summary Table

Frequently Asked Questions

Can OX App Suite and IceWarp both run fully on-premises with no cloud component?

Yes, both support fully self-hosted deployment rather than requiring a cloud tier. OX App Suite’s middleware supports a local file system mount point for single-node setups and scales to NFS or object storage as mailbox counts grow, so a small deployment doesn’t need distributed storage infrastructure to get started. IceWarp likewise offers self-hosted deployment as a standard option alongside its cloud tiers, and its hybrid model specifically runs an on-premises server core for storage. The practical difference shows up in scale: OX App Suite publishes deployment guidance up to 100,000 users for large self-hosted rollouts, which is a specific figure worth confirming still fits a given organization’s growth plans before committing to either self-hosted path.

Does IceWarp’s hybrid deployment require migrating every mailbox at once?

No, that’s the specific design goal of IceWarp’s hybrid model. It runs IceWarp alongside an organization’s existing mail server within a single domain, allowing mailboxes to migrate gradually rather than in a single cutover event. At the same time, both systems appear as a single system to anyone emailing the company from outside. This suits an organization concerned about disruption due to a hard migration deadline. The trade-off is that both systems have to be administered in parallel for as long as the hybrid state persists, which adds ongoing coordination work that an admin team should plan staffing for, rather than treating it as a short-term transition step.

What happens to mailbox data if we later need to move off OX App Suite?

OX App Suite’s standard protocol support means mail and calendar data generally exports in common formats. Still, the specifics depend on how a given deployment was configured, particularly which object storage backend was used for OX Drive and attachment data. A self-hosted deployment with a customized storage backend may require more export planning than a straightforward cloud mailbox. Buyers planning for this scenario should confirm export tooling and format compatibility with their implementation partner before finalizing the initial deployment configuration, rather than assuming a uniform export path applies regardless of how the backend was set up.

Is IceWarp’s SOC 2 and ISO/IEC 27001 certification enough for a HIPAA-regulated business?

Not on its own. IceWarp is documented as SOC 2 and GDPR compliant with ISO/IEC 27001 certification, which covers organizational security control maturity. Still, a signed HIPAA Business Associate Agreement is not publicly confirmed as part of that certification set. A healthcare organization with HIPAA obligations should request written BAA confirmation directly from IceWarp rather than assuming its existing certifications automatically extend to HIPAA coverage, since these are separate compliance frameworks that don’t imply one another, even when a vendor holds strong marks in each area.

Does OX App Suite include video conferencing at the same scale as IceWarp?

Not natively at the same documented scale. IceWarp’s Business tier specifically supports video conferencing for up to 1,000 attendees, which is a citable capacity figure for large all-hands or webinar-style meetings. OX App Suite’s core suite is built around cloud storage, document editing, email, and calendar management as its primary modules, without the same large-attendee conferencing capacity documented in its published materials. An organization whose primary requirement is large-scale video conferencing should weigh that specific gap heavily, since it’s a genuine, sourced difference rather than a minor feature nuance.

How does OX Guard encryption compare to IceWarp’s security approach?

OX Guard is a native, integrated add-on to OX App Suite that provides email and file encryption directly within the platform’s console, meaning key management sits within the same administrative environment as mailbox management. IceWarp’s documented security posture centers on third-party audited certifications, including SOC 2, GDPR, and ISO/IEC 27001, which cover organizational controls rather than a single named encryption module. These answer different buyer needs: a team wanting direct control over message-level encryption keys gets a more direct answer from OX Guard. In contrast, a procurement process that requires audited certification evidence receives a faster response from IceWarp’s published certification set.

Which platform has documented migration tools for moving off Google Workspace?

IceWarp publishes migration tooling specifically covering moves from Google Workspace, alongside Exchange, Microsoft 365, and Zimbra, giving a Workspace-departing buyer named tool support rather than a generic IMAP workaround. Moving from Google Workspace to OX App Suite is more commonly handled as a reseller-managed migration project through an Implementation & Migration Partner like Hiya Digital, where a migration team plans and executes the cutover directly, rather than the customer using a self-serve tool. Both paths can move the same underlying data, messages, calendar, and contacts; the difference is whether tooling or a managed team drives the process.

Can a growing business add OX Guard encryption or extra storage without upgrading its entire plan?

Generally, yes, OX App Suite’s modular architecture is designed so that components like Guard encryption, OX Documents, and additional storage can typically be scoped and added independently, rather than requiring a full tier upgrade to unlock a single feature. This suits an organization where only some users need advanced encryption or heavier storage allowances. IceWarp’s tiered structure works differently: moving to a higher named tier (for example, from Essential to Business) is generally required to unlock a higher storage allowance, since storage scales by tier rather than as an isolated add-on in IceWarp’s published plan structure.

Does either platform support mobile access without a separate app download?

Both support browser-based access without requiring an app install, though native apps are also available on both platforms for a fuller offline-capable experience. IceWarp’s WebClient is built to centralize email, chat, calls, contacts, calendars, tasks, and files in a single browser-accessible interface, eliminating the need to switch between separate tabs. OX App Suite’s OX Drive component is similarly accessible directly through the browser-based App Suite interface, with dedicated apps available for phone, tablet, and desktop for users who want app-specific features like offline sync and push notifications rather than browser-only access.

Who provides support if something breaks in a self-hosted OX App Suite deployment managed through Hiya Digital?

Support routes through Hiya Digital as the Authorized Reseller and Licensing & Support Partner rather than requiring the customer to open a ticket directly with the underlying middleware vendor for routine issues. This matters in practice because a support contact already familiar with a specific deployment’s configuration, storage backend, migration history, and module setup can typically resolve an issue faster than a general support queue that has to gather that context from scratch on every new ticket. For infrastructure-level failures outside the reseller’s scope, escalation paths are defined in the initial Support Partner agreement.

Glossary

Hybrid deployment: An architecture where a mail platform runs alongside an existing mail server on the same domain, allowing gradual migration rather than a single cutover event.

OX Guard: OX App Suite’s integrated email and file encryption add-on, managed within the same administrative console as mailbox and calendar management.

OX Drive: OX App Suite’s native cloud storage and file-synchronization component, built with device-specific adaptation for phones, tablets, and desktops.

Object storage: A storage architecture used for large-scale OX App Suite deployments to hold persistent data such as attachments and OX Drive files across multiple server nodes.

WebAdmin: IceWarp’s browser-based server management console, used for account resets, permission changes, and monitoring server activity such as storage utilization.

SOC 2: A third-party audit standard evaluating an organization’s security, availability, and confidentiality controls, distinct from a product feature.

ISO/IEC 27001: An international standard for information security management systems, used as a certification benchmark independent of any single vendor’s platform architecture.

Business Associate Agreement (BAA): A signed agreement required under HIPAA between a healthcare organization and a vendor handling protected health information, separate from general security certifications.

Provisioning API: A programmatic interface (such as OX App Suite’s Java RMI/SOAP APIs) allowing mailbox creation, modification, and management to be automated through an external system rather than a manual admin console.

Kubernetes orchestration: A containerized deployment architecture, used by current OX App Suite Software Subscription releases, that manages scaling and operations across a cluster of servers.