
# Case management on Azure

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

Canonical page: https://launchinyourcloud.com/clouds/azure/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: Subscription and resource group
- Provider group: cloud-infrastructure
- Provider classification: Navigation group for the documented infrastructure offering; read each application path for its actual account boundary. Source: https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/manage-resource-groups-portal (checked 2026-11-20).
- Network: Virtual Network (VNet)
- Identity and access: Microsoft Entra identities and Azure RBAC
- Installation guidance: Bicep/ARM templates or Terraform; review deployment scope and role assignments.
- Guidance source: https://learn.microsoft.com/en-us/azure/azure-resource-manager/bicep/overview
- Guidance reviewed: 2026-11-10


### Private offers

Microsoft Marketplace private offers negotiate product pricing and terms. Confirm the exact offer, billing scope and benefit eligibility rather than assuming all purchases count toward a commitment.
Source: https://learn.microsoft.com/en-us/marketplace/private-offers-overview (reviewed 2026-11-14).

### Private connectivity

Azure Private Link uses private endpoints in a virtual network for supported Azure and partner services. Check application support, DNS and service availability.
Source: https://learn.microsoft.com/en-us/azure/private-link/private-link-overview (reviewed 2026-11-14).

### Cross-tenant operations

Azure Lighthouse supports delegated management with customer-controlled scopes and actions. Agree the roles, audit requirements and revocation plan for the selected vendor.
Source: https://learn.microsoft.com/en-us/azure/lighthouse/overview (reviewed 2026-11-14).

### Government environments

Azure Government uses isolated US datacenters and networks. Commercial Azure documentation alone does not establish a product path or compliance in Government.
Source: https://learn.microsoft.com/en-us/azure/azure-government/documentation-government-welcome (reviewed 2026-11-14).

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

5 listings.


## Flowable Enterprise Platform

Commercial workflow and case-management platform with vendor Terraform and Helm deployments.

- Listing: https://launchinyourcloud.com/directory/flowable-platform/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure
- 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: Terraform; Kubernetes manifests
- Architecture: Flowable application services, database, search and persistent storage on EKS or AKS.
- 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://documentation.flowable.com/latest/admin/cloud-deployment/terraform-aws
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The Apache-licensed open-source engine and commercial Work/Platform distribution are different scopes. Supplier-onboarding examples require application modeling and do not establish a packaged supplier-qualification system. The commercial application requires its own licence file.

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

Flowable application services, database, search and persistent storage on EKS or AKS. 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 with vendor Terraform and Helm deployments.

- case-management: Commercial workflow and case-management platform with vendor Terraform and Helm deployments.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://documentation.flowable.com/latest/admin/cloud-deployment/terraform-aws (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://documentation.flowable.com/latest/admin/cloud-deployment/terraform-azure (checked 2026-11-19). 


### Cloud deployment evidence

- AWS Terraform (aws): https://documentation.flowable.com/latest/admin/cloud-deployment/terraform-aws
  Flowable application services, database, search and persistent storage on EKS or AKS. The Apache-licensed open-source engine and commercial Work/Platform distribution are different scopes. Supplier-onboarding examples require application modeling and do not establish a packaged supplier-qualification system. The commercial application requires its own licence file.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Azure Terraform (azure): https://documentation.flowable.com/latest/admin/cloud-deployment/terraform-azure
  Flowable application services, database, search and persistent storage on EKS or AKS. The Apache-licensed open-source engine and commercial Work/Platform distribution are different scopes. Supplier-onboarding examples require application modeling and do not establish a packaged supplier-qualification system. The commercial application requires its own licence file.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- AWS Terraform: https://documentation.flowable.com/latest/admin/cloud-deployment/terraform-aws

- Azure Terraform: https://documentation.flowable.com/latest/admin/cloud-deployment/terraform-azure

- Helm Guide: https://documentation.flowable.com/latest/admin/cloud-deployment/helm

- Supplier Onboarding: https://www.flowable.com/solutions/manufacturing

- Supplier LEAN Alert: https://www.flowable.com/success-stories/great-dane/digitalized-automated-order-lifecycle-management-manufacturing

- Case Management: https://www.flowable.com/solutions/case-management

- License File Renewal: https://documentation.flowable.com/latest/admin/maintenance/license-renewal

- Trial Terms: https://www.flowable.com/flowable-trial-terms-of-use

