
# Merative Cúram Social Program Management

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

Canonical page: https://launchinyourcloud.com/directory/merative-spm/
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.


1 listing.


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






