CommCare HQ Self-Hosted

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

4 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

    Terraform

  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.

    AWS Terraform ↗ · 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 methodTerraform
InfrastructureServers / containers
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.
Licensing modelOpen Source / Open Core
BSD-3-Clause for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
LicenseBSD-3-Clause for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

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%) · 4 documented · 0 unresolved. Evidence coverage is not a feature score.

Single sign-on
AvailableEvidence and scope for Single sign-on

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.

CommCare HQ upstream SAML user federation; hosted subscription entitlement and OIDC separate · Source ↗ · Reviewed 2026-11-21

Documented · Editor reviewed.

Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC

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.

CommCare HQ Self-Hosted deployment example; review the full linked installation instructions · Deployment artifact ↗ (master (moving branch)) · Reviewed 2026-11-19

Documented · Editor reviewed.

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

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.

CommCare HQ small-production single-server reference versus clustered/HA deployment · Source ↗ · Reviewed 2026-11-21

Documented · Editor reviewed.

License pricing
DocumentedEvidence and scope for License pricing

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

CommCare HQ Self-Hosted; software terms only, excluding cloud charges, labour and separately licensed services · Source ↗ · Reviewed 2026-11-19

Documented · 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

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.

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

Category fit

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

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
  • 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
  • Merative Cúram Social Program ManagementCommercial social-program case-management software with customer Kubernetes runbooks.
    • 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.

    • AWS Terraform ↗ · AWS

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

      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.

  3. Infrastructure evidenceChecked
  4. Licensing evidenceChecked
  5. Community & maintenance evidenceChecked

Suggest a correction · Back to directory