> For the complete documentation index, see [llms.txt](https://docs.openg2p.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openg2p.org/1.2/platform/architecture.md).

# Architecture

## Introduction

OpenG2P has a flexible architecture that allows governments and social benefit delivery systems to choose modules per their needs. Using the OpenG2P platform, governments can digitalise the benefit delivery end-to-end and gain significantly in terms of efficiency, ease of administration, speed, cost, and convenience for the beneficiaries. The platform is built for inclusion and has supporting features. For example, beneficiaries in remote areas without network connectivity can be registered offline.

## Functional architecture

{% embed url="<https://miro.com/app/board/uXjVNGpmGPw=/?share_link_id=873269042816>" %}

The above diagram depicts the offerings of the OpenG2P platform. These include:

* [Social Registry](/1.2/platform/modules/social-registry.md)
* [Registration Toolkit](/1.2/platform/modules/registration-tool-kit.md)
* [Program & Beneficiary Management System](/1.2/platform/modules/program-and-beneficiary-management-system.md)
* [G2P Cash Transfer Bridge](/1.2/platform/modules/g2p-cash-transfer-bridge.md)
* [Social Payments Account Registry](/1.2/platform/modules/social-payments-account-registry-spar.md)

All the modules are designed to be installed and used standalone.  However, the full power of OpenG2P can be harnessed if all the modules are used in conjunction with each other.

## Guiding principles

**Interoperability** of components  across DPGs is being established by implementing interfaces defined by emerging standards like G2P Connect. [Lean more >>](/1.2/platform/interoperability.md).

The platform design and deployment embodies **privacy and security** of user data. [Learn more >>.](/1.2/platform/privacy-and-security.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.openg2p.org/1.2/platform/architecture.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.