System requirements

To plan the infrastructure for OpenLM Platform, check these requirements. They apply to every deployment path.

Where path-specific sizing lives

The authoritative sizing reference for each path is the Requirements page inside its deployment guide: Platform as VM, On-premises machines, AWS, and Azure. Start there to plan a specific deployment. This page is the cross-path summary.

What OpenLM Platform needs

OpenLM Platform requires a Kubernetes cluster and four infrastructure services:

Component	What it is	Why OpenLM Platform needs it
Kubernetes cluster	Container orchestration	Runs all 100+ microservices and handles scheduling and self-healing
SQL database	Either a single MSSQL instance, or MariaDB/MySQL + PostgreSQL	Stores identity, operational, and reporting data.
MongoDB	Document database	Stores platform configuration, state, and data for some of the services
Kafka	Message broker	Event streaming between microservices
Redis	In-memory cache	Caching and session management

OpenLM Platform needs only the endpoint of each service. Whatever the deployment path, a service can be cloud-managed or run in the cluster from the charts in the deployment package. For what is available in each environment, see Deployment paths. For details on the two SQL configurations, see SQL database options.

Baseline resource requirements

Across all deployment paths, OpenLM Platform needs roughly the following resources:

Resource	Baseline
Compute	8 nodes, 60 vCPUs, 136 GB RAM
Storage	300 GB SSD for data services, 50 GB per standard node
Kubernetes	A supported distribution with ingress and TLS (EKS for AWS, AKS for Azure, any CNCF-conformant distribution or Red Hat OpenShift for on-premises)
Networking	HTTPS (443) and HTTP (80) ingress for agents and users, outbound access to public.ecr.aws/r3q3q2f4, docker.tyk.io, and docker.io for container images

These numbers represent a stable baseline for small-to-medium production load. Each deployment path's requirements page in the deployment guide covers detailed node layouts and managed service sizing.

Shared requirements

The following requirements apply to all deployment paths:

• Persistent storage classes must be available for stateful workloads (databases, Kafka).
• TLS termination at the ingress layer with a certificate trusted by all agent machines.
• Validate sizing against expected Broker counts, user volume, report volume, and data retention.

Validate sizing before deployment

The preceding resource numbers are baselines for small-to-medium production load. Validate them against your expected Broker counts, user volume, report volume, and data retention.