System Requirements

ViXa Identity-First Platforms system requirements

This topic applies to all Ost Infinity ViXa Identity-First Platforms (self-hosted) products. Requirements depend on various variables, such as:

Ost Infinity ViXa Identity-First Platforms deployment in the cloud vs on premises.
Size of the environment to be monitored. This topic provides requirements for small, medium, large and extra large deployments, based on the number of monitored elements, such as nodes, interfaces, or component monitors, based on your Subscription. See Subscription model for Ost Infinity Identity-First Observability Self-Hosted.
Review your product Administrator Guides and release notes for the exact product requirements beyond these minimums.
Ost Infinity Identity-First recommends reviewing the latest Ost Infinity Identity-First Platforms Release Notes.
Ost Infinity Identity-First does not provide a comprehensive list of all supported devices. If your device supports standard SNMP MIB2, it can be monitored with the Ost Infinity Identity-First Platforms. See Supported vendors and devices.

What requirements are you looking for?

Requirements for supported cloud solutions:
- Amazon Web Service
- Microsoft Azure
On-premises deployment requirements overview:
- Server hardware details
- Server software details
- Database server details
- Ports to open
- Ost Infinity Identity-First Platforms Web Console browser requirements

Amazon Web Service

Requirements	Small (up to 500 elements)	Medium (501–2,000 elements)	Large (more than 2,000 elements)	XL (up to 1,000,000 elements)
Ost Infinity Identity-First Platforms server	m4.xlarge	m4.2xlarge	m5.2xlarge	m5.4xlarge
Ost Infinity Identity-First Platforms database using Azure SQL DB	All installed products must run on ViXa Identity-First Platforms 2019.2 or later. Time zone setting of the server must be the same as Azure SQL DB time zone (UTC).
	DTU Standard Tier S3 or better vCore General Purpose Tier 2 or better	DTU Standard Tier S3 or better vCore General Purpose Tier 2 or better	DTU Standard Tier S4 or better vCore General Purpose Tier 2 or better	DTU P15 vCore Hyper-Scale 40 vCPU
Ost Infinity Identity-First Platforms database using Azure SQL Database managed instance	Gen5 4 vCores	Gen5 8 vCores	Gen5 16 vCores	Gen5 40 vCores
Ost Infinity Identity-First Platforms database deployed in an Azure VM	A4_v2	DS4_v2 Standard	E8s_v3	E64as_v4 IOPS 30,000+
Additional Polling Engine	Only relevant for environments that monitor over 12,000 elements at default polling intervals.		D4s_v3	D4s_v3
Additional Web Server	Less than 50 concurrent users: DS12_v2 More than 50 concurrent users: DS4_v2 or larger		DS4_v2 or larger

On premises

To deploy a single Ost Infinity Identity-First Platforms product locally, on a server, review the following recommendations.

The minimum/recommended requirements are based on the most common element distribution (nodes, volumes, and interfaces) and polling technology used (ICMP/SNMPv2).

Using other polling methods (Ost Infinity Identity-First Platforms Agent, WMI, or SNMPv3) with authentication or more complex element types (applications, firewalls, load balancers, or wireless controllers) will increase hardware requirements for the server.

Ost Infinity Identity-First Observability Self-Hosted

Minimum / Recommended

Requirements	Small (up to 500 elements)	Medium (501–2,000 elements)	Large (more than 2,000 elements)	XL (up to 1,000,000 elements)
Server Hardware	CPU: 4 Cores / 8 Cores RAM: 16 GB / 32 GB	CPU: 4 Cores / 8 Cores RAM: 16 GB / 32 GB	CPU: 8 Cores / 12 Cores RAM: 32 GB / 64 GB	CPU: 8 Cores / 12 Cores RAM: 32 GB / 64 GB
Server Software	Windows Server 2025, 2022, 2019, 2016 Desktop OS only for evaluations; NOT recommended for production environments FIPS-compliant OS, STIG-compliant OS, Device Guard-compliant OS
Database Server	Production environment requirements: In production environments, the server and database must be deployed on separate machines. If using virtual machine, database must be on a different physical drive. Recommended: For XL environments, use SQL Server Enterprise 2019 CU4+ on Windows Server 2019. Supported: SQL Server 2016 SP1 and later Quad core 8 GB / 16 GB RAM 20 GB / 40 GB HD Dual quad core 16 GB / 64 GB RAM 50 GB / 100 GB HD Dual quad core+ 64 GB / 128 GB RAM 100 GB / 400 GB HD High performance CPUs with 32,000+ PassMark 256 GB RAM / 512 GB RAM 2 TB HD IOPS: 30,000 / 190,000 SSD strongly recommended
Additional Polling Engines	CPU: 4 Cores / 8 Cores RAM: 16 GB / 32 GB Windows Server 2025, 2022, 2019, 2016		CPU: 8 Cores / 12 Cores RAM: 32 GB / 64 GB
Additional Web Server	Relevant for environments near 50 concurrent users. 8-core CPU or better, 16 GB RAM, 60 GB HD Windows Server 2025, 2022, 2019, 2016 Requirements depend on the number of concurrent users. If multiple users are logged in at the same time, the more RAM, HD space, and cores you need.
Ports to open	Outbound: 22, 25, 465, 587, 1433, 1434 Inbound: 80, 162, 443, 514, 17778 Bi-directional: 53, 135, 161, 5671, 17777
Account privileges	Ost Infinity Identity-First recommends that administrators have local administrator privileges on the server to ensure full functionality of local tools. Web Console user accounts do not require local administrator privileges. Users running Configuration wizard must have DBO specified as the default DB schema. All services run under LocalSystem to protect certificates and credentials from shared lower-privilege accounts.
Latency	The latency (RTT) between the engine and database server should be below 200 ms. Latency may begin to degrade at 100 ms depending on deployment size and utilization. Higher latency will affect large deployments more significantly. Use ping to the SQL Server to verify latency and ensure stable connections.
Other	Localization constraints: German and Japanese only for self-hosted environments. Supported systems: NPM, NTA, LA, NCM, SAM, and VMAN Calendar constraints: Gregorian calendar only