Requirements

	Standard Stack#	Custom Stack†#
Operating System	Docker / Containers (official dotCMS image)	Custom Docker Image
Orchestrator	Docker Compose on Docker CE Linux Kubernetes	Custom Orchestrator
Application Server	Tomcat 9 (bundled)	Tomcat 9
JVM	Java 25 (bundled)	Java 25
Database	PostgreSQL 18+ Amazon RDS for PostgreSQL 18+ The `pgvector` extension is required for dotAI features.	PostgreSQL 18+ Amazon RDS for PostgreSQL 18+
Search	OpenSearch 1.3.x (current) OpenSearch 3.8.x (migration target; required from Q1 2027)* AWS OpenSearch Service (matching version)
Cache / Pub-Sub	Redis Valkey
Hardware	Multi-Core Processor 8+ GB RAM (Dedicated) 100 GB Disk
Client Browser	Evergreen versions of: Microsoft Edge Chrome Firefox
Authentication	Built-in single sign-on (dotAuth)‡: OpenID Connect / OAuth 2.0 SAML 2.0 Headless token exchange (OIDC `id_token`) Compatible with standards-based identity providers such as Microsoft Entra ID, ADFS, Okta, Google Workspace, Auth0, Keycloak, and Ping.

*	dotCMS currently runs on OpenSearch 1.3.x. A phased, zero-downtime migration to OpenSearch 3.x is available now, and OpenSearch 3.x will be required starting in Q1 2027. We recommend planning your migration early. See the OpenSearch Migration Guide and the OpenSearch Migration Reference.
†	dotCMS provides support for environments that meet these requirements for an additional cost.
‡	Available in dotCMS 26.08.24-01 and later. Identity provider endpoints must use HTTPS and be reachable from the dotCMS server; OIDC providers must publish a standard discovery document (`/.well-known/openid-configuration`). By default, identity providers on private or internal network addresses are blocked. Native dotCMS login remains available as an administrator fallback.