
# CiviCRM with CiviCase and CiviGrant

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

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


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



