OpenCRVS
Open-source civil registration software for birth, death and related registration workflows.
5 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 →
What lands where
Supplied by
Vendor or project
Terraform; Kubernetes manifests
Runs in
Documented customer environment
OpenCRVS application and persistent services on the project's named-cloud Kubernetes infrastructure templates.
- AWS: Customer cloud account
- Google Cloud: Customer cloud account
- Hetzner: Customer cloud account
- AWS
- Google Cloud
- Hetzner
Servers / containers
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 EKS Terraform ↗ · Source checked 2026-11-19
- Google Cloud: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
GCP GKE Terraform ↗ · Source checked 2026-11-19
- Hetzner: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Hetzner K8s 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 method | Terraform; Kubernetes manifests |
|---|---|
| Infrastructure | Servers / containers OpenCRVS application and persistent services on the project's named-cloud Kubernetes infrastructure templates. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure. |
| Licensing model | Open Source / Open Core GNU LGPL licence for the reviewed upstream edition; optional commercial services and bundled components have separate terms. |
| License | GNU LGPL licence 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%) · 3 documented · 1 unresolved. Evidence coverage is not a feature score.
- Single sign-on
Not confirmedEvidence and scope for Single sign-on
The server-hosting guide distinguishes production user two-factor codes, test accounts and government VPN access, but does not establish a supported external user SAML/OIDC login path. VPN/server identity and the application authentication service are separate; verify the selected current release and country configuration.
OpenCRVS enterprise/user federation remains unconfirmed · Source ↗ · Reviewed 2026-11-21
Sources checked — unresolved · Editor reviewed.
- Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC
The reviewed source supplies deployment configuration for OpenCRVS application and persistent services on the project's named-cloud Kubernetes infrastructure templates. Set organization-specific secrets, networking, storage and compatible image versions before use.
Reviewed deployment source collection; application images and infrastructure components have separate versions · Source ↗ · Deployment artifact ↗ (main (moving branch)) · Reviewed 2026-11-19
Documented · Editor reviewed.
- Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing
The v1.7 guide lists production/staging at 8 CPUs/16 GB RAM with storage calculated from registration volume/attachments, versus development/QA at 4 CPUs/16 GB/320 GB. It specifies x86_64 Ubuntu 24.04 and separate backup requirements. Revalidate the selected release, clustering, throughput and recovery rather than applying this as an unrestricted current HA minimum.
Versioned OpenCRVS v1.7 environment-specific baseline; current deployment/version sizing separate · Source ↗ · Reviewed 2026-11-21
Documented · Editor reviewed.
- License pricing
DocumentedEvidence and scope for License pricing
GNU LGPL licence for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
OpenCRVS; 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
A country configuration, institutional identity, registration rules and integrations must be supplied. Infrastructure templates and the application release are separate, and public source does not confer authority to issue civil records.
Community & maintenance
The reviewed upstream contributor history includes rikukissa, euanmillar, makelicious, 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 civil registration software for birth, death and related registration workflows.
Compare within Case management
- CiviCRM with CiviCase and CiviGrantSelf-hosted constituent management with configurable case activities and grant application tracking.
- AWS
- 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
- 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
- AWS EKS Terraform ↗raw.githubusercontent.com
- GCP GKE Terraform ↗raw.githubusercontent.com
- Hetzner K8s Terraform ↗raw.githubusercontent.com
- MPL-2.0 ↗raw.githubusercontent.com
- Releases ↗github.com
- 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 EKS Terraform ↗ · AWS
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
OpenCRVS application and persistent services on the project's named-cloud Kubernetes infrastructure templates. A country configuration, institutional identity, registration rules and integrations must be supplied. Infrastructure templates and the application release are separate, and public source does not confer authority to issue civil records.
- GCP GKE Terraform ↗ · Google Cloud
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
OpenCRVS application and persistent services on the project's named-cloud Kubernetes infrastructure templates. A country configuration, institutional identity, registration rules and integrations must be supplied. Infrastructure templates and the application release are separate, and public source does not confer authority to issue civil records.
- Hetzner K8s Terraform ↗ · Hetzner
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
OpenCRVS application and persistent services on the project's named-cloud Kubernetes infrastructure templates. A country configuration, institutional identity, registration rules and integrations must be supplied. Infrastructure templates and the application release are separate, and public source does not confer authority to issue civil records.
- AWS EKS Terraform ↗ · AWS
- Infrastructure evidenceChecked
- Licensing evidenceChecked
- Community & maintenance evidenceChecked
- Community, governance or adoption evidence ↗github.com
- Upstream project ↗github.com