Use this section when you deploy OpenLM on infrastructure that you manage.

Core platform baseline

These requirements apply across customer-managed Kubernetes deployments.

Shared requirements

• Use persistent storage classes for stateful workloads.
• Use TLS termination at the ingress layer.
• Validate sizing against expected Broker counts, usage volume, report volume, and retention.
• Confirm that all required OpenLM services can reach the cluster endpoints.

Provider-specific references

• Azure cloud infrastructure requirements
• Managed Amazon Elastic Kubernetes Service infrastructure requirements

Use the provider-specific pages for network sizing, node pool layouts, and managed service baselines.

———————————————————————————————————–

This reference captures the Azure sizing baseline from document version 1.1.1 dated November 26, 2025. Adjust node counts and service sizes for larger environments.

Networking

Use Azure Container Networking Interface (CNI) mode for Azure Kubernetes Service (AKS).

Capacity example

• The source design allows about 29 pod IP addresses per node.
• Six nodes provide about 174 pod IP addresses.
• 143 pods and 6 nodes consume about 149 IP addresses.
• A /22 block leaves room for growth.

Azure Kubernetes Service

Use Kubernetes version 1.32.9 or another AKS-supported version that matches your release policy.

The source design uses 7 virtual machines across the 3 node pools. Nodes with 16 GB of RAM leave headroom for platform pods because baseline node overhead is about 1 GB per node.

Managed services

AKS provisions managed disks automatically when the cluster uses the required storage classes.

Sizing notes

• Validate pod counts, data retention, and report volume before deployment.
• Increase database and cache sizes when user volume, reporting load, or retention increases.

This reference matches the Terraform-based deployment document dated February 4, 2026. The sizing baseline reflects a production deployment in eu-central-1.

Deployment summary

• Region: eu-central-1
• Availability Zones: eu-central-1a, eu-central-1b, eu-central-1c
• Kubernetes service: Amazon Elastic Kubernetes Service
• Kubernetes version: 1.34
• Endpoint access: public and private, with public access restricted by allowed network ranges
• Control plane logs: API, audit, authenticator, controller manager, and scheduler
• Secrets encryption: AWS Key Management Service (KMS) customer-managed key
• Source commit: acbd6f0

Network topology

Node groups

The source design uses 7 nodes in total: 1 m6i.large node and 6 m6i.xlarge nodes.

Managed AWS services

Amazon Relational Database Service for SQL Server

Amazon Managed Streaming for Apache Kafka

Amazon ElastiCache for Valkey

MongoDB requirement

• AWS DocumentDB is not supported in this deployment.
• Use MongoDB Atlas as a managed service, or run MongoDB in Kubernetes.

Ballpark monthly cost

These estimates apply to eu-central-1 as of February 4, 2026. Use AWS Pricing Calculator for final quotes.

Total estimated range: about $3,050 to $5,100 per month.

Assumptions

• This sizing assumes a moderately loaded production system.
• Development sizing is available in dev.tfvars.example.
• The Amazon Relational Database Service price includes SQL Server licensing, and that licensing is a major cost driver.
• Costs increase with throughput, storage growth, and workload demand.

Infrastructure requirements

Minimum hardware requirements

• Dual-core CPU
• 2 GB of RAM

Platform Support

Tested on:

• Windows 10
• Windows 11
• Ubuntu 18
• Ubuntu 20
• CentOS 8

Dependencies

• The Linux Workstation Agent requires a pre-installed libXScrnSaver library when installed on CentOS using the tar.gz package
• The Workstation Agent is a self-contained .NET app (no additional runtimes required)

Network requirements

• The Workstation Agent needs to connect to TCP port 443 for communications with:
  • Agents Hub
  • OpenLM Identity

Hardware requirements

• Dual core CPU
• 4 GB memory (Recommended: 8 GB)

Platform requirements

• Windows only

Dependencies

• .NET Framework 4.5.2 or higher required to run the installer
• Self-contained .NET Core application (no additional runtimes required)

Port configuration

• Port 8081 must be free during installation
  • If occupied, edit kestrel.config in the DSA installation folder (C:\Program Files\OpenLM\OpenLM Directory Synchronization Agent)
  • Change port number and restart the Directory Synchronization Agent service

Network requirements

When installed separately from OpenLM Server:

• DSA machine requires outbound access to port 7026

Supported Directory Services

• Microsoft Active Directory
• NetIQ eDirectory
• ApacheDS
• AzureAD