Open-Xchange Community Edition is an version that is not officially supported by Open-Xchange

When you choose to install packages for one of the maintained platforms as listed below, you can later buy maintenance and a support contract without migrating any data.

Products like OXtender for MS Outlook and OXtender for Mac OS can only be purchased and supported in combination with a maintenance contract and thus only with products like HE, SE or SE for UCS .

Maintained packages (Support contract available)

To download and install the software, please use the following Installation Guides:

Unsupported packages

Update from old packages

Installation Requirements


Community Edition (CE)

  • Installation, Administration and Provisioning of users and groups

User Guide & Quick Guide



UI Customization and Examples

Groupware Server customization

Programming Interfaces

  • The HTTP API is used by the Open-Xchange GUI and various 3rd party applications. It consists mainly of messages in JavaScript Object Notation (JSON) sent over HTTP.
  • Provisioning API to access the Open-Xchange Admin Daemon
    • The RMI API is used for data provisioning of Contexts, Users, Groups and Resources as well as for configuring Databases, Filestores and OX Servers. It is currently split into two parts,
    • The Open-Xchange CLT are shell scripts that simplify groupware and service administration
    • Create contexts/users with with Csv_import
    • Provisioning using SOAP
  • The Oxmapi is a windows library for programmers needed to communicate with the OX server
  • Open-Xchange Mail Abstraction Layer
  • The Plugin API for extending the GUI is described in two documents: an overview and the reference
  • UDPPush Open-Xchange PUSH Interface for Groupware Objects

Importing and exporting data

Configuration and Tweaks

Testing and QA


Installation based on source code

Open-Xchange Plugins

Open-Xchange is using the OSGi architecture to have maximum extensibility and flexibility. Many parts of Open-Xchange Server can be replaced by different OSGi components, which are called Bundles.

If you have further requests, this document describes the Open-Xchange feature prioritization process and the options for partners and customers to either feed feature requests into this process or to order custom feature implementations.

Community OXtender


Open-Xchange Munin integration