Document Version: 1.0
Date: 23 September 2025

This document outlines the minimum and recommended server specifications required for a successful deployment of the iqxWEB application stack. Adhering to the recommended specifications is crucial for ensuring optimal performance, stability, and scalability in a production environment.

The following tables detail the resource requirements. The Minimum configuration is suitable for testing or light production use with a limited number of concurrent users. The Recommended configuration is designed to provide a robust and responsive experience for a moderate user load.

A modern, 64-bit server distribution is required. We recommend any of the following Long-Term Support (LTS) versions:

• Ubuntu Server
• Debian
• Red Hat Enterprise Linux (RHEL) family (e.g., RHEL, Rocky Linux, AlmaLinux)
• SUSE Linux Enterprise Server

• Windows Server 2025 or later is required.
• Hardware-assisted virtualization (e.g., Intel VT-x or AMD-V) must be enabled in the BIOS/UEFI.
• The Windows Subsystem for Linux (WSL) 2 feature must be installed and enabled, as the application runs within Linux containers.

Please ensure the following requirements are met prior to the scheduled installation date.

• Public Accessibility: The server must be accessible from the internet on a static public IP address. Alternatively, a professionally configured reverse proxy can be used to forward traffic to the server.
• Firewall Rules:
  • Inbound traffic must be permitted on TCP ports 80 (HTTP) and 443 (HTTPS).
  • Outbound traffic must be permitted from the web server to the IQXHub (Bridge Server) host over its designated port (typically TCP 54000).
• SSL/TLS Certificate: A valid SSL/TLS certificate and its corresponding private key for the application's domain name must be provided to the installation team before deployment can begin.
• SSH Access (Linux): For security purposes, we strongly recommend that server access be configured using SSH key-pair authentication and that password-based authentication is disabled.

The client is responsible for the ongoing maintenance and security of the server environment. This includes, but is not limited to:

• Performing regular operating system updates and security patching.
• Implementing and managing a robust data backup and disaster recovery strategy.
• Monitoring server performance, resource utilisation, and log files.