
# Case management on Google Cloud

Compare documented Case management deployments on Google Cloud, including operating responsibility, licensing and deployment evidence.

Canonical page: https://launchinyourcloud.com/clouds/gcp/case-management/
Catalog revision: 170de95bb7d832897d269051ad4500713acf96a62f3d01bc1d4e649679a56fde




Named clouds have provider-specific evidence. Missing clouds do not establish incompatibility. Preserve edition, account boundary, operating responsibilities and publisher disclosures. Source review dates record human checks, not rebuilds.


## Provider guidance

- Account boundary: Google Cloud project
- Provider group: cloud-infrastructure
- Provider classification: Navigation group for the documented infrastructure offering; read each application path for its actual account boundary. Source: https://docs.cloud.google.com/resource-manager/docs/creating-managing-projects (checked 2026-11-20).
- Network: VPC network
- Identity and access: IAM policies and service accounts
- Installation guidance: Terraform, optionally using Infrastructure Manager for resource provisioning; deploy the application separately.
- Guidance source: https://docs.cloud.google.com/infrastructure-manager/docs/overview
- Guidance reviewed: 2026-11-10


### Private offers

Cloud Marketplace vendors can negotiate a private offer for a specified Cloud Billing account. Check duration, renewal terms and commitment treatment in the actual agreement.
Source: https://docs.cloud.google.com/marketplace/docs/offers/discover-private-offers (reviewed 2026-11-14).

### Private connectivity

Private Service Connect connects VPC consumers to supported managed or producer services. Confirm the actual product endpoint and network/DNS architecture.
Source: https://docs.cloud.google.com/vpc/docs/private-service-connect (reviewed 2026-11-14).

### External workload access

Workload Identity Federation can grant external workloads scoped Google Cloud access without long-lived service-account keys. Validate the trust configuration and exact roles.
Source: https://docs.cloud.google.com/iam/docs/workload-identity-federation (reviewed 2026-11-14).

### Regulated environments

Assured Workloads applies control packages for residency and access boundaries. Confirm supported services, regions and the product deployment; it is not automatic product certification.
Source: https://docs.cloud.google.com/assured-workloads/docs/overview (reviewed 2026-11-14).

The listings below have evidence for Google Cloud. Read each cloud evidence note for the applicable package, edition and support qualifications.

3 listings.


## Hyland OnBase On-Premise

Customer-hosted enterprise content and case platform for document-heavy business processes.

- Listing: https://launchinyourcloud.com/directory/onbase/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial OnBase licenses and separately scoped modules
- Licensing model: commercial-only
- Installation: Vendor or partner-assisted on-premises installation
- Architecture: Customer-hosted enterprise application, document storage and database; deployment sizing and modules require implementation planning.
- Operations: Customer maintains on-premises infrastructure and backups; agree implementation, upgrades and support responsibilities with Hyland or its partner.
- Product website: https://www.hyland.com/
- Source review: 2026-11-13; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

This entry covers licensed OnBase on-premises deployments. Category memberships describe documented platform configurations and integrations, not separately included turnkey applications. Loan tracking, claims integrations and other service solutions need scope and licensing confirmation.

The selected OnBase on-premises product is commercially licensed. Its current on-premises terms restrict production copies and require applicable fees for additional environments and certain access; modules and integrations follow the contracted scope.

Customer-hosted enterprise application, document storage and database; deployment sizing and modules require implementation planning.


### Category fit

- document-management: Enterprise content repository with capture, document workflows and integration with business applications.

- records-management: Retention and destruction workflows for electronic documents; WorkView also supports tracking physical records.

- contract-management: Configurable WorkView contract applications and document workflows; confirm modules and implementation scope.

- financial-application-management: Loan-document tracking and integration with loan origination systems; this supports the document process rather than replacing a lending core.

- case-management: Configurable case applications connect case data, documents, tasks and approvals.

- correspondence-management: Configurable OnBase workflows can store and route correspondence documents with related case work; implementation is solution-specific.

- vendor-supplier-document-management: Vendor case records and supporting documents in WorkView and accounts-payable workflows; not a dedicated supplier-risk service.

- hr-employee-records-management: Employee-file access, applicant-document routing and employee onboarding/offboarding workflows.

- policy-procedure-management: Electronic policy distribution and policy/procedure sign-off workflows in the HR document-management scope.