- Latest Releases (2026.1.5.1): https://documentation.flowable.com/latest/admin/release-notes/latest

- 2026.1.x Release Notes: https://documentation.flowable.com/latest/admin/release-notes/2026.1.0-release

### Licensing sources

- https://documentation.flowable.com/latest/admin/maintenance/license-renewal

- https://www.flowable.com/flowable-trial-terms-of-use

### Infrastructure sources

- https://documentation.flowable.com/latest/admin/cloud-deployment/terraform-aws

- https://documentation.flowable.com/latest/admin/cloud-deployment/terraform-azure


### 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 Enterprise guide configures user SSO for Work/Engage, Design and Hub using OAuth 2.0 with Keycloak, including separate clients, redirect URIs and application security settings. This is application-specific configuration, not automatic SSO from merely installing Spring Security. Scope: Flowable Enterprise applications; validate current product and IdP versions and replace demonstration credentials. Source: https://documentation.flowable.com/latest/howto/howto/howto-oauth2-keycloak (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. Flowable publishes authenticated Helm charts and separate AWS/Azure Terraform guides. The chart configures licensed product images, database and search connections, secrets and persistent services; repository credentials and compatible chart/application versions are required. Scope: Enterprise Kubernetes chart and deployment guides; not an unrestricted open-source Flowable engine entitlement. Source: https://documentation.flowable.com/latest/admin/cloud-deployment/helm (reviewed 2026-11-20). Deployment artifact: https://repo.flowable.com/flowable-helm. Artifact reference: authenticated Helm repository; select a chart matching the licensed product release. Supporting source: AWS Terraform guide — https://documentation.flowable.com/latest/admin/cloud-deployment/terraform-aws.

- Minimum footprint / sizing: Documented. The Enterprise requirements give Flowable Work a production minimum of 2 CPU and 8 GB RAM. Application disk guidance differs for files persisted in the database (10 GB) versus the filesystem (100 GB). The separate database minimum without file BLOBs is 4 CPU, 16 GB RAM and 100 GB disk; HA generally needs at least two application instances plus separately sized search, database and storage services. Scope: Product-specific average-scenario guidance; per-application figures are not a total HA footprint. Source: https://documentation.flowable.com/latest/admin/installs/system-requirements (reviewed 2026-11-20).

- License pricing: Documented. Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation. Scope: Flowable Enterprise Platform; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://documentation.flowable.com/latest/admin/maintenance/license-renewal (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## 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.







## Laserfiche Self-Hosted

Self-hosted document and records platform with forms and configurable business process automation.

- Listing: https://launchinyourcloud.com/directory/laserfiche-self-hosted/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial self-hosted software; license and module entitlements apply
- Licensing model: commercial-only
- Installation: Licensed Laserfiche 12 Windows installers
- Architecture: Persistent Windows Server applications, repository storage and database; current support guidance excludes containerized self-hosted applications.
- Operations: Customer operates supported Windows servers, repository/database backups and product updates; follow the chosen modules installation requirements.
- Product website: https://www.laserfiche.com/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

Scope is the self-hosted product. Use-case pages describe platform workflows; confirm availability and licensing for the chosen version and modules. The current support matrix requires Windows Server Desktop Experience and explicitly excludes Docker and Kubernetes deployment for self-hosted applications.

This record covers the commercial self-hosted Laserfiche product. Installation and activation require licensed application entitlements; marketplace templates do not confer a license to the underlying platform.

Persistent Windows Server applications, repository storage and database; current support guidance excludes containerized self-hosted applications.


### Category fit

- document-management: Repository, capture, search and document process automation on customer-operated servers.

- records-management: Document lifecycle, retention, access controls and disposition; configure schedules for the organization.

- contract-management: Configurable contract creation, approval and records workflows; confirm the selected self-hosted modules.

- financial-application-management: Document routing and automation for loan applications, illustrated by the vendor banking case study.

- case-management: Forms, repository content and process workflows for service case management; implementation is configured to the case process.

- hr-employee-records-management: Employee records, onboarding approvals and access controls for HR processes.

- claims-management: Low-code claims review and approval workflows; does not establish an insurance policy or adjudication core.

- workflow-automation: Forms and document workflows for routing, approvals and task automation.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://mccmeetings.blob.core.usgovcloudapi.net/nwpraguemn-pubu/MEET-Packet-7ead60072b1d4ae485774089b3fea95c.pdf (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://mccmeetings.blob.core.usgovcloudapi.net/nwpraguemn-pubu/MEET-Packet-7ead60072b1d4ae485774089b3fea95c.pdf (checked 2026-11-12). 


