
# Case management on AWS

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

Canonical page: https://launchinyourcloud.com/clouds/aws/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: AWS account
- 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.aws.amazon.com/accounts/latest/reference/getting-started.html (checked 2026-11-20).
- Network: VPC
- Identity and access: IAM roles and policies
- Installation guidance: CloudFormation or Terraform; review stack changes and requested IAM permissions.
- Guidance source: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/Welcome.html
- Guidance reviewed: 2026-11-10


### Private offers

AWS Marketplace private offers can contain negotiated pricing and terms for a buyer account. Confirm the product delivery model and your agreement; commitment credit is not established by a directory badge.
Source: https://docs.aws.amazon.com/marketplace/latest/buyerguide/buyer-private-offers-subscribing.html (reviewed 2026-11-14).

### Private connectivity

PrivateLink provides private endpoints to supported services and resources across VPC/account boundaries. Confirm that the selected product exposes a compatible endpoint service.
Source: https://docs.aws.amazon.com/vpc/latest/privatelink/what-is-privatelink.html (reviewed 2026-11-14).

### Cross-account operations

Use an IAM role with scoped permissions and a third-party external ID where applicable. Review the trust principal, support access and revocation separately from installation access.
Source: https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_common-scenarios_third-party.html (reviewed 2026-11-14).

### Government environments

AWS GovCloud (US) is a distinct isolated-region environment. A commercial-region product deployment does not establish availability or certification there.
Source: https://docs.aws.amazon.com/govcloud-us/latest/UserGuide/whatis.html (reviewed 2026-11-14).

The listings below have evidence for Amazon Web Services. Read each cloud evidence note for the applicable package, edition and support qualifications.

10 listings.


## CiviCRM with CiviCase and CiviGrant

Self-hosted constituent management with configurable case activities and grant application tracking.

- Listing: https://launchinyourcloud.com/directory/civicrm/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Open-source; hosting and implementation separately arranged
- Licensing model: open-source
- Installation: Standalone installation or supported CMS integration
- Architecture: Customer-operated PHP application and MySQL/MariaDB database
- Operations: Customer or service provider maintains the installation, extensions, database and updates.
- Product website: https://civicrm.org/
- Source review: 2026-11-19; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

CiviCase coordinates sequences of activities, case roles and follow-up. CiviGrant supports organizations distributing funds, including applications, amounts and reporting; more complex grant pathways can combine it with CiviCase. This is a configurable civic/nonprofit platform, not an assertion of enterprise case-management or research-administration parity. CiviCRM 6.20.1 and 6.16.9 ESR fix 29 advisories, CIVI-SA-2026-53 through -81, spanning SQL injection, authorization and ACL bypass, XSS, information disclosure and data-integrity issues. CIVI-SA-2026-81 is Critical and could reverse Afform relationship-permission flags. Upgrade the installed supported line to 6.20.1, 6.16.9 ESR or later. The 6.20.1 synopsis reports no schema or API change and no configuration action.

CiviCRM identifies its current core as AGPLv3 with the CiviCRM Licensing Exception. This record covers the documented CiviCase/CiviGrant setup; separately selected extensions and services must be checked individually rather than assumed to share the same license.

The listed self-hosted installation uses application servers, database services or container workloads. This classification covers that deployment option; managed storage or a vendor control plane does not make the application serverless.


### Category fit

- case-management: CiviCase coordinates case roles, sequences of activities and follow-up for civic or nonprofit workflows; enterprise case-management feature parity is not asserted.

- grants-management: CiviGrant tracks outgoing grant applications, requested and awarded amounts, attachments and reporting; complex grant pathways may combine it with CiviCase.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://aws.amazon.com/blogs/publicsector/managing-nonprofit-members-donors-civicrm-aws/ (checked 2026-11-12). 


### Cloud deployment evidence

