> 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/products/registry.md).

# Registry

**OpenG2P Registry** is an open-source platform for building **functional registries** — not mere databases — of individuals, non-human entities, and groups, designed to fit naturally into a country's digital public infrastructure. A single deployment hosts one or more **Registers** (Individual, Household, Farmer, …), each governed by change-management workflows, version history, consent-aware data sharing and a metadata-driven UI.

The **platform is itself installable** and ships a runnable reference registry. A domain registry — social, farmer, disability, … — is a thin **extension** on top of it, not a fork. So the platform and every registry built on it share one codebase, one Helm chart and one set of images.

{% hint style="info" %}
**New home: GitLab.** These repositories are now developed on GitLab:

* [`registry-platform`](https://gitlab.com/openg2p/registry/registry-platform)
* [`national-social-registry`](https://gitlab.com/openg2p/registry/national-social-registry)
* [`farmer-registry`](https://gitlab.com/openg2p/registry/farmer-registry)
  {% endhint %}

## In this section

|                                                                                |                                                                                                                                                                                                                          |
| ------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| [**OpenG2P Registry (Platform)**](/products/registry/registry.md)              | The platform itself — concepts, features, design, the developer zone, and how it is [packaged and extended](/products/registry/registry/deployment-and-extension.md). Start here to understand how registries are built. |
| [**Farmer Registry**](/products/registry/farmer-registry.md)                   | A registry tuned for agricultural use — Farmer and Household registers plus farm, land, crop, livestock and cooperative data.                                                                                            |
| [**National Social Registry**](/products/registry/national-social-registry.md) | A registry for social protection — Individual and Household registers with the socio-economic data used to target and enrol programmes.                                                                                  |

Both the Farmer Registry and the National Social Registry are **extensions of the platform**: each adds only its domain model, seed data, tests and a thin values overlay. See [Deployment and Extension](/products/registry/registry/deployment-and-extension.md) for how that works, and [Use Case Implementation](/products/registry/registry/use-case-implementation.md) to build your own.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.openg2p.org/products/registry.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.