System Requirements

This is the canonical reference for everything you need to know before deploying Syteca: how to size the Application Server, Management Tool, and database for your workload; which operating systems are supported; which network ports must be open; and what kind of CPU, bandwidth, and storage each Client generates. Use it during planning, during procurement, and as a sanity check during installation.

Deployment sizing

Sizing depends on the number of concurrent Client sessions you’ll be recording. Syteca recognizes four tiers — PoC, Small, Medium, and Large.

Application Server, Management Tool, and Database

Component	PoC	10–200 sessions	200–1,000 sessions	1,000–10,000 sessions
Application Server	4–8 vCPU, 16 GB RAM	4–8 vCPU, 8–16 GB RAM	8–16 vCPU, 8–16 GB RAM	16–32 vCPU, 8–16 GB RAM
High Availability	Optional	Optional	Optional	Strongly recommended
Management Tool	4–8 vCPU, 4 GB RAM	4–8 vCPU, 4 GB RAM	4–8 vCPU, 4 GB RAM	4–8 vCPU, 4 GB RAM
Database	4–8 vCPU, 16 GB RAM	8–16 vCPU, 24–32 GB RAM	16–32 vCPU, 64–128 GB RAM	(scale beyond Medium per workload)
Bandwidth	1 Gbps Ethernet	1 Gbps Ethernet	10 Gbps Ethernet	10 Gbps Ethernet
Operating systems	Windows 10 / Server 2019 / 2022 / 2025	Windows Server 2019 / 2022 / 2025	Windows Server 2019 / 2022 / 2025	Windows Server 2019 / 2022 / 2025

For deployments with 1,000+ Clients, install multiple Application Servers in High Availability / load balancing mode to avoid performance issues. The Strongly Recommended designation in the Large column reflects this — single-AS deployments at that scale will struggle.

Database support

All deployment sizes support the same database engines:

Database	Supported versions
Microsoft SQL Server	2012 through 2022
PostgreSQL	13 or higher
Microsoft Azure SQL Database	(managed)

For the differences between PostgreSQL and MS SQL Server in a Syteca deployment, see Comparison of database types.

Storage sizing

Storage requirements scale with the number of concurrent Client sessions and the work pattern (24/7 always-on vs. 8/5 business hours). The values below assume 1 Client session generates an average of ~300 MB per 8-hour day (see Performance numbers below).

Work pattern	PoC	Small	Medium	Large
24/7 (always-on)	272 GB	5.25 TB	27 TB	270 TB
8/5 (business hours only)	65 GB	1.4 TB	7 TB	40 TB

Store binary data in a shared or local folder, not in the SQL database itself. The SQL Database binary storage option is only recommended for the smallest deployments — for anything beyond PoC, the data volumes accumulate too quickly. See Configure binary storage for the options including filesystem, network share, and Amazon S3-compatible storage.

Client requirements

Syteca Clients are lightweight endpoint agents. The performance impact on each monitored endpoint is minimal — see Performance numbers below for the specifics.

Windows Clients

Versions supported	Hardware	Additional applications
Windows 11, Windows 11 Enterprise LTSC 2024, Windows 11 IoT Enterprise LTSC 2024	CPU: 2.4 GHz or higher	(For PAM customers only — see right column)
Windows 10, Windows 8.1, Windows 8, Windows 7	RAM: 4 GB (35 MB per session)	• PuTTY — for Unix (SSH) secrets
Windows Server 2025, 2022, 2019, 2016, 2012	Ethernet: 100 Mbps / 1 Gbps	• SQL Server Management Studio (SSMS) 18–20 — for MS SQL secrets
		• Google Chrome in Incognito mode — for Web account secrets
		• WinSCP — for File Transfer

macOS Clients

Versions supported	Hardware
macOS Tahoe 26, Sequoia 15, Sonoma 14, Ventura 13, Monterey 12	CPU: 2.4 GHz Intel Core 2 Duo or higher / M1, M2, M3, M4. RAM: 2 GB. Ethernet: 100 Mbps / 1 Gbps

Linux Desktop Clients (with X Window System GUI)

Distribution	Versions
Ubuntu	24.04 LTS, 22.04 LTS, 20.04 LTS, 18.04.1 LTS, 16.04.5 LTS, 16.04.2, 14.04.5 LTS, 14.04.2, 14.04 LTS, 12.04.1 (including Wayland for: 24.04 LTS, 22.04 LTS, 24.10, 23.10, 23.04, 22.10)
Red Hat (RHEL)	9.0, 8.8, 8.0–8.4, 7.0–7.6, 6.0–6.10
CentOS	8, 7.1–7.5, 6.1–6.9
Oracle Linux	9.1, 8.5–8.7, 5.26–7.x
Amazon Linux	2.x
AlmaLinux	9.3–9.4, 9.7
openSUSE	15 (SP1, SP2, SP3, SP4, SP5, SP6), 12 (SP1, SP2, SP3, SP4, SP5)

