Setup - Server Requirements¶

This document presents the minimum hardware and resource requirements for EnQualify production installations.

General Notes¶

• CPU, RAM, and Disk values are the minimum requirements. Production environments should not fall below these thresholds.
• ADAuth API is optional — it is only required when AD login integration is enabled.
• VideoCall components (VideoResize, Signalling, CoTurn) are optional — they are only required when the video conferencing feature is enabled.
• File Storage is optional — it is required when Video Conference recording or Screen Recording is enabled.
• Test, staging, and backup systems are not included in these requirements.
• In low-volume installations (< 1,000 transactions/day), resources can be shared between components where operationally acceptable.

Option A — Classic Installation (VM / Bare-Metal)¶

Recommended use: Organizations using traditional on-premises or private cloud infrastructure (VMware, Hyper-V, bare-metal servers).

Two installation topologies are available:

• Consolidated: Multiple EnQualify components run on a single VM/server. Reduces the number of machines, suitable for smaller installations.
• Per-Container: Each component runs in its own Docker container on separate VMs. Easier to scale and update individual services.

A.1 — Consolidated Topology (Consolidated Servers)¶

Multiple components combine on a single server. Suitable for medium to large-scale deployments in traditional infrastructure.

Configuration: Base (Temel)¶

Only core EnQualify components. No optional modules.

Configuration: Screen Recording (Ekran Kaydı)¶

Includes screen recording / file storage.

Configuration: Video Call (Video Görüşme)¶

Includes video conferencing (WebRTC).

Configuration: Video Call + Screen Recording¶

Includes video conferencing (WebRTC) and screen recording / file storage.

Configuration: Video Call + Screen Recording + STT-TTS¶

Includes video conferencing (WebRTC), screen recording / file storage, Speech To Text (STT) and Text To Speech (TTS).

AD Authentication¶

Configuration: AD Authentication (AD Kimlik Doğrulama)¶

Includes AD authentication integration.

Configuration: AD Authentication + Screen Recording¶

Includes AD authentication integration and screen recording / file storage.

Configuration: AD Authentication + Video Call¶

Includes AD authentication integration and video call (WebRTC).

Configuration: AD Authentication + Video Call + Screen Recording¶

Includes AD authentication integration, video call (WebRTC), and screen recording / file storage.

A.2 — Container-Based Topology (Per-Container)¶

Each service runs in its own Docker container. Suitable for Kubernetes-ready or Docker-based deployments that require individual service scaling.

Configuration: Base¶

Only core EnQualify components. No optional module.

Configuration: Screen Recording¶

Includes screen recording / file storage.

Configuration: Video Call¶

Includes video call (WebRTC).

Configuration: Video Call + Screen Recording¶

Includes video call (WebRTC) and screen recording / file storage.

Configuration: Video Call + Screen Recording + STT-TTS¶

Includes video call (WebRTC), screen recording / file storage, Speech To Text (STT) and Text To Speech (TTS).

Configuration: AD Authentication¶

Includes AD authentication integration.

Configuration: AD Authentication + Screen Recording¶

Includes AD authentication integration and screen recording/file storage.

Configuration: AD Authentication + Video Call¶

Includes AD authentication integration and video call (WebRTC).

Configuration: AD Authentication + Video Call + Screen Recording¶

Includes AD authentication integration, video call (WebRTC), and screen recording/file storage.

Option B — Cloud-On-Premises Setup (Kubernetes)

Recommended use: Organizations in modern cloud infrastructure (AWS EKS, Azure AKS, Google GKE or on-premises Kubernetes clusters).

Main advantage: Resource requests start low. The Horizontal Pod Autoscaler (HPA) automatically scales pods based on actual load. Excess resource allocation during purchase is not necessary.

• • HPA target: Scaling out is triggered when CPU usage ≥ 70%. If the threshold is maintained for 5 minutes, scaling in occurs.
• Managed database (RDS / Azure DB / Cloud SQL) is strongly recommended to eliminate DB server sizing issues.
• The ADAuth API runs on a Windows node pool; it cannot be containerized on Linux.

