
# CommCare HQ Self-Hosted

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

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


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