- Customer-deployed CiviCRM on AWS reference architecture (aws): https://aws.amazon.com/blogs/publicsector/managing-nonprofit-members-donors-civicrm-aws/
  AWS documents deploying CiviCRM with WordPress in the customer account, including an EC2 application tier, load balancing, Auto Scaling and an RDS database. The walkthrough is from 2023; use current supported WordPress, PHP, database and CiviCRM releases and confirm the required CiviCase/CiviGrant components. This is a full application deployment rather than an RDS integration alone.
  Source type: provider-guide; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Installation requirements: https://docs.civicrm.org/installation/en/latest/requirements/

- Download and deployment choices: https://civicrm.org/download

- CiviCase functionality: https://docs.civicrm.org/user/en/latest/case-management/what-is-civicase/

- CiviGrant functionality: https://docs.civicrm.org/user/en/latest/grants/what-is-civigrant/

- Licensing and edition terms: https://civicrm.org/about/license

- Licensing and edition terms: https://civicrm.org/about

- CiviCRM 6.19.3 security release: https://civicrm.org/ca/node/15698

- CiviCRM security advisory index: https://civicrm.org/advisory

- CiviCRM 6.20.1 and 6.16.9 ESR security release: https://civicrm.org/blog/dev-team/civicrm-security-release-6201-616-esr

- CiviCRM 6.20.1 release record: https://download.civicrm.org/release/6.20.1

- CIVI-SA-2026-81 critical Afform permission advisory: https://civicrm.org/advisory/civi-sa-2026-81

### Licensing sources

- https://civicrm.org/about/license

- https://civicrm.org/about

- https://docs.civicrm.org/user/en/latest/grants/what-is-civigrant/

### Infrastructure sources

- https://docs.civicrm.org/installation/en/latest/requirements/

- https://civicrm.org/download


### Buyer diligence


Research coverage: 6/12 fields (50%); 5 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: Documented. CiviCRM recognizes the authenticated user session of its host CMS and maps CMS users to contacts. This confirms shared browser login for CMS-integrated installations; configure the selected Drupal/WordPress/Joomla/Backdrop identity integration and permissions separately. It does not establish one universal SAML/OIDC setup for Standalone or every CMS. Scope: CiviCRM CMS-integrated browser authentication; deployment-specific CMS federation. Source: https://docs.civicrm.org/dev/en/latest/framework/authx/ (reviewed 2026-11-21).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Documented. CiviCRM 6.20.1 and 6.16.9 ESR fix 29 advisories, including SQL injection, authorization and ACL bypass, XSS, disclosure and data-integrity issues. CIVI-SA-2026-81 is Critical and affects 6.20.0 and earlier. Upgrade the installed supported line. Scope: CiviCRM releases through 6.20.0; use 6.20.1, 6.16.9 ESR or later. Source: https://civicrm.org/blog/dev-team/civicrm-security-release-6201-616-esr (reviewed 2026-11-19). Supporting source: Critical Afform relationship-permission flaw — https://civicrm.org/advisory/civi-sa-2026-81. Supporting source: Representative SQL-injection advisory — https://civicrm.org/advisory/civi-sa-2026-53.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The Standalone installation guide recommends release tarballs for most sites and offers an official Composer project template for automated/complex installations. Buildkit is for development; a provider image may instead bundle a CMS-based configuration. Scope: CiviCRM Standalone application deployment; not a guarantee of provider-package equivalence. Source: https://docs.civicrm.org/installation/en/latest/standalone/ (reviewed 2026-11-14). Deployment artifact: https://github.com/civicrm/civicrm-standalone. Artifact reference: repository default branch (moving; select matching Composer release).

- Minimum footprint / sizing: Sources checked — unresolved. The requirements specify PHP memory_limit of 256 MB alongside database and CMS dependencies. That is a PHP process setting, not whole-host production CPU/RAM/storage sizing; concurrent staff, contributions, mailings, attachments and backups still require a capacity plan. Scope: Current CiviCRM runtime requirements; complete production hardware baseline unconfirmed. Source: https://docs.civicrm.org/installation/en/latest/requirements/ (reviewed 2026-11-21).