### Cloud deployment evidence

- Laserfiche reseller installation terms for customer AWS and Azure environments (aws, azure): https://mccmeetings.blob.core.usgovcloudapi.net/nwpraguemn-pubu/MEET-Packet-7ead60072b1d4ae485774089b3fea95c.pdf
  Cities Digital installation terms, published in the municipal meeting packet on PDF page 40, explicitly cover new Azure or AWS environments and exclude Laserfiche Cloud from that section. The client supplies Windows, SQL Server and network configuration and validates workflows. This documents a reseller-assisted self-hosted path; confirm the current server version, license, support scope and implementation fees.
  Source type: public-procurement-record; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Self-hosted installation overview: https://doc.laserfiche.com/laserfiche.documentation/12/userguide/en-us/content/install-overview.htm

- Current operating system and deployment support: https://support.laserfiche.com/kb/1012418/raw

- Business process solutions: https://www.laserfiche.com/solutions/

- Document and records capabilities: https://www.laserfiche.com/products/document-and-records-management/

- Loan application automation case study: https://www.laserfiche.com/resources/customer-stories/growin-bank-expedites-loan/

- Insurance claims workflows: https://www.laserfiche.com/solutions/financial-services/insurance/

- Software license agreement and legal resources: https://www.laserfiche.com/legal/

### Licensing sources

- https://doc.laserfiche.com/laserfiche.documentation/12/userguide/en-us/content/install-overview.htm

- https://www.laserfiche.com/legal/

### Infrastructure sources

- https://doc.laserfiche.com/laserfiche.documentation/12/userguide/en-us/content/install-overview.htm

- https://support.laserfiche.com/kb/1012418/raw


### Buyer diligence


Research coverage: 4/12 fields (33%); 2 documented, 2 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. Laserfiche 12 Directory Server accepts SAML 2.0 identity providers using imported metadata and claim mappings. Configure the licensing site, client integrations and local-account policy; this does not establish every optional module or Cloud entitlement. Scope: Laserfiche 12 self-hosted Directory Server federation. Source: https://doc.laserfiche.com/laserfiche.documentation/12/userguide/en-us/content/admin-lfds-saml-identity-provider.htm (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. Laserfiche 12 uses a product installer that selects applications, detects installed versions and offers updates. Follow new-installation, repository and system-specification instructions; this page is not a public IaC package. Scope: Laserfiche self-hosted version 12 installer and initial configuration. Source: https://doc.laserfiche.com/laserfiche.documentation/12/userguide/en-us/content/install-overview.htm (reviewed 2026-11-16).

- Minimum footprint / sizing: Sources checked — unresolved. The current supported-platforms list establishes Windows Server and database compatibility, but does not supply a complete Laserfiche 12 CPU/RAM topology. Public numeric checklists found cover version 11 or older. Obtain a version-12 component and HA sizing design rather than applying those legacy minima. Scope: Laserfiche 12 self-hosted hardware sizing unresolved. Source: https://support.laserfiche.com/kb/1012418/pdf (reviewed 2026-11-20). Supporting source: Older version-11 server minimum is not a version-12 sizing recommendation — https://doc.laserfiche.com/laserfiche.documentation/11/administration/en-us/Subsystems/LFAdmin/Content/Installation/Laserfiche_Server_%28United%29_pre_check.htm.

- License pricing: Sources checked — unresolved. The self-hosted Directory Server workflow requires a licensing site registering the repository server. The reviewed integration documentation does not establish current licence prices, user metrics or maintenance terms; obtain an on-premises quote rather than applying Laserfiche Cloud prices. Scope: Self-hosted licence delivery established; commercial pricing and terms unresolved. Source: https://doc.laserfiche.com/laserfiche.documentation/12/userguide/en-us/content/config-lfm-configuration-page-connection.htm (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Merative Cúram Social Program Management

Commercial social-program case-management software with customer Kubernetes runbooks.

- Listing: https://launchinyourcloud.com/directory/merative-spm/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure
- 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: Kubernetes manifests
- Architecture: Licensed Cúram application and supported data services on EKS or AKS.
- 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://github.com/merative/curam-kubernetes
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The public containerization assets are not the commercial application licence. Keep runbook/container-packaging releases separate from the licensed Cúram release and validate the supported database/runtime matrix.

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