B.0 — Kubernetes Resource Notation — Terminology¶

The Kubernetes configuration tables in this document utilize the following units and terms. These are standard Kubernetes resource notations.

Why not GB/MB? Kubernetes uses binary (base-2) arithmetic for memory internally. Writing ‘Mi’ and ‘Gi’ prevents ambiguity; 1 GB (decimal) ≠ 1 GiB (binary). All memory values in this document are in binary units (Mi / Gi).

Difference between CPU request and limit: A pod with request=250m and limit=500m always receives 0.25 core. It can burst up to 0.5 core if there is free capacity on the node.

B.1 — Reference Architecture¶

• • Platform: EKS (AWS) / AKS (Azure) / GKE (GCP) / On-premises Kubernetes 1.26+
• Deployment: Helm Chart. One chart for each EnQualify service; values.yaml overrides for each environment.
• Ingress: NGINX Ingress Controller or equivalent (ALB on EKS, Application Gateway on AKS)
• Service Mesh: Optional. Istio or Linkerd for inter-service mTLS.
• Persistent Storage: PVC (ReadWriteOnce) for DB volumes; ReadWriteMany (EFS / Azure Files / GCS Fuse) for File Storage.
• Secrets: Kubernetes Secrets or HashiCorp Vault integration.

B.2 — Horizontal Pod Autoscaler (HPA) Configuration¶

Each AI and API workload is configured with HPA. Example for enqualify-aiapp:

apiVersion: autoscaling/v2
kind: HorizontalPodAutoscaler
spec:
  minReplicas: 1
  maxReplicas: 4
  metrics:
    - type: Resource
      resource:
        name: cpu
        target:
          type: Utilization
          averageUtilization: 70

B.3 — POC / Minimum Startup Configuration¶

Minimum resource requirements needed to run EnQualify. Suitable for proof-of-concept and low-volume production (< 1,000 transactions/day). HPA manages burst load automatically.

POC Configuration: Base¶

Only core EnQualify components. No optional module.

POC Configuration: Screen Recording¶

Includes screen recording / file storage.

POC Configuration: Video Call¶

Includes video conferencing (WebRTC).

POC Configuration: Video Call + Screen Recording¶

Includes video conferencing (WebRTC) and screen recording / file storage.

POC Configuration: Video Call + Screen Recording + STT-TTS¶

Includes video conferencing (WebRTC), screen recording / file storage, Speech To Text (STT), and Text To Speech (TTS).

POC Configuration: AD Authentication¶

Includes AD authentication integration.

POC Configuration: AD Authentication + Screen Recording¶

Includes AD authentication integration and screen recording/file storage.

POC Configuration: AD Authentication + Video Call¶

Includes AD authentication integration and video call (WebRTC).

POC Configuration: AD Authentication + Video Call + Screen Recording¶

Includes AD authentication integration, video call (WebRTC), and screen recording/file storage.

B.4 — Production Scale Configuration¶

Recommended resource allocations for production workloads (> 1,000 transactions/day). Replicas are automatically scaled via HPA to the defined maximum.

Production Configuration: Base¶

Only core EnQualify components. No optional module.

Production Configuration: Screen Recording¶

Includes screen recording/file storage.

Production Configuration: Video Call¶

Includes video call (WebRTC).

Production Configuration: Video Call + Screen Recording¶

Includes video call (WebRTC) and screen recording / file storage.

Production Configuration: Video Call + Screen Recording + STT-TTS

Includes video call (WebRTC), screen recording / file storage, Speech To Text (STT), and Text To Speech (TTS).

Production Configuration: AD Authentication¶

Includes AD authentication integration.

Production Configuration: AD Authentication + Screen Recording¶

Includes AD authentication integration and screen recording / file storage.

Production Configuration: AD Authentication + Video Call¶

Includes AD authentication integration and video call (WebRTC).

Production Configuration: AD Authentication + Video Call + Screen Recording¶

AD authentication integration includes video conferencing (WebRTC) and screen recording / file storage.

Installation Option Comparison¶

This document is maintained by Enqura Engineering. Please contact the solution architecture team for sizing inquiries.