CiviCRM with CiviCase and CiviGrant
Self-hosted constituent management with configurable case activities and grant application tracking.
11 sources checked by an editor on · Product website ↗
Read this page as JSON or Markdown.
Deployment terms: BYOC · control plane · data plane · private offer
· Open requirements shortlist · Estimate operating costs
Compare this listing with another →
CiviCRM security release review
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.
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.
Primary source · Reviewed 2026-11-17
CiviCRM 6.20.1 and 6.16.9 ESR security update
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.
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.
Primary source · Critical Afform relationship-permission flaw · Representative SQL-injection advisory · Reviewed 2026-11-19
What lands where
Supplied by
Vendor or project
Standalone installation or supported CMS integration
Runs in
Documented customer environment
Customer-operated PHP application and MySQL/MariaDB database
- AWS: Customer cloud account
- AWS
Servers / containers
Operated by
Your team
Customer or service provider maintains the installation, extensions, database and updates.
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.
Customer-deployed CiviCRM on AWS reference architecture ↗ · Source checked 2026-11-12
Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.
| Install method | Standalone installation or supported CMS integration |
|---|---|
| Infrastructure | Servers / containers 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. |
| Licensing model | Open Source / Open Core 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. |
| License | Open-source; hosting and implementation separately arranged |
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.
6 of 12 fields researched (50%) · 5 documented · 1 unresolved. Evidence coverage is not a feature score.
- Single sign-on
AvailableEvidence and scope for Single sign-on
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.
CiviCRM CMS-integrated browser authentication; deployment-specific CMS federation · Source ↗ · Reviewed 2026-11-21
Documented · Editor reviewed.
- Security controls
DocumentedEvidence and scope for Security controls
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.
CiviCRM releases through 6.20.0; use 6.20.1, 6.16.9 ESR or later · Source ↗ · Critical Afform relationship-permission flaw ↗ · Representative SQL-injection advisory ↗ · Reviewed 2026-11-19
Documented · Editor reviewed.
- Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC
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.
CiviCRM Standalone application deployment; not a guarantee of provider-package equivalence · Source ↗ · Deployment artifact ↗ (repository default branch (moving; select matching Composer release)) · Reviewed 2026-11-14
Documented · Editor reviewed.
- Minimum footprint / sizing
Not confirmedEvidence and scope for Minimum footprint / sizing
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.
Current CiviCRM runtime requirements; complete production hardware baseline unconfirmed · Source ↗ · Reviewed 2026-11-21
Sources checked — unresolved · Editor reviewed.
- License pricing
DocumentedEvidence and scope for License pricing
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.
CiviCRM core software licence and published exception · Source ↗ · Reviewed 2026-11-21
Documented · Editor reviewed.
- Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence
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.
CiviCRM upstream standard release; 6.16.9 is the corresponding maintained ESR fix · Source ↗ · Security-release announcement ↗ · Reviewed 2026-11-19
Documented · Editor reviewed.
Show all fields (6 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.
- Air-gapped operation
- Not researched Supply a public source.
- Operating cost estimate
- Not researched Supply a public source.
Scope & considerations
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.
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.
Compare within Case management
- CommCare HQ Self-HostedOpen-source case-management backend with an upstream AWS provisioning and operations toolchain.
- AWS
- Flowable Enterprise PlatformCommercial workflow and case-management platform with vendor Terraform and Helm deployments.
- AWS
- Azure
- FormKiQ Case Management Directory PublisherCoordinate intake-to-resolution workflows with auditable document trails, role-based access, and process visibility.
- AWS
- Hyland OnBase On-PremiseCustomer-hosted enterprise content and case platform for document-heavy business processes.
- AWS
- Azure
- Google Cloud
- Laserfiche Self-HostedSelf-hosted document and records platform with forms and configurable business process automation.
- AWS
- Azure
- Merative Cúram Social Program ManagementCommercial social-program case-management software with customer Kubernetes runbooks.
- AWS
- Azure
- OpenCRVSOpen-source civil registration software for birth, death and related registration workflows.
- AWS
- Google Cloud
- Hetzner
- OpenG2POpen-source social-protection and beneficiary-program platform with a documented AWS deployment flow.
- AWS
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
- Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
- Review the vendor's installation documentation, required permissions and outbound data flows.
- Deploy to a non-production environment; configure identity, networking and monitoring.
- Test backup recovery and upgrades before promoting to production.
Evidence trail
Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.
- Deployment sourcesChecked
- Installation requirements ↗docs.civicrm.org
- Download and deployment choices ↗civicrm.org
- CiviCase functionality ↗docs.civicrm.org
- CiviGrant functionality ↗docs.civicrm.org
- Licensing and edition terms ↗civicrm.org
- Licensing and edition terms ↗civicrm.org
- CiviCRM 6.19.3 security release ↗civicrm.org
- CiviCRM security advisory index ↗civicrm.org
- CiviCRM 6.20.1 and 6.16.9 ESR security release ↗civicrm.org
- CiviCRM 6.20.1 release record ↗download.civicrm.org
- CIVI-SA-2026-81 critical Afform permission advisory ↗civicrm.org
- Cloud deployment evidenceChecked
The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.
- Customer-deployed CiviCRM on AWS reference architecture ↗ · AWS
Provider guide · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
- Customer-deployed CiviCRM on AWS reference architecture ↗ · AWS
- Infrastructure evidenceChecked
- Licensing evidenceChecked