Licensed Cúram application and supported data services on EKS or AKS. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- case-management: Commercial social-program case-management software with customer Kubernetes runbooks.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://raw.githubusercontent.com/merative/curam-kubernetes/main/src/pages/architecture/eks-consideration/security.mdx (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://raw.githubusercontent.com/merative/curam-kubernetes/main/src/pages/architecture/aks-consideration/security.mdx (checked 2026-11-19). 


### Cloud deployment evidence

- EKS Source (aws): https://raw.githubusercontent.com/merative/curam-kubernetes/main/src/pages/architecture/eks-consideration/security.mdx
  Licensed Cúram application and supported data services on EKS or AKS. The public containerization assets are not the commercial application licence. Keep runbook/container-packaging releases separate from the licensed Cúram release and validate the supported database/runtime matrix.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- AKS Source (azure): https://raw.githubusercontent.com/merative/curam-kubernetes/main/src/pages/architecture/aks-consideration/security.mdx
  Licensed Cúram application and supported data services on EKS or AKS. The public containerization assets are not the commercial application licence. Keep runbook/container-packaging releases separate from the licensed Cúram release and validate the supported database/runtime matrix.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- EKS Source: https://raw.githubusercontent.com/merative/curam-kubernetes/main/src/pages/architecture/eks-consideration/security.mdx

- AKS Source: https://raw.githubusercontent.com/merative/curam-kubernetes/main/src/pages/architecture/aks-consideration/security.mdx

- Curam K8s README: https://github.com/merative/curam-kubernetes/blob/main/README.md

- EKS Guide: https://merative.github.io/curam-kubernetes/architecture/eks-consideration/security/

- AKS Guide: https://merative.github.io/curam-kubernetes/architecture/aks-consideration/security/

- Cúram Site: https://www.curaminnovations.com/

- Merative Terms: https://www.merative.com/terms

- Cúram K8s Releases: https://github.com/merative/curam-kubernetes/releases

### Licensing sources

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

### Infrastructure sources

- https://raw.githubusercontent.com/merative/curam-kubernetes/main/src/pages/architecture/eks-consideration/security.mdx

- https://raw.githubusercontent.com/merative/curam-kubernetes/main/src/pages/architecture/aks-consideration/security.mdx


### Buyer diligence


Research coverage: 4/12 fields (33%); 1 documented, 3 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 chart includes an optional Keycloak/Liberty OIDC configuration for application paths, but its sample sets signatureAlgorithm to none. A secure, release-matched provider configuration, token-validation policy and supported login flow were not established. Kubernetes IAM authentication and older Universal Access portal examples do not settle current caseworker SSO. Scope: Cúram application identity candidate; secure production configuration and release support remain unconfirmed. Source: https://github.com/merative/curam-kubernetes/blob/main/helm-charts/apps/templates/configmaps/configmap-oidc.yaml (reviewed 2026-11-21).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Sources checked — unresolved. The public repository documents Kubernetes deployment and cloud architecture. Its Apache-2.0 documentation/assets do not establish access to a licensed, versioned Cúram application chart or image. Scope: Cúram deployment documentation versus licensed runtime artifacts. Source: https://github.com/merative/curam-kubernetes/blob/main/README.md (reviewed 2026-11-19).

- Minimum footprint / sizing: Documented. The active chart defaults enable the Cúram application with pod requests of 1 CPU/2.5 GiB and limits of 1.5 CPU/3 GiB; deployment templates consume these values. They exclude database, messaging, batch, other applications, OpenShift/Kubernetes overhead, replicas and persistent data. Commented examples are not counted as active defaults. Scope: Moving vendor Cúram chart application-pod defaults, not full production/HA capacity. Source: https://github.com/merative/curam-kubernetes/blob/main/helm-charts/apps/values.yaml (reviewed 2026-11-21). Supporting source: Resource-consuming deployment template — https://github.com/merative/curam-kubernetes/blob/main/helm-charts/apps/templates/deployment-producer.yaml.

- License pricing: Sources checked — unresolved. Current Cúram deployment assets do not establish the customer’s commercial runtime agreement or price; historical Merative website terms and the Apache-licensed deployment repository are separate scopes. Scope: Selected self-managed application or customer-cloud service; contract confirmation required. Source: https://www.curaminnovations.com/ (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.






