System requirements for OpenLM components
To check that a machine can run a component, select the tab of the component. The install pages link to their own tab.
- Workstation Agent
- DSA
- Broker
- SaaS Agent
- AI Proxy
- OpenLM Router
Infrastructure requirements
This section lists the hardware, platform, dependency, and network requirements for the Workstation Agent.
Minimum hardware requirements
The Workstation Agent requires the following minimum hardware:
- Dual-core CPU
- 2 GB of RAM
Platform support
The Workstation Agent runs on:
- Windows 10 and Windows 11.
- Linux, 64-bit x86: Ubuntu and Debian with the DEB package, and Rocky Linux and other Red Hat Enterprise Linux family distributions with the RPM package. The
tar.gzarchive also installs on these. - macOS 10.15 (Catalina) or higher, on Intel and Apple Silicon Macs.
On Linux, the Workstation Agent needs glibc 2.27 or later.
For the steps, see Install Workstation Agent.
Dependencies
The Workstation Agent has the following dependencies:
- The Linux Workstation Agent reads the idle time of the X11 desktop session. The RPM package installs
libXScrnSaver. With the DEB package or thetar.gzarchive, installlibxss1on Ubuntu or Debian. - The Linux Workstation Agent requires the ICU library,
libicu. Ubuntu includes it. On Rocky Linux and other Red Hat Enterprise Linux distributions, install it withsudo dnf install libicubefore you install the agent. - The Workstation Agent is a self-contained app, so you install no separate .NET runtime on Windows, Linux, or macOS.
Network requirements
Confirm this network connectivity:
- The Workstation Agent needs to connect to TCP port 443 for communications with:
- Agents Hub
- Identity
Hardware requirements
The Directory Synchronization Agent (DSA) requires the following minimum hardware:
- Dual-core CPU
- 4 GB memory (recommended: 8 GB)
Platform requirements
The DSA runs on 64-bit Windows only.
Dependencies
The DSA has the following runtime dependencies:
- .NET Framework 4.5.2 or higher, required to run the installer
- The DSA is a self-contained .NET app, so you install no separate runtime
Network requirements
The DSA opens every connection itself, so the machine needs no inbound access from the internet. Open these ports:
| Direction | Port | Purpose |
|---|---|---|
| Outbound | 443 (HTTPS) | Reporting to OpenLM Platform |
| Outbound | 389, or 636 with SSL | Reading a local directory (LDAP) |
| Outbound | 3268, or 3269 with SSL | Reading through a Global Catalog |
| Local | 8099 | The DSA's own service port on the machine |
| Outbound | 443 (HTTPS) | Reading a cloud directory such as Microsoft Entra ID, Google, or Okta |
For the steps, see Install the Directory Synchronization Agent (DSA).
Supported directory services
The DSA can synchronize with the following directory services:
- Microsoft Active Directory
- NetIQ eDirectory
- ApacheDS
- AzureAD
Broker requirements
The Broker requires the following resources:
- Memory: 4 GB of RAM (recommended: 8 GB)
- Java: Java 11 or higher, or Java 8. Java 9 and 10 aren't supported. On Windows, the installer includes a Java runtime. On Linux and Unix, install one first
- .NET Framework: 4.5 or higher and a 64-bit Windows, for the Windows installer
- For the Linux packages, a 64-bit x86 machine. The RPM package needs
java,systemd, and/bin/sh.
Supported platforms
The Broker is tested on the following operating systems:
| OS version | Support level | Comments |
|---|---|---|
| Windows Server 2012 | Tested, fully supported | Provided with installer and configuration wizard |
| Windows Server 2012 R2 | Tested, fully supported | Provided with installer and configuration wizard |
| Windows Server 2016 | Tested, fully supported | Provided with installer and configuration wizard |
| Windows Server 2019 | Tested, fully supported | Provided with installer and configuration wizard |
| Windows Server 2022 | Tested, fully supported | Provided with installer and configuration wizard |
| Windows Server 2025 | Supported | Provided with installer and configuration wizard |
| Windows 7 (32-bit) | Tested, fully supported (only Broker v4.4) | Provided with installer and configuration wizard |
| Windows 7 (64-bit) | Tested, fully supported (only Broker v4.4) | Provided with installer and configuration wizard |
| Windows 8 (all) | Not supported | None |
| Windows 8.1 | Tested, fully supported | Provided with installer and configuration wizard |
| Windows 10 | Tested, fully supported | Provided with installer and configuration wizard |
| Debian and Ubuntu | Supported | DEB package, or tar.gz archive |
| RHEL family (Red Hat Enterprise Linux, Rocky Linux, CentOS) | Supported | RPM package, or tar.gz archive |
| Other Unix/Linux OS | Expected to work | tar.gz archive |
Network requirements
The Broker only opens connections to OpenLM Platform. OpenLM Platform never connects into your network. See the table in Network requirements for the ports to open.
SaaS Agent requirements and deployment guidelines
The SaaS Agent requires the following resources and configuration.
Hardware requirements
The host system needs the following hardware:
- CPU: 4 cores
- Memory: 8 GB of RAM
- Hard drive: 100 GB
- MAC address: Static MAC address (use an elastic network interface (ENI) for cloud servers)
Platform support
The SaaS Agent supports the following platform:
- Windows 10, Windows 11, or Windows Server
- Google Chrome, installed on the host before the agent
- No separate .NET runtime for the SaaS Agent and its app: they include their own
- .NET Framework 4.5 or higher, which the installer checks before it installs
Network requirements
Confirm this network connectivity:
- Internet access is required on the host system
- Outbound port 443 must be open for communication with OpenLM Platform
- The SaaS services you monitor must be reachable from the host system
- Ports 7572 and 9222 through 9231 are used on the host itself. Port 7572 connects the desktop UI to the SaaS Agent service, and the local Chrome uses ports 9222 through 9231. They do not need to be opened at the perimeter, and should be firewalled off from the network
Credential management
When you add a service, sign in in the Chrome window the agent opens, and let Chrome save the password. See Add a monitored service.
Windows account
Run the installer with the Windows account the service will run under. The account needs administrator rights. For the full guidance, see Before you begin.
Required files
The following files must be available on the target system:
- SaaS Agent installer
- A SaaS Agent authorization file, generated in Identity
For the steps, see Install SaaS Agent.
AI Proxy requirements
AI Proxy runs as a Docker Compose stack on a Linux host, not as a desktop installer. The essentials:
- A 64-bit Linux host with Docker Engine and the Docker Compose v2 plugin
- 2 vCPU and 4 GB of RAM minimum (4 vCPU and 8 GB recommended)
- Outbound HTTPS (port 443) to your LLM providers and to OpenLM Platform
For full host, hardware, and network details, see AI Proxy system requirements. To deploy it, see Deploy AI Proxy.
System requirements
OpenLM Router runs as containers on a Linux host in your network. The essentials:
- A 64-bit Linux host, with Docker Engine 20.10 or later and the Docker Compose v2 plugin. Windows hosts are not supported.
- 2 vCPU and 2 GB of RAM minimum (4 vCPU and 4 GB recommended), and 10 GB of disk (20 GB or more recommended).
- MongoDB 7.x and Redis 7.x, which you run as containers beside the Router or take from servers you already operate.
- A Router feature in your OpenLM license.
- Outbound HTTPS to your OpenLM Platform, and access to each license server's
lmgrdport.
For the full requirements, see OpenLM Router system requirements. To deploy it, see Deploy OpenLM Router.
The documentation team might draft this page using a large language model. A technical writer reviews every page and verifies it against the product before publishing it. A human makes the final decision.