- claims-management: Document capture and workflows integrated with insurance claims systems; not a replacement for claims adjudication software.

- workflow-automation: Content and case workflows with routing, rules and low-code WorkView applications.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.reveillesoftware.com/solutions/reveille-for-hyland-onbase/ (checked 2026-11-12). Source: https://www.hyland.com/en/partners/reveille (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.reveillesoftware.com/solutions/reveille-for-hyland-onbase/ (checked 2026-11-12). Source: https://www.hyland.com/en/partners/reveille (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.reveillesoftware.com/solutions/reveille-for-hyland-onbase/ (checked 2026-11-12). Source: https://www.hyland.com/en/partners/reveille (checked 2026-11-12). 


### Cloud deployment evidence

- Hyland partner statement on customer-managed OnBase cloud deployments (aws, azure, gcp): https://www.reveillesoftware.com/solutions/reveille-for-hyland-onbase/
  Hyland-authorized integration partner Reveille explicitly describes OnBase 18+ in customer-managed AWS, Azure and Google Cloud environments, separately from OnBase Cloud. This is the partner's compatibility statement, not a Hyland installation guide or cloud-support certification. Confirm the current OnBase release, Windows/database topology, licenses and vendor support agreement; Reveille itself is not required for self-hosting.
  Source type: partner-evidence; reviewed: 2026-11-12; vendor support: not-assessed. Versions: OnBase 18+ in partner statement; confirm current release.

- Hyland identification of Reveille as an authorized integration partner (aws, azure, gcp): https://www.hyland.com/en/partners/reveille
  Hyland identifies Reveille as an authorized build partner for OnBase and other Hyland platforms. This corroborates the source relationship, not an independent certification of every deployment listed by the partner; use its customer-managed-cloud statement together with OnBase installation and commercial requirements.
  Source type: partner-relationship; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- OnBase platform capabilities: https://www.hyland.com/en/solutions/products/onbase

- On-premises product terms: https://legal.hyland.com/pst-on-premise-multi-products

- WorkView business application examples: https://www.hyland.com/en/resources/articles/workview-product-overview

- HR files and policy sign-offs: https://www.hyland.com/en/resources/terminology/human-resources/document-management

- OnBase workflow routing: https://docs.hyland.com/r/OnBase/Workflow/Foundation-23.1/Workflow/Overview/Workflow-Overview

- Correspondence document integration: https://docs.hyland.com/r/OnBase/Application-Client-Connector/Foundation-24.1/Application-Client-Connector/Overview/Introduction

- Loan-document tracking solution: https://community.hyland.com/kb/articles/1332-hyland-services-loan-document-tracking

- Insurance claims integration case study: https://www.hyland.com/en/customers/p-c-insurer

### Licensing sources

- https://legal.hyland.com/pst-on-premise-multi-products

### Infrastructure sources

- https://legal.hyland.com/pst-on-premise-multi-products


### Buyer diligence


Research coverage: 4/12 fields (33%); 4 documented, 0 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The Foundation 26.1 Web Client documents Integration for Single Sign-On and configuration of automatic login. Hyland identity-service authentication is also module-specific; confirm client coverage, identity-provider compatibility and licensed integrations for the selected solution. Scope: OnBase Foundation 26.1 Web Client configuration; not a blanket claim for every module. Source: https://docs.hyland.com/r/OnBase/Web-Server/Foundation-26.1/Web-Server/Configuration/Web.config-Configuration/appSettings?contentId=stz0b9kK0lYB~c4sf1hbkA (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The Foundation 26.1 Web Server is delivered through vendor setup.exe/MSI installation media with documented interactive and silent configuration. Application Server installation is a prerequisite; no public cloud-provisioning template is established by this installer guide. Scope: Vendor-supplied OnBase Web Server installation media, not public IaC. Source: https://docs.hyland.com/r/OnBase/Web-Server/Foundation-26.1/Web-Server/Installation/Installation/Running-the-Installer?contentId=6JGslGq~Cra0GizajFYkbA (reviewed 2026-11-20).

