6. System Requirements

    Hardware Requirements

    The following table shows hardware requirements for CloverDX Server and CloverDX Cluster.

    Table 1. Hardware requirements
    Hardware Server Cluster (each node)


    8 GB (recommended 64 GB)

    8 GB (recommended 64 GB)


    8 logical cores [1]

    8 logical cores [1][2]

    Disk space (installation)

    1 GB

    1 GB

    Disk space (temp space)

    > 25 GB [3]

    > 25 GB [3]

    Disk space (data)

    > 50 GB [3]

    > 50 GB [3]

    Disk space (shared) [4]


    > 50 GB [3]


    A CPU core in this context is a logical core. Most modern processors use simultaneous multi-threading (called Hyper-Threading by Intel) and the number of logical cores is double the number of physical cores.


    This may vary depending on total number of nodes and cores in license.


    Minimum value, the disk space requirements depends on data and the processes you run on CloverDX Server.


    Disk space for shared sandboxes is required only for CloverDX Cluster.

    Software Requirements

    CloverDX Server requires a compatible operating system, an application server, Java Development Kit (JDK) and a database to run. Together, these requirements are called a stack. Not every combination of the supported vendors or software product version are supported by CloverDX Server. This section provides details about the supported configurations of software dependencies for CloverDX Server.

    At the same time, CloverDX Server can be deployed in different circumstances - either as a production instance, as a test/non-production instance, or as an evaluation instance. Production instances must follow the software stacks as described below to ensure full support and maximum stability of the platform.

    Using unsupported configurations may lead to unexpected behavior, errors, or instability within your CloverDX deployment. Adhering to the officially supported stacks and database versions ensures a reliable and functional CloverDX environment.

    Note that CloverDX Server requires a Java Development Kit (JDK) to run. JRE is not supported.

    Production deployment

    • Operating system: pick any of the systems listed below

      • Red Hat Enterprise Linux 8 (recommended)

      • Red Hat CentOS 7

      • Ubuntu 20 LTS and 22 LTS

    • Application server and JDK: application server must always be paired with specific vendor and version of JDK, other combinations are not supported.

    • System database: a system database stores CloverDX Server’s configuration and variety of logs. You can pick any of the databases mentioned in the list below. We support the listed major version for each database below, but you can pick a different minor/bugfix version of each. We use the exact version listed in our test environment.

    When using Apache Tomcat as your application server, you can also use Eclipse Temurin JDK 11. This may be useful if you require Java 11 compatibility for some reason (e.g., legacy 3rd party drivers or libraries). However, we recommend always using Java 17 if you can, as it is more secure and has higher performance.

    As you can see from the above, the preferred stack to use is RHEL + Apache Tomcat + Temurin JDK 17 + PostgreSQL 15. This stack uses mostly open-source components and is therefore simple to install and run.

    The other stacks use commercial components which come with their own support policies. Ensure that you understand those policies before selecting any of the commercial stacks.

    Non-production deployment

    For your non-production deployments, you should generally follow the same configuration as for your production instances. This will ensure maximum compatibility between your instances which is especially important during promotion of code from dev/test environments to your production.

    Same technology requirements hold for non-production deployments as for production deployments. Usually, the non-production instances are smaller (e.g., 4 cores instead of 8) or do not have as high redundancy (e.g., 2-node cluster instead of 4).

    Evaluation deployment

    Evaluation deployments are useful when you are trying new version of CloverDX Server to try a new feature, when evaluating CloverDX platform for the first time or during trainings etc.

    To make the evaluation as simple as possible, we offer one more way of installing the CloverDX Server - you can use it without external system database. In such case, CloverDX Server will use its own instance of Apache Derby database.

    Additionally, evaluation instances can also be installed on operating systems Microsoft Windows 10 (64-bit), Microsoft Windows 11 (64-bit) or macOS 13 (Ventura) and newer.

    To make the installation as easy as possible, we offer a "bundle" which contains Apache Tomcat with already deployed CloverDX Server instance which is configured to use embedded Derby instance as its system database.

    Supported Web Browsers for CloverDX Console

    CloverDX Server Console is a web interface that can be used to manage and monitor CloverDX Server instances. It is a web app and requires the following browsers to run:

    • Mozilla Firefox (latest)

    • Google Chrome (latest)

    Using any other recent browser (e.g., Microsoft Edge or Apple Safari) should work but is not supported or recommended.