Skip to content

System Requirements and Prerequisites

System Requirements

To install and use Squash TM, please see the minimum and recommended requirements below:

Minimum (for trial) Single-core 1 GB dedicated 1 GB Linux, Windows
Recommended Bi-core 2 GB dedicated 5 GB Linux

The hard drive disk (HDD) will be used to store logs and the database if it is on the same server.

The app itself and its files weigh 130 MB. You need at least 200 MB of free disk space if you want to store Squash TM and its logs. If you want to also store Java and Squash TM database on the same server, you need at least a minimum of 1 GB of free disk space.


These elements are only given as an indication. They cannot replace a complete study that takes into account the target context.


Table of middleware versions compatible with Squash TM:

Minimum production environment Recommended
Operating system Linux, Windows Debian 11, Centos 7
Java JVM version 17 LTS JVM version 17 LTS
Database PostgreSQL 11+, MariaDB 10.6 PotgreSQL 13, MariaDB 10.6


Starting from version 6.X, Squash TM is no longer compatible with Java versions lower than 17 (Java installed on the machine hosting Squash TM).

As a reminder, Squash TM is no longer compatible with:

  • MariaDB 10.5 and previous versions since version 5.0
  • MySQL since version 4.0


Squash TM is delivered with an embedded base (H2) that can be used for evaluation purposes. We do not recommend you to use it in a production context.
Please visit the page Install database to learn how to use another database than H2.

  • Other software recommendations:
    • Mantis 2.x+ or Jira 8.4+
    • Apache HTTPD (frontal web)'s latest version

Possible Architecture

For small volumes and a limited number of users (less than 50), Henix recommends a "three-level" architecture. In other words, on a virtual machine, you install these three services:

  • Application
  • DBMS
  • Frontal Web

To deploy Squash TM within a shared infrastructure, it is possible to have the three services on three different systems and to interconnect them through the network.

The reverse proxy is optional, but we recommend you to use it for two reasons: first, to separate the access logs from the application logs; and second, to entrust the TLS encryption to another process/service than Squash TM, even if the app's embedded Tomcat server is able to do it.

We highly recommend that no matter the volumes, to have both Squash TM and the database on the same server so as not to slow down performance with additional processes.

Recommendations for Squash Orchestrator use

There are no prerequisites to install and use Squash TM with Squash Orchestrator:

  • To use Squash Orchestrator with Squash TM, you just have to install the required plugins

Learn More

To learn more about Autom plugins, please visit the page Squash TM Plugins

  • When it comes to sizing the database, it will depend on the quantity and frequency of automated tests results transmitted to Squash TM. Squash TM has a feature to help you regulate the volume of automated executions: Automated suites cleaning
  • Squash Orchestrator is packaged as a Docker image but exchanges with Squash TM are done via REST calls, so you do not need to also install Squash TM as a Docker.