Merative Cúram Social Program Management

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

8 sources checked by an editor on · Product website ↗

Deployment terms: BYOC · control plane · data plane · private offer

· Open requirements shortlist · Estimate operating costs

Compare this listing with another →

What lands where

  1. Supplied by

    Vendor or project

    Kubernetes manifests

  2. Operated by

    Your team

    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.

Deployment boundaries by provider
  • AWS: Customer cloud account · Customer-operated

    Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.

    EKS Source ↗ · Source checked 2026-11-19

  • Azure: Customer cloud account · Customer-operated

    Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.

    AKS Source ↗ · Source checked 2026-11-19

Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.

Install methodKubernetes manifests
InfrastructureServers / containers
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.
Licensing modelCommercial Only
Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.
LicenseCommercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.

Buyer diligence

Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.

How to read these facts

Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.

4 of 12 fields researched (33%) · 1 documented · 3 unresolved. Evidence coverage is not a feature score.

Single sign-on
Not confirmedEvidence and scope for Single sign-on

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.

Cúram application identity candidate; secure production configuration and release support remain unconfirmed · Source ↗ · Reviewed 2026-11-21

Sources checked — unresolved · Editor reviewed.

Deployment artifact / IaC
Not confirmedEvidence and scope for Deployment artifact / IaC

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.

Cúram deployment documentation versus licensed runtime artifacts · Source ↗ · Reviewed 2026-11-19

Sources checked — unresolved · Editor reviewed.

Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing

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.

Moving vendor Cúram chart application-pod defaults, not full production/HA capacity · Source ↗ · Resource-consuming deployment template ↗ · Reviewed 2026-11-21

Documented · Editor reviewed.

License pricing
Not confirmedEvidence and scope for License pricing

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.

Selected self-managed application or customer-cloud service; contract confirmation required · Source ↗ · Reviewed 2026-11-19

Sources checked — unresolved · Editor reviewed.

Show all fields (8 not researched)
Marketplace delivery
Not researched Supply a public source.
Cloud commitment eligibility
Not researched Supply a public source.
SCIM provisioning
Not researched Supply a public source.
Compliance attestations
Not researched Supply a public source.
Security controls
Not researched Supply a public source.
Air-gapped operation
Not researched Supply a public source.
Operating cost estimate
Not researched Supply a public source.
Release snapshot / cadence
Not researched Supply a public source.

Scope & considerations

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.

Category fit

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

Compare within Case management

  • CiviCRM with CiviCase and CiviGrantSelf-hosted constituent management with configurable case activities and grant application tracking.
    • AWS
    Customer-operated · Open Source / Open Core
  • CommCare HQ Self-HostedOpen-source case-management backend with an upstream AWS provisioning and operations toolchain.
    • AWS
    Customer-operated · Open Source / Open Core
  • Flowable Enterprise PlatformCommercial workflow and case-management platform with vendor Terraform and Helm deployments.
    • AWS
    • Azure
    Customer-operated · Commercial Only
  • FormKiQ Case Management Directory PublisherCoordinate intake-to-resolution workflows with auditable document trails, role-based access, and process visibility.
    • AWS
    Customer-operated · Commercial Only
  • Hyland OnBase On-PremiseCustomer-hosted enterprise content and case platform for document-heavy business processes.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Commercial Only
  • Laserfiche Self-HostedSelf-hosted document and records platform with forms and configurable business process automation.
    • AWS
    • Azure
    Customer-operated · Commercial Only
  • OpenCRVSOpen-source civil registration software for birth, death and related registration workflows.
    • AWS
    • Google Cloud
    • Hetzner
    Customer-operated · Open Source / Open Core
  • OpenG2POpen-source social-protection and beneficiary-program platform with a documented AWS deployment flow.
    • AWS
    Customer-operated · Open Source / Open Core

Showing 8 of 9 other listings in Case management. These products address related workflows; read their category-fit notes before comparing scope. See all of Case management →

Installation outline

  1. Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
  2. Review the vendor's installation documentation, required permissions and outbound data flows.
  3. Deploy to a non-production environment; configure identity, networking and monitoring.
  4. Test backup recovery and upgrades before promoting to production.

Watch this listing with RSS

Evidence trail

Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.

  1. Deployment sourcesChecked
  2. Cloud deployment evidenceChecked

    The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.

    • EKS Source ↗ · AWS

      Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.

      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.

    • AKS Source ↗ · Azure

      Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.

      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.

  3. Infrastructure evidenceChecked
  4. Licensing evidenceChecked

Suggest a correction · Back to directory