
# OpenG2P

Open-source social-protection and beneficiary-program platform with a documented AWS deployment flow.

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


## OpenG2P

Open-source social-protection and beneficiary-program platform with a documented AWS deployment flow.

- Listing: https://launchinyourcloud.com/directory/openg2p/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Mozilla Public License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Documented AWS infrastructure provisioning followed by the project environment and module installation
- Architecture: Reverse-proxy, compute, storage and optional backup nodes followed by the project's environment and module installation steps.
- 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://github.com/OpenG2P/openg2p-deployment
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

AWS node provisioning is one step of the full application deployment. Registry, program and payment modules have separate configuration and component licences; a deployment-repository tag is not a universal application release.

Mozilla Public License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

Reverse-proxy, compute, storage and optional backup nodes followed by the project's environment and module installation steps. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- case-management: Open-source social-protection and beneficiary-program platform with a documented AWS deployment flow.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.openg2p.org/operations/deployment/infrastructure-setup/provisioning/aws-provisioning (checked 2026-11-19). 


### Cloud deployment evidence

- AWS Provisioning (aws): https://docs.openg2p.org/operations/deployment/infrastructure-setup/provisioning/aws-provisioning
  Reverse-proxy, compute, storage and optional backup nodes followed by the project's environment and module installation steps. AWS node provisioning is one step of the full application deployment. Registry, program and payment modules have separate configuration and component licences; a deployment-repository tag is not a universal application release.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes pjoshi751, lalithkota, pramod444, 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/OpenG2P/openg2p-deployment/graphs/contributors

- Upstream project: https://github.com/OpenG2P/openg2p-deployment

### Sources

- AWS Provisioning: https://docs.openg2p.org/operations/deployment/infrastructure-setup/provisioning/aws-provisioning

- MPL-2.0: https://raw.githubusercontent.com/OpenG2P/openg2p-deployment/v1.1.0/LICENSE

- Releases: https://github.com/OpenG2P/openg2p-deployment/releases

### Licensing sources

- https://raw.githubusercontent.com/OpenG2P/openg2p-deployment/v1.1.0/LICENSE

### Infrastructure sources

- https://docs.openg2p.org/operations/deployment/infrastructure-setup/provisioning/aws-provisioning


### 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 versioned guide configures MOSIP e-Signet as an OIDC authorization-code provider with private-key client authentication, endpoints, claims and registrant mapping. Its example creates portal users. This confirms that portal path, not automatic federation for every registry/staff application or all platform versions. Scope: OpenG2P 1.2 e-Signet portal-user integration; provider registration and application scope. Source: https://docs.openg2p.org/1.2/user-guides/platform-guides/authentication/integrate-mosip-e-signet (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. OpenG2P documents AWS infrastructure provisioning and separately publishes a Helm deployment guide. Provision the compatible cluster, storage, secrets and licensed/required dependencies, then install the selected product modules. The application release, deployment repository and chart versions need deliberate alignment. Scope: OpenG2P documented AWS provisioning plus version-specific Helm deployment. Source: https://docs.openg2p.org/operations/deployment/infrastructure-setup/provisioning/aws-provisioning (reviewed 2026-11-21). Deployment artifact: https://docs.openg2p.org/1.3/deployment/helm-charts. Artifact reference: OpenG2P 1.3 Helm documentation. Supporting source: Helm deployment — https://docs.openg2p.org/1.3/deployment/helm-charts.

- Minimum footprint / sizing: Documented. The 1.3 requirements give the OpenG2P cluster 16 vCPU/64 GB RAM/256 GB storage, with separate Rancher, NFS, bastion and Nginx resources. It permits splitting cluster resources across VMs and directs HA deployments to a production guide. This is version/module-dependent, not a whole-system or workload cost guarantee. Scope: OpenG2P 1.3 cluster baseline with separate infrastructure and HA requirements. Source: https://docs.openg2p.org/1.3/deployment/hardware-requirements (reviewed 2026-11-21).

- License pricing: Documented. Mozilla Public License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: OpenG2P; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/OpenG2P/openg2p-deployment/v1.1.0/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.






