2.0 Resource Requirements & Sizing

These are the ZTrust hardware requirements based on the number of users.

Sizing CPU and memory resources

Use this as a starting point to size a ZTrust environment. Adjust the values for your environment as needed based on your load tests.

• Performance will be lowered when scaling to more Pods (due to additional overhead) and using a multi-cluster setup (due to additional traffic and operations).

• Increased cache sizes can improve the performance when ZTrust instances running for a longer time. This will decrease response times and reduce IOPS on the database. Still, those caches need to be filled when an instance is restarted, so do not set resources too tight based on the stable state measured once the caches have been filled.

• Use these values as a starting point and perform your own load tests before going into production.

1. Minimum Hardware Resource Requirements

Resource	Minimum Specification
vCPU	2 vCPU
Memory (RAM)	4 GB
Storage	25 GB
Platform	Kubernetes, AWS, Azure, or any other container orchestration platform
Network	1 Gbps NIC (recommended)

1. Target Users for ZTrust Deployment

Tier	Target Users	Number of Instances/Pods	CPU (Total)	RAM (Total)	Storage (Total)
Small	≤ 1,000	2	4 CPU	16 GB	75 GB
Medium	≤ 10,000	3	8 CPU	32 GB	150 GB
Large	≤ 100,000	4	16 CPU	64 GB	500 GB

1. Use an L4/L7 Load Balancer (NGINX / HAProxy / Cloud LB) for distributing requests.

2. Software Component: PostgreSQL 17 (recommended version)

ZTrust SSO nodes should be stateless where possible, allowing scale-out and quick failover.