> 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/platform/roadmap.md). # Roadmap OpenG2P is an open-source platform for delivering government-to-person (G2P) benefits at national scale. This roadmap lays out where we are taking the platform, the products built on it, and the community around it. It is a statement of direction — priorities evolve with field experience and the needs of the governments, partners, and communities we serve. {% hint style="info" %} This roadmap is indicative, not a commitment to dates. Items shift as we learn from real deployments and as customer and country priorities change. We share it to be transparent about our thinking and to invite collaboration. {% endhint %} ## At a glance | Horizon | Theme | Focus | | -------- | ------------------------ | ----------------------------------------------------------------------------------------------------------- | | **2026** | Consolidate & harden | Mature and enhance the Gen2 modules, complete DCI interoperability, and launch new registries and services | | **2027** | Intelligence & inclusion | Bring AI and verifiable credentials into everyday use, and unify the product architecture | | **2028** | Scale & reach | Expand into solutioning and advisory roles, and extend G2P technology beyond government to humanitarian use | *** ## 2026 — Consolidate & harden Having brought our modules together into a coherent Gen2 platform, this year is about maturing what we have, proving it across more use cases, and filling the gaps that the field has shown us matter most. ### Platform & products * **Registry Gen2 in production** — Registry Gen2 is in good shape; we continue to apply it to new use cases and refine it with customer feedback. * **New reference registries** — Reference implementations of a **Disability Registry** and a **Family Registry**, demonstrating how the domain-agnostic core adapts to new sectors. * **Consent management for data sharing** — A consent layer, focused initially on governing how data is shared out of the registry. * **Partner management module** — Partner onboarding and management brought out into its own dedicated module. ### Interoperability * **DCI interoperability** — A substantial amount of Digital Convergence Initiative (DCI) interoperability is already complete; this year we finish the **Disability Registry** and **Integrated Beneficiary Registry (IBR)** work. ### Deployment & operations * **AI-assisted deployment** — Highly automated, AI-based deployment tooling to cut the time and effort of standing up an OpenG2P environment. ### Adoption & community * **Country support** — Deepening support for countries adopting OpenG2P. * **First OpenG2P Country & Partner Conference** — Bringing together the governments and partners in our ecosystem for the first time. *** ## 2027 — Intelligence & inclusion With the platform consolidated, we turn to making it smarter and more inclusive — putting AI and verifiable credentials to work in real use cases, and simplifying the architecture so partners can build faster. ### Trust & credentials * **Verifiable credentials in use** — Issuance and use of verifiable credentials across a range of G2P use cases. ### AI & intelligence * **AI for administrators** — Tools that give programme administrators insight into the operations of G2P benefit delivery. * **Reimagined OpenG2P Academy** — A new, AI-driven avatar of the Academy for learning and enablement. ### Inclusion * **Voice-based Grievance Redressal** — A voice-driven GRM to reach beneficiaries for whom text and apps are a barrier. ### Architecture * **Unifying SPAR onto Registry** — Aligning SPAR with the registry architecture so that SPAR becomes an implementation of the OpenG2P Registry, reducing duplication across the platform. ### Ecosystem & partners * **Solutioning support** — Helping departments and countries design end-to-end solutions on OpenG2P. * **Partner productivity tools** — Tooling that helps implementation partners learn OpenG2P faster, customise it, and deploy with confidence. * **A larger local partner ecosystem** — Growing a base of local partners who can be onboarded quickly with the help of AI-based tools. *** ## 2028 — Scale & reach Our third horizon is about reach: taking on a broader advisory role, extending G2P technology to new kinds of organisations, and continuously evolving the products from what we learn in the field. ### Inclusion * **Deeper voice-based GRM** — Further enhancing the voice-based grievance mechanism to increase inclusion. ### Reach & advocacy * **Advisory role** — Taking on more of an advisory role, providing end-to-end G2P solutions to countries. * **Beyond government** — Reaching out to humanitarian organisations to use G2P technology, not only governments. ### Continuous evolution * **Field-driven product evolution** — Evolving all of our products on the basis of real field experience. *** {% hint style="success" %} **Want to shape the roadmap?** OpenG2P is built in the open. If you are a government, implementation partner, or contributor with a use case or a priority you'd like us to consider, reach out through our [Community](/community/contributing-to-openg2p.md) channels. {% endhint %} --- # 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/platform/roadmap.md?ask=&goal= ``` `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.