Requirements

The following table provides an overview about the supported components of OX App Suite Software Subscription v8 and further products. This overview makes no claim to be complete.

Hardware Requirements

General Assumptions

Open-Xchange App Suite Software Subscription v8 is designed to be deployed into a standard Kubernetes cluster, though assumes some additional components to be available (Istio, Redis Operator). This works best in a cluster dedicated to only running Open-Xchange Software Subscription v8. This preserves the degrees of freedom necessary to choose global enhancements to Kubernetes. If you need to run OX App Suite Software Subscription v8 in a Kubernetes cluster used for additional applications, care needs to be taken to ameliorate OX App Suite Software Subscription v8 requirements for the cluster with those of other components.

Network is expected to be flat, inside one datacenter, no multi-datacenter, no segments. No packet loss, low latency.

Disclaimer

All recommendations below are without guarantee and can differ for specific deployments. For mid- and large-scale setups, a detailed deployment planning and sizing tests are mandatory and should be agreed on with OX Professional Services.

High Level Design / Kubernetes Setup

We assume a standard Kubernetes cluster, as per the upstream kubernetes.io version of the software.

Further hardened and modified Kubernetes distributions might work, but we don't test them explicitly. The closer to a standard Kubernetes the cluster is, the fewer problems there'll be. For any of the Kubernetes components (Kubernetes and add-ons) we'll support and expect one version below the currently released version and one below that, but expect swift and frequent updates to the platform as well. Automation needs to be in place to update cluster software and App Suite 8 itself. We do not recommend running services requiring persistence (database, file store) inside Kubernetes yet.

Platform Architecture: Kubernetes needs to be able to run containers in 64 bit (x84_64) architecture.

Node Sizing

Container Sizing

• For Java services (of which there are 4) we recommend to use not more than 4GB as memory requests and limits and scale out by scaling up the number of containers instead
• For the spellcheck service, we recommend allocating not more than 2 GB of memory
• UI Middleware needs 512MB
• The UI source containers (of which there are 4) need around 100MB of RAM and usually don't need to be scaled up since they only supply source code to the UI middleware
• Helm charts contain reasonable defaults for these values, and usually you will only need to change them downwards if you're serving a smaller than usual installation or instead scale up the number of containers if your load exceeds what the standard setup can handle.

Cluster Sizing

• General advice for running a robust Kubernetes cluster apply. Run a separate ETCd cluster with at least 3 nodes, at least 2 Kubernetes API / primary nodes and at least 2 agents. Factor in some overhead on top of the sums of what the services use above.
• 2 agents with 16 GB memory each should serve as a starter configuration if you want to run at least two redundant instances of anything but the UI source containers (of which one is enough). That should cover a minimum viable professional installation of App Suite 8.

Untested/Unsupported Deployments

• Hardened Kubernetes (e.g. OpenShift). We aspire to supporting these platforms, but currently don't yet.
• Cloud platform services (PaaS) that promise to replacements for certain supported technologies but have not been verified by OX for these regards
• Multi-site active-active

Software Requirements

Kubernetes + Non-Standard Kubernetes Components

Component	Version
Standard Kubernetes	1.26, 1.27
Istio Service Mesh	1.18, 1.19
Redis Operator	1.2.4 (Chart: 3.2.8, 3.2.9)

These requirements change rather frequently as the listed components have their own lifecycles and support timeframes:

• Istio: ~6 months
• Kubernetes: ~12 months
• Redis: ~18 months

Thus we can only document which versions we have tested at the time of the OX App Suite Software Subscription v8 release.

Recommended Additional Components

In addition to the components above, we strongly recommend using FluentBit / Graylog for log ingestion and storage as well as Prometheus/Grafana for monitoring.

Databases

OX App Suite Software Subscription v8 uses MariaDB with the InnoDB storage engine as its primary data store. The following vendors and products are supported.

Vendor	Product	Versions
MariaDB	MariaDB Server, Galera Cluster	v10.6.x, v10.11.x

File Storage

Temporary Data

OX App Suite Software Subscription v8 stores temporary files in the local file system, e.g. for spooling of uploaded data, and uses emptyDirs for that. This will use some local storage on the agents.

Persistent Data

Persistent data like OX Drive files, PIM attachments etc. and temporary attachment data need to be stored in a distributed file system as registered file store that is available from all server nodes. For single-node setups a local file system mount point can be used, small to mid-scale setups can be powered by NFS. For large-scale setups, object storage should be considered.

Object Storage

OX App Suite Software Subscription v8 ships with different optional adapters to support object storage.

Vendor	Product	API	Remarks
Amazon	AWS S3	S3 HTTP API	See also AppSuite:S3_File_Store
CEPH	RadosGW	S3 HTTP API	See also AppSuite:S3_File_Store
Scality	Scality RING	Sproxyd HTTP API	See also AppSuite:Scality_File_Store

Desktop Browser (Minimum display resolution: 1024 x 768)

Browser	OX App Suite User Front-End
Google Chrome (latest & previous version)	v8.23
Mozilla Firefox (latest & current ESR-Version)	v8.23
Apple Safari (17.x)	v8.23
Microsoft Edge (latest version, Chromium-based)	v8.23

Mobile OS & Browser Support (Smartphone & Tablet)

Mobile Device	Supported Browser	OX App Suite User Front-End
iOS/iPadOS >= 16.7.2, >= 17.x	Safari	v8.23
Android >= 10	Chrome (latest version)	v8.23

Mobile network connection: Devices not connected a local wifi should at least use a 4G (LTE) internet connection for best results

Calendar/Contact synchronization Apple macOS

Requirement	Calendar synchronization with CalDAV	Contacts synchronization with CardDAV
macOS 13.0 (Ventura)	✅	✅
macOS 14.0 (Sonoma)	✅	✅

Calendar/Contact synchronization Apple iOS

Requirement	Calendar synchronization with CalDAV	Contacts synchronization with CardDAV
Apple iOS 15 / iOS 16 / iOS 17 / iPadOS	✅	✅

Mobility Solution - Supported-Platforms, Features and Devices

Feature/Technology/Device	OXtender for Business Mobility (available for App Suite, OXHE, OXSE)
Exchange Active Sync 2.5	✅
Exchange Active Sync 12.1	✅
Access and creation of emails	✅
Personal PIM folder	✅
Public and Shared PIM folder	❌
Global address book	✅
Push E-Mail	✅
Apple iOS 15 / iOS 16 / iOS 17 / iPadOS	✅
Android 8 (Oreo) or later with latest Gmail app.	✅

OX Drive Clients

Requirement	System / Platform
OX Drive for Windows	OX App Suite Software Subscription v8.23 Latest versions of Windows 10 and above (no support for Windows RT and emulators)
OX Drive for Apple macOS	OX App Suite Software Subscription v8.23 macOS Ventura 13, macOS Sonoma 14, Intel- and Apple Silicon-based devices are both supported
OX Drive for Apple iOS	OX App Suite Software Subscription v8.23 iOS / iPadOS 15 and above
OX Drive for Android	OX App Suite Software Subscription v8.23 Smartphones and tablets running Android 9.0 (API level 28) and above

OX Sync App

Requirement	System / Platform / User Interface
OX App Suite Software Subscription	v8.23
OX Sync App for Android	Smartphone on Android 5.0 or later

OX Guard

Requirement	System / Platform / User Interface
OX App Suite Software Subscription	v8.23