- Minimum footprint / sizing: Documented. Foundation 26.1 lists a 2.4-GHz dual-core minimum, 4 GB RAM for Web Server and 8 GB for 64-bit Application Server, with 16 GB recommended for each. These are dedicated-role requirements; database, files, other modules, HA and workload capacity are additional. Scope: OnBase Foundation 26.1 Web/Application role minima; not the complete solution. Source: https://docs.hyland.com/r/OnBase/Technical-Requirements-Overview-for-New-Installations-and-Upgrades/Foundation-26.1/Technical-Requirements-Overview-for-New-Installations-and-Upgrades/Part-6-Web/Application-Server-and-Core-Services-Hardware-Requirements/64-Bit-Server-Hardware-Requirements?contentId=UToZTDrd9HvkQpjb7tURJQ (reviewed 2026-11-20).

- License pricing: Documented. The current on-premises terms distinguish production, disaster-recovery and separately licensed non-production use. Confirm the purchased product/client/API permissions and environments in the agreement; these terms do not supply a public total price. Scope: OnBase on-premises terms v1.2, effective 2026-06-23; customer order may add conditions. Source: https://legal.hyland.com/pst-on-premise-multi-products (reviewed 2026-11-16).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## OpenCRVS

Open-source civil registration software for birth, death and related registration workflows.

- Listing: https://launchinyourcloud.com/directory/opencrvs/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, gcp, hetzner
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GNU LGPL licence for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Terraform; Kubernetes manifests
- Architecture: OpenCRVS application and persistent services on the project's named-cloud Kubernetes infrastructure templates.
- Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
- Product website: https://www.opencrvs.org
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

A country configuration, institutional identity, registration rules and integrations must be supplied. Infrastructure templates and the application release are separate, and public source does not confer authority to issue civil records.

GNU LGPL licence for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

OpenCRVS application and persistent services on the project's named-cloud Kubernetes infrastructure templates. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- case-management: Open-source civil registration software for birth, death and related registration workflows.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://raw.githubusercontent.com/opencrvs/cloud-infrastructure/main/terraform-templates/amazon-web-services/README.md (checked 2026-11-19). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://raw.githubusercontent.com/opencrvs/cloud-infrastructure/main/terraform-templates/google-cloud-platform/README.md (checked 2026-11-19). 

- hetzner: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://raw.githubusercontent.com/opencrvs/cloud-infrastructure/main/terraform-templates/hetzner-cloud/k8s_cluster.tf (checked 2026-11-19). 


### Cloud deployment evidence

- AWS EKS Terraform (aws): https://raw.githubusercontent.com/opencrvs/cloud-infrastructure/main/terraform-templates/amazon-web-services/README.md
  OpenCRVS application and persistent services on the project's named-cloud Kubernetes infrastructure templates. A country configuration, institutional identity, registration rules and integrations must be supplied. Infrastructure templates and the application release are separate, and public source does not confer authority to issue civil records.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- GCP GKE Terraform (gcp): https://raw.githubusercontent.com/opencrvs/cloud-infrastructure/main/terraform-templates/google-cloud-platform/README.md
  OpenCRVS application and persistent services on the project's named-cloud Kubernetes infrastructure templates. A country configuration, institutional identity, registration rules and integrations must be supplied. Infrastructure templates and the application release are separate, and public source does not confer authority to issue civil records.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Hetzner K8s Terraform (hetzner): https://raw.githubusercontent.com/opencrvs/cloud-infrastructure/main/terraform-templates/hetzner-cloud/k8s_cluster.tf
  OpenCRVS application and persistent services on the project's named-cloud Kubernetes infrastructure templates. A country configuration, institutional identity, registration rules and integrations must be supplied. Infrastructure templates and the application release are separate, and public source does not confer authority to issue civil records.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes rikukissa, euanmillar, makelicious, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee.

Reviewed 2026-11-19.

- Community, governance or adoption evidence: https://github.com/opencrvs/opencrvs-core/graphs/contributors

- Upstream project: https://github.com/opencrvs/opencrvs-core

### Sources

- AWS EKS Terraform: https://raw.githubusercontent.com/opencrvs/cloud-infrastructure/main/terraform-templates/amazon-web-services/README.md

- GCP GKE Terraform: https://raw.githubusercontent.com/opencrvs/cloud-infrastructure/main/terraform-templates/google-cloud-platform/README.md

- Hetzner K8s Terraform: https://raw.githubusercontent.com/opencrvs/cloud-infrastructure/main/terraform-templates/hetzner-cloud/k8s_cluster.tf