Hardware: CPU 2.4 GHz or higher, RAM 4 GB (35 MB per session), Ethernet 100 Mbps / 1 Gbps, Linux Kernel 2.6.32 or higher.

Linux Server Clients (as a Terminal Server)

Distribution	Versions
Debian	12.11, 11.0, 9.0, 8.0, 7.0
Ubuntu	24.04 LTS, 22.04 LTS, 22.04, 20.04, 18.04, 16.04, 14.04
Red Hat (RHEL)	10.0, 9.0, 8.8, 8.0–8.4, 7.0–7.6, 6.0–6.10
CentOS Stream	9, 8
CentOS	8, 7.1–7.5, 6.1–6.9
Oracle Linux	9.4, 9.1, 8.5–8.7, 5.26–7.x
Amazon Linux	2.x
AlmaLinux	9.3–9.4, 9.7, 10.1
openSUSE	15 (SP1–SP6), 12 (SP1–SP5), 11 (SP2, SP3, SP4)
Solaris	11.4 (x86_64), 11.0–11.3 (Sparc), 10.0 (SPARC) — Global and Whole-root zones only
AIX	7.3, 7.2, 7.1

Network requirements

Open these TCP ports in Windows Firewall (or your equivalent firewall product) for Syteca to operate correctly. The exact set depends on your deployment topology.

Direction	Protocol/Port	Required?	Purpose
Endpoint Client → Application Server	TCP/9447	Required	Session data from Clients to the Application Server. In SaaS: required for Windows Clients only.
Application Server → Management Tool	TCP/22713 & TCP/22714	If on different machines	Management Tool connection to Application Server, when they’re on separate hosts.
Management Tool → browser (HTTPS)	TCP/443	If on same machine	Browser access to the Management Tool. In SaaS: required for Windows, macOS, and Linux Clients to check for certificate updates regularly. Also required in SaaS for macOS and Linux Clients to send session data to the Application Server (replacing TCP/9447 in this case).
Application Server → Endpoint Clients	TCP/135 & TCP/445	For remote install	Required only when installing Windows Clients remotely from the Management Tool.
Application Server → PostgreSQL database	TCP/5432	If on different machines	Application Server to PostgreSQL database connection, when on separate hosts.
Application Server → MS SQL database	TCP/1433	If on different machines	Application Server to MS SQL database connection, when on separate hosts.

In SaaS only: TCP/443 plays a dual role — it’s the Management Tool browser port, but it also handles certificate-update checks for all Client OSes, and is the data channel for macOS and Linux Clients (replacing TCP/9447 used by Windows Clients).

The Windows Firewall configuration for the Application Server is normally automated during installation — see Install the Application Server for the manual configuration procedure if needed.

Performance numbers

The metrics below describe per-Client resource usage. They drive the storage sizing calculations above and help you plan bandwidth and disk capacity.

Per-Client resource usage

Parameter	Value
Average CPU consumption (1 hour of operation)	0.5% per Client session
Peak CPU consumption	Up to 5% per Client session
Bandwidth requirements	128 Kbit/s
Average data volume	~300 MB per 8-hour work day per Client (most Client types — Linux SSH sessions often more)
Peak data volume	15–25 MB per intensive work hour per Client

Windows Client data volume

Scenario	Data volume
1 Client session/day (average)	300 MB
1 Client session/day (maximum, highest screen capture resolution)	5,172 MB
100 Client sessions/day (average)	30 GB

Linux Client data volume

X Window System sessions only — remote SSH sessions often generate more data.

Scenario	Data volume
1 Client session per 15 minutes (average)	8 MB
1 Client session per day (average)	100 MB

Performance measured with one session using Full HD display resolution and the default screen capture and color settings. Real-world numbers vary with monitor count, screen activity, color depth, and Client configuration.

Reduce data volume by tuning recording settings. Default settings are tuned for visibility — most deployments can significantly reduce data volume without losing the recording fidelity they actually need. Adjustable parameters live on the Windows Clients, macOS Clients, and Linux Clients configuration pages, including user activity recording parameters, monitoring filters, and (for Linux) per-command output limits.

Architecture overview

The component structure of a Syteca deployment.

Install Application Server

Fresh installation with database, certificate, and firewall setup.

High Availability

Scale-out with multiple Application Server instances, load balancing, and disaster recovery.

VDI Monitoring

Citrix, VMware Horizon, Microsoft AVD, Amazon WorkSpaces — with floating licensing.

Welcome

Get Started