- License pricing: Documented. CiviCRM 2.x and later use GNU AGPLv3 with the CiviCRM Licensing Exception. Hosting, implementation, support, CMS components and extensions have separate costs/terms; the core licence does not supply those services. Scope: CiviCRM core software licence and published exception. Source: https://civicrm.org/about/license (reviewed 2026-11-21).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. CiviCRM 6.20.1 is the reviewed current release, dated November 19, 2026; its artifact was built at 2026-11-18T21:59:25Z. It fixes 29 security advisories, does not change the schema or API and requires no configuration attention. The maintained ESR fix is 6.16.9. Scope: CiviCRM upstream standard release; 6.16.9 is the corresponding maintained ESR fix. Source: https://download.civicrm.org/release/6.20.1 (reviewed 2026-11-19). Supporting source: Security-release announcement — https://civicrm.org/blog/dev-team/civicrm-security-release-6201-616-esr.




### Security and lifecycle reviews

Selected editorial reviews only; no flag does not mean safe or supported.

- CiviCRM security release review (security-advisory): The October security update addresses SQL injection, API/ACL bypasses and Standalone authentication and privilege issues. Scope: CiviCRM 6.19.3 and the associated 6.16 ESR update; individual advisory scopes differ. Conditions: The hosting integration and enabled features affect applicability. The reviewed announcement includes Drupal Composer/tag instructions. Action: Apply the supported security update for the installed line and review the linked individual advisories before rollout. Source: https://civicrm.org/ca/node/15698; reviewed 2026-11-17.

- CiviCRM 6.20.1 and 6.16.9 ESR security update (security-advisory): CiviCRM's November release fixes 29 advisories, CIVI-SA-2026-53 through -81, including a Critical Afform relationship-permission flaw. Scope: CiviCRM through 6.20.0; the maintained fixed targets are 6.20.1 and 6.16.9 ESR or later. Conditions: Installed release, extensions and exercised features determine applicability; the advisories cover SQL injection, authorization, XSS, disclosure and data-integrity paths. Action: Upgrade the installed supported line to 6.20.1, 6.16.9 ESR or later and review the individual advisories. Source: https://civicrm.org/blog/dev-team/civicrm-security-release-6201-616-esr; reviewed 2026-11-19. Supporting source: Critical Afform relationship-permission flaw — https://civicrm.org/advisory/civi-sa-2026-81. Supporting source: Representative SQL-injection advisory — https://civicrm.org/advisory/civi-sa-2026-53.




## CommCare HQ Self-Hosted

Open-source case-management backend with an upstream AWS provisioning and operations toolchain.

- Listing: https://launchinyourcloud.com/directory/commcare/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: BSD-3-Clause for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Terraform
- Architecture: CommCare HQ application and data services provisioned with Terraform and Ansible on AWS.
- 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://commcare.dimagi.com/open-source/
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

This covers a customer-operated HQ installation, not Dimagi's hosted service. Use current role-based AWS authentication guidance; older account-bootstrap examples mention root keys and are not a production credential recommendation. Mobile synchronization and external integrations require separate configuration.

BSD-3-Clause for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

CommCare HQ application and data services provisioned with Terraform and Ansible on AWS. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- case-management: Open-source case-management backend with an upstream AWS provisioning and operations toolchain.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/dimagi/commcare-cloud/tree/master/src/commcare_cloud/terraform (checked 2026-11-19). 


### Cloud deployment evidence

- AWS Terraform (aws): https://github.com/dimagi/commcare-cloud/tree/master/src/commcare_cloud/terraform
  CommCare HQ application and data services provisioned with Terraform and Ansible on AWS. This covers a customer-operated HQ installation, not Dimagi's hosted service. Use current role-based AWS authentication guidance; older account-bootstrap examples mention root keys and are not a production credential recommendation. Mobile synchronization and external integrations require separate configuration.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes orangejenny, czue, snopoke, 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/dimagi/commcare-hq/graphs/contributors

- Upstream project: https://github.com/dimagi/commcare-hq

