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.

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 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.