- MPL-2.0: https://raw.githubusercontent.com/opencrvs/opencrvs-core/master/LICENSE

- Releases: https://github.com/opencrvs/opencrvs-core/releases

### Licensing sources

- https://raw.githubusercontent.com/opencrvs/opencrvs-core/master/LICENSE

### Infrastructure sources

- https://raw.githubusercontent.com/opencrvs/cloud-infrastructure/main/terraform-templates/amazon-web-services/README.md

- https://raw.githubusercontent.com/opencrvs/cloud-infrastructure/main/terraform-templates/google-cloud-platform/README.md

- https://raw.githubusercontent.com/opencrvs/cloud-infrastructure/main/terraform-templates/hetzner-cloud/k8s_cluster.tf


### Buyer diligence


Research coverage: 4/12 fields (33%); 3 documented, 1 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Sources checked — unresolved. The server-hosting guide distinguishes production user two-factor codes, test accounts and government VPN access, but does not establish a supported external user SAML/OIDC login path. VPN/server identity and the application authentication service are separate; verify the selected current release and country configuration. Scope: OpenCRVS enterprise/user federation remains unconfirmed. Source: https://documentation.opencrvs.org/v1.7/setup/3.-installation/3.3-set-up-a-server-hosted-environment (reviewed 2026-11-21).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The reviewed source supplies deployment configuration for OpenCRVS application and persistent services on the project's named-cloud Kubernetes infrastructure templates. Set organization-specific secrets, networking, storage and compatible image versions before use. Scope: Reviewed deployment source collection; application images and infrastructure components have separate versions. Source: https://raw.githubusercontent.com/opencrvs/cloud-infrastructure/main/terraform-templates/amazon-web-services/README.md (reviewed 2026-11-19). Deployment artifact: https://github.com/opencrvs/cloud-infrastructure/tree/main/terraform-templates/amazon-web-services. Artifact reference: main (moving branch).

- Minimum footprint / sizing: Documented. The v1.7 guide lists production/staging at 8 CPUs/16 GB RAM with storage calculated from registration volume/attachments, versus development/QA at 4 CPUs/16 GB/320 GB. It specifies x86_64 Ubuntu 24.04 and separate backup requirements. Revalidate the selected release, clustering, throughput and recovery rather than applying this as an unrestricted current HA minimum. Scope: Versioned OpenCRVS v1.7 environment-specific baseline; current deployment/version sizing separate. Source: https://documentation.opencrvs.org/v1.7/setup/3.-installation/3.3-set-up-a-server-hosted-environment (reviewed 2026-11-21).

- License pricing: Documented. GNU LGPL licence for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: OpenCRVS; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/opencrvs/opencrvs-core/master/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Pega Platform Client-Managed

Commercial workflow and case-management platform installed in customer-managed Kubernetes infrastructure.

- Listing: https://launchinyourcloud.com/directory/pega-platform-client-managed/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.
- Licensing model: commercial-only
- Installation: Helm / Kubernetes operator; Kubernetes manifests
- Architecture: Pega application Helm charts, supported database and runtime dependencies on EKS, AKS or GKE.
- Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
- Product website: https://docs.pega.com/bundle/platform/page/platform/deployment/client-managed-cloud/containerized-deployments-kubernetes.html
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

This listing covers the platform established by the deployment runbooks. It does not imply that a separately licensed Pega Government Platform package or municipal-permit application is installed. The chart's open-source licence does not license the Pega runtime.

Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.

Pega application Helm charts, supported database and runtime dependencies on EKS, AKS or GKE. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- workflow-automation: Commercial workflow and case-management platform installed in customer-managed Kubernetes infrastructure.

- case-management: Commercial workflow and case-management platform installed in customer-managed Kubernetes infrastructure.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://raw.githubusercontent.com/pegasystems/pega-helm-charts/master/docs/Deploying-Pega-on-EKS.md (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://raw.githubusercontent.com/pegasystems/pega-helm-charts/master/docs/Deploying-Pega-on-AKS.md (checked 2026-11-19). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://raw.githubusercontent.com/pegasystems/pega-helm-charts/master/docs/Deploying-Pega-on-GKE.md (checked 2026-11-19). 


### Cloud deployment evidence