### Sources

- AWS Terraform: https://github.com/dimagi/commcare-cloud/tree/master/src/commcare_cloud/terraform

- Cloud CLI Docs: https://commcare-cloud.readthedocs.io/en/latest/reference/1-commcare-cloud/commands.html

- BSD-3-Clause: https://raw.githubusercontent.com/dimagi/commcare-hq/master/LICENSE

- Commits: https://github.com/dimagi/commcare-hq/commits/master

### Licensing sources

- https://raw.githubusercontent.com/dimagi/commcare-hq/master/LICENSE

### Infrastructure sources

- https://github.com/dimagi/commcare-cloud/tree/master/src/commcare_cloud/terraform


### 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 upstream HQ developer documentation describes SAML2 with CommCare as service provider, trusted IdP certificates and user identity mapping. Configure the self-hosted environment and account/organisation policy; the guide describes OIDC as a possible future option rather than current support. Scope: CommCare HQ upstream SAML user federation; hosted subscription entitlement and OIDC separate. Source: https://commcare-hq.readthedocs.io/sso/overview.html (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 CommCare HQ application and data services provisioned with Terraform and Ansible on AWS. Set organization-specific secrets, networking, storage and compatible image versions before use. Scope: CommCare HQ Self-Hosted deployment example; review the full linked installation instructions. Source: https://github.com/dimagi/commcare-cloud/tree/master/src/commcare_cloud/terraform (reviewed 2026-11-19). Deployment artifact: https://github.com/dimagi/commcare-cloud/tree/master/src/commcare_cloud/terraform. Artifact reference: master (moving branch).

- Minimum footprint / sizing: Documented. The deployment guide suggests at least 32 GB RAM and 2 TB SSD for a small single-server environment, explicitly without HA. It separately describes clustered resources and workload variation; the much smaller demo/tutorial configuration must not be presented as production. Validate concurrent workers, forms, reports, database/search and recovery capacity. Scope: CommCare HQ small-production single-server reference versus clustered/HA deployment. Source: https://commcare-cloud.readthedocs.io/en/latest/prereqs/5-requirements.html (reviewed 2026-11-21).

- License pricing: Documented. BSD-3-Clause for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: CommCare HQ Self-Hosted; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/dimagi/commcare-hq/master/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







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







## FormKiQ Case Management

Coordinate intake-to-resolution workflows with auditable document trails, role-based access, and process visibility.

- Listing: https://launchinyourcloud.com/directory/formkiq-case-management/
- Publisher listing: Yes — FormKiQ publishes this directory.
- Entry kind: solution; configured solution on formkiq
- Documented cloud IDs: aws
- Operating model: Customer-operated
- Infrastructure IDs: serverless
- License: Commercial FormKiQ Advanced or Enterprise; confirm required extensions
- Licensing model: commercial-only
- Installation: Configure the solution in a FormKiQ deployment; CloudFormation installs the platform.
- Architecture: Application on the FormKiQ document and workflow platform
- Operations: Customer-managed AWS deployment option; agree solution configuration, modules and support with FormKiQ.
- Product website: https://formkiq.com/solutions/case-management/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

This is a business solution built on FormKiQ, not a separate infrastructure product. Its application configuration and available capabilities depend on the agreed edition and extension modules. This listing covers the customer-managed AWS option; vendor-managed deployments are outside this entry.

This listing describes the packaged Business Solution available through commercial Advanced/Enterprise deployments. The separate open-source Core platform does not by itself include this packaged solution.

Serverless baseline for this business solution; no required OpenSearch dependency is identified. Optional OpenSearch add-ons are evaluated separately and do not add a Hybrid label to this listing.


OpenSearch required for this solution: No

### Category fit

- case-management: Intake, case files, evidence and resolution workflows.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.formkiq.com/docs/formkiq-modules/installation/formkiq (checked 2026-11-12). 


### Cloud deployment evidence

