---
title: Infrastructural Requirements
description: This page describes the infrastructural requirements for deploying PingOne Recognize on-premise.
component: recognize
page_id: recognize:on-premise:on-premise-infrastructural-requirements
canonical_url: https://docs.pingidentity.com/recognize/on-premise/on-premise-infrastructural-requirements.html
llms_txt: https://docs.pingidentity.com/recognize/llms.txt
docs_for_agents: https://developer.pingidentity.com/build-with-ai/docs-for-agents.md
section_ids:
  kubernetes-version: Kubernetes Version
  postgresql-version: PostgreSQL Version
  s3-compatible-storage: S3-Compatible Storage
  helm-docker-repository: Helm / Docker Repository
---

# Infrastructural Requirements

## Kubernetes Version

Kubernetes version 1.34 and OpenShift 4.14 on GCP are officially supported. Any 1.34.x version should work, but is not officially supported. PingOne Recognize is tested on AWS EKS and GCP GKE, respecting the Kubernetes versions mentioned. Nodes must be x86\_64. ARM architecture is not supported.

## PostgreSQL Version

PostgreSQL 14+ and 15+ are officially supported. A PostgreSQL database is used by the following services to store data:

* Core Daemon Service

* Administration Dashboard Service

## S3-Compatible Storage

An S3-compatible backend (e.g. GCS) is required by the following services to store data:

* Core Daemon Service

## Helm / Docker Repository

The Helm charts are stored in a private Helm repository. Connection details and authentication credentials are provided by PingOne Recognize upon request.

The Helm charts are configured to retrieve Docker images from the PingOne Recognize private `quay.io` repository. Access to the Docker repository must be granted by PingOne Recognize before installing the service.