Setup - Server Requirements¶

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

General Notes¶

• CPU, RAM, and Disk values are 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 Call 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 among components where operationally acceptable.

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

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

Two installation topologies are available:

• Consolidated Servers: 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 are consolidated per server. Suitable for medium to large-scale installations 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: AD Authentication (AD Kimlik Doğrulama)¶

Includes AD authentication integration.

Configuration: AD Authentication + Screen Recording¶

Includes AD authentication integration and screen recording/file storage.

(Note: No table is provided for this configuration in the original document.)

Configuration: AD Authentication + Video Call¶

Includes AD authentication integration and video conferencing (WebRTC).

Configuration: AD Authentication + Video Call + Screen Recording¶

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

A.2 — Per-Container Topology (Konteyner Tabanlı)¶

Each service runs in its own Docker container. Suitable for Kubernetes-ready or Docker-based installations requiring individual service scaling.

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: 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 conferencing (WebRTC).

Configuration: AD Authentication + Video Call + Screen Recording¶

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

Option B — Cloud-Local Installation (Kubernetes)¶

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

Main advantage: Resource requests start low. Horizontal Pod Autoscaler (HPA) automatically scales pods according to real workload — excessive resource provisioning at purchase time is not required.

• HPA target: Scaling out is triggered when CPU utilization ≥ 70%. If the threshold remains below for 5 minutes, scale in occurs.
• Managed database (RDS / Azure DB / Cloud SQL) is strongly recommended to avoid DB server sizing issues.
• ADAuth API runs on a Windows node pool — cannot be containerized on Linux.

B.0 — Kubernetes Resource Notation — Terminology¶

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

Why not GB/MB? Kubernetes internally uses binary (base-2) arithmetic for memory. Using 'Mi' and 'Gi' avoids ambiguity — 1 GB (decimal) ≠ 1 GiB (binary). All memory values in this document are binary units (Mi / Gi).

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

B.1 — Reference Architecture¶

• Platform: EKS (AWS) / AKS (Azure) / GKE (GCP) / On-prem Kubernetes 1.26+
• Deployment: Helm Chart — one chart per EnQualify service, values.yaml overrides per environment
• Ingress: NGINX Ingress Controller or equivalent (ALB in EKS, Application Gateway in AKS)
• Service Mesh: Optional — Istio or Linkerd for inter-service mTLS
• Persistent Storage: PVC for DB volumes (ReadWriteOnce); ReadWriteMany for File Storage (EFS / Azure Files / GCS Fuse)
• 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 requests to get EnQualify up and running. Suitable for proof of concept (POC) and low-volume production (< 1,000 transactions/day). HPA automatically manages burst load.

POC Configuration: Base (Temel)¶

Only core EnQualify components. No optional modules.

POC Configuration: Screen Recording (Ekran Kaydı)¶

Includes screen recording/file storage.

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

Includes video conferencing (WebRTC).