- FormKiQ commercial AWS installation (aws): https://docs.formkiq.com/docs/formkiq-modules/installation/formkiq
  The publisher documents customer-specific CloudFormation installation for Essentials, Advanced and Enterprise, including target AWS regions and licensed modules. Business solutions are configurations of this same AWS platform; their solution scope and entitlements must be agreed separately.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed. Edition: FormKiQ platform; solution configuration and entitlement must be agreed separately.


### Sources

- Case Management solution: https://formkiq.com/solutions/case-management/

- Business solution editions and platform relationship: https://formkiq.com/solutions/

- Commercial deployment notes: https://docs.formkiq.com/docs/formkiq-modules/installation/formkiq

- Platform infrastructure and optional components: https://docs.formkiq.com/docs/platform/overview

- Licensing and edition terms: https://formkiq.com/pricing/

### Licensing sources

- https://formkiq.com/solutions/

- https://formkiq.com/pricing/

### Infrastructure sources

- https://formkiq.com/solutions/case-management/

- https://docs.formkiq.com/docs/platform/overview


### Buyer diligence


Research coverage: 5/12 fields (42%); 3 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.

This is a configured solution. Parent platform buyer facts: https://launchinyourcloud.com/directory/formkiq/#buyer-diligence. Parent entitlements, sizing and release versions are not automatically established for this solution.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Sources checked — unresolved. The solution overview describes configurable access and workflows but does not establish its actual end-user SAML/OIDC integration, identity provider or account mapping. FormKiQ platform Cognito/JWT and IAM/API authentication are separate evidence; obtain the solution-specific login design and included commercial modules. Scope: FormKiQ Case Management; configured commercial AWS solution, not the public Core deployment; solution-user federation remains unconfirmed. Source: https://formkiq.com/solutions/case-management/ (reviewed 2026-11-21). Supporting source: Underlying platform architecture — https://docs.formkiq.com/docs/platform/overview.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Documented. The overview describes role-based case access, document-specific permissions and auditable case histories. This is a vendor-described configurable control, not an independent attestation or a tested implementation. Scope: FormKiQ Case Management; customer-managed AWS deployment; configured commercial solution, not Core; agreed application configuration and modules. Source: https://formkiq.com/solutions/case-management/ (reviewed 2026-11-16).

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. Commercial installations use customer-specific CloudFormation templates supplied during onboarding. Request the template for this solution, licensed modules and AWS region; the public Core template does not include the configured solution. Scope: FormKiQ Case Management; customer-managed AWS deployment; configured commercial solution, not Core. Source: https://formkiq.com/solutions/case-management/ (reviewed 2026-11-16). Supporting source: Commercial deployment and customer-specific templates — https://docs.formkiq.com/docs/formkiq-modules/installation/formkiq.

- Minimum footprint / sizing: Sources checked — unresolved. The configured solution uses customer-specific deployment and optional processing/search/integration modules. No quantitative solution-specific CPU/RAM/concurrency/storage baseline was established. Serverless platform architecture and a document-import benchmark do not size the complete business workflow, external services or HA/recovery requirements. Scope: FormKiQ Case Management; configured commercial AWS solution, not the public Core deployment; complete workload sizing remains unconfirmed. Source: https://formkiq.com/solutions/case-management/ (reviewed 2026-11-21). Supporting source: Platform architecture and optional components — https://docs.formkiq.com/docs/platform/overview. Supporting source: Commercial deployment templates — https://docs.formkiq.com/docs/formkiq-modules/installation/formkiq.

- License pricing: Documented. The solution requires agreed commercial scope. The solution page identifies Advanced or Enterprise; confirm the edition, modules, implementation and support in a solution quote. Published base-platform prices are not the total solution price; AWS usage and connected services are additional. Scope: FormKiQ Case Management; customer-managed AWS deployment; configured commercial solution, not Core. Source: https://formkiq.com/solutions/case-management/ (reviewed 2026-11-16). Supporting source: Edition pricing and separately quoted modules/services — https://formkiq.com/pricing/.

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







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







## OpenG2P

Open-source social-protection and beneficiary-program platform with a documented AWS deployment flow.

- Listing: https://launchinyourcloud.com/directory/openg2p/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Mozilla Public License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Documented AWS infrastructure provisioning followed by the project environment and module installation
- Architecture: Reverse-proxy, compute, storage and optional backup nodes followed by the project's environment and module installation steps.
- 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/OpenG2P/openg2p-deployment
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

AWS node provisioning is one step of the full application deployment. Registry, program and payment modules have separate configuration and component licences; a deployment-repository tag is not a universal application release.

Mozilla Public License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

Reverse-proxy, compute, storage and optional backup nodes followed by the project's environment and module installation steps. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- case-management: Open-source social-protection and beneficiary-program platform with a documented AWS deployment flow.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.openg2p.org/operations/deployment/infrastructure-setup/provisioning/aws-provisioning (checked 2026-11-19). 


### Cloud deployment evidence

- AWS Provisioning (aws): https://docs.openg2p.org/operations/deployment/infrastructure-setup/provisioning/aws-provisioning
  Reverse-proxy, compute, storage and optional backup nodes followed by the project's environment and module installation steps. AWS node provisioning is one step of the full application deployment. Registry, program and payment modules have separate configuration and component licences; a deployment-repository tag is not a universal application release.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes pjoshi751, lalithkota, pramod444, 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/OpenG2P/openg2p-deployment/graphs/contributors

- Upstream project: https://github.com/OpenG2P/openg2p-deployment

### Sources

- AWS Provisioning: https://docs.openg2p.org/operations/deployment/infrastructure-setup/provisioning/aws-provisioning

- MPL-2.0: https://raw.githubusercontent.com/OpenG2P/openg2p-deployment/v1.1.0/LICENSE

- Releases: https://github.com/OpenG2P/openg2p-deployment/releases

### Licensing sources

- https://raw.githubusercontent.com/OpenG2P/openg2p-deployment/v1.1.0/LICENSE

### Infrastructure sources

- https://docs.openg2p.org/operations/deployment/infrastructure-setup/provisioning/aws-provisioning


### 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 versioned guide configures MOSIP e-Signet as an OIDC authorization-code provider with private-key client authentication, endpoints, claims and registrant mapping. Its example creates portal users. This confirms that portal path, not automatic federation for every registry/staff application or all platform versions. Scope: OpenG2P 1.2 e-Signet portal-user integration; provider registration and application scope. Source: https://docs.openg2p.org/1.2/user-guides/platform-guides/authentication/integrate-mosip-e-signet (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. OpenG2P documents AWS infrastructure provisioning and separately publishes a Helm deployment guide. Provision the compatible cluster, storage, secrets and licensed/required dependencies, then install the selected product modules. The application release, deployment repository and chart versions need deliberate alignment. Scope: OpenG2P documented AWS provisioning plus version-specific Helm deployment. Source: https://docs.openg2p.org/operations/deployment/infrastructure-setup/provisioning/aws-provisioning (reviewed 2026-11-21). Deployment artifact: https://docs.openg2p.org/1.3/deployment/helm-charts. Artifact reference: OpenG2P 1.3 Helm documentation. Supporting source: Helm deployment — https://docs.openg2p.org/1.3/deployment/helm-charts.

- Minimum footprint / sizing: Documented. The 1.3 requirements give the OpenG2P cluster 16 vCPU/64 GB RAM/256 GB storage, with separate Rancher, NFS, bastion and Nginx resources. It permits splitting cluster resources across VMs and directs HA deployments to a production guide. This is version/module-dependent, not a whole-system or workload cost guarantee. Scope: OpenG2P 1.3 cluster baseline with separate infrastructure and HA requirements. Source: https://docs.openg2p.org/1.3/deployment/hardware-requirements (reviewed 2026-11-21).

- License pricing: Documented. Mozilla Public License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: OpenG2P; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/OpenG2P/openg2p-deployment/v1.1.0/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.