- EKS Runbook (aws): https://raw.githubusercontent.com/pegasystems/pega-helm-charts/master/docs/Deploying-Pega-on-EKS.md
  Pega application Helm charts, supported database and runtime dependencies on EKS, AKS or GKE. This listing covers the platform established by the deployment runbooks. It does not imply that a separately licensed Pega Government Platform package or municipal-permit application is installed. The chart's open-source licence does not license the Pega runtime.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- AKS Runbook (azure): https://raw.githubusercontent.com/pegasystems/pega-helm-charts/master/docs/Deploying-Pega-on-AKS.md
  Pega application Helm charts, supported database and runtime dependencies on EKS, AKS or GKE. This listing covers the platform established by the deployment runbooks. It does not imply that a separately licensed Pega Government Platform package or municipal-permit application is installed. The chart's open-source licence does not license the Pega runtime.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- GKE Runbook (gcp): https://raw.githubusercontent.com/pegasystems/pega-helm-charts/master/docs/Deploying-Pega-on-GKE.md
  Pega application Helm charts, supported database and runtime dependencies on EKS, AKS or GKE. This listing covers the platform established by the deployment runbooks. It does not imply that a separately licensed Pega Government Platform package or municipal-permit application is installed. The chart's open-source licence does not license the Pega runtime.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- EKS Runbook: https://raw.githubusercontent.com/pegasystems/pega-helm-charts/master/docs/Deploying-Pega-on-EKS.md

- AKS Runbook: https://raw.githubusercontent.com/pegasystems/pega-helm-charts/master/docs/Deploying-Pega-on-AKS.md

- GKE Runbook: https://raw.githubusercontent.com/pegasystems/pega-helm-charts/master/docs/Deploying-Pega-on-GKE.md

- Pega Terms: https://www.pega.com/terms

- PGP Release Notes: https://docs.pega.com/bundle/pega-government-platform/page/pega-government-platform/releasenotes/constellation/cons-newfeatures.html

- Helm Releases: https://github.com/pegasystems/pega-helm-charts/releases

### Licensing sources

- https://www.pega.com/terms

### Infrastructure sources

- https://raw.githubusercontent.com/pegasystems/pega-helm-charts/master/docs/Deploying-Pega-on-EKS.md

- https://raw.githubusercontent.com/pegasystems/pega-helm-charts/master/docs/Deploying-Pega-on-AKS.md

- https://raw.githubusercontent.com/pegasystems/pega-helm-charts/master/docs/Deploying-Pega-on-GKE.md


### Buyer diligence


Research coverage: 4/12 fields (33%); 4 documented, 0 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. Pega Platform documents SAML 2.0 and OIDC authentication services for user SSO. A security administrator creates the service and configures identity/claim mapping and any operator provisioning; token credentials for API integrations are a separate authentication type. Scope: Pega Platform application user federation; confirm the chosen client-managed release and identity-service configuration. Source: https://docs.pega.com/bundle/platform/page/platform/security/create-authentication-service.html (reviewed 2026-11-20). Supporting source: Public documentation API with article body — https://docs-be.pega.com/api/bundle/platform/page/platform/security/create-authentication-service.html.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. Pega publishes Helm charts and EKS/AKS/GKE runbooks for client-managed Kubernetes. The EKS guide requires separately obtained Pega images, registry access and a supported database. Match chart, application, search and database versions; chart source access does not grant platform software rights. Scope: Client-managed licensed platform deployment; no ECS support inferred from generic container capability. Source: https://github.com/pegasystems/pega-helm-charts/blob/master/docs/Deploying-Pega-on-EKS.md (reviewed 2026-11-20). Deployment artifact: https://github.com/pegasystems/pega-helm-charts/tree/master/charts/pega. Artifact reference: master (moving branch); select a chart compatible with the licensed Pega release.

- Minimum footprint / sizing: Documented. The reviewed upstream chart gives the web-user tier a per-pod request of 3 CPU and 12 GiB memory, with limits of 4 CPU and 12 GiB. These are configurable chart defaults; background/search tiers, database, autoscaling, replica counts and cluster overhead are additional. Scope: Moving chart web-tier defaults, not a vendor-certified minimum or a complete 100-user/1-TB HA sizing. Source: https://github.com/pegasystems/pega-helm-charts/blob/master/charts/pega/values.yaml (reviewed 2026-11-20).

- License pricing: Documented. Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation. Scope: Pega Platform Client-Managed; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://www.pega.com/terms (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.






