> For the complete documentation index, see [llms.txt](https://documentation.opencrvs.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.opencrvs.org/v1.7/general/product-roadmap.md).

# Product roadmap

## The OpenCRVS Use Case Inventory

We often get the question "What does OpenCRVS do?". Beyond the descriptions found in the [Functional Architecture](/v1.7/product-specifications/functional-architecture.md) section, we maintain a full inventory of use cases, which will allow you to quickly map existing and future use cases supported by OpenCRVS with your own country requirements. 

{% file src="/files/cWGYMqnXHCgtgmCNYvq4" %}

In addition to the functional and integration use cases, a separate tab includes non-functional requirements (NFRs) that we believe are important for national scale civil registration systems, the majority of which OpenCRVS is already compliant with.  

## Future release dates

The following table provides an overview of projected delivery dates for future releases, as defined in the Use Case Inventory above. 

* The beta release is typically made available after initial QA testing, but before full regression testing has been commenced. It is not intended for live use in a production environment, however it allows accredited implementation partners to test out sample configurations and to contribute to the release testing effort.
* All dates provided are indicative and are subject to change, however OpenCRVS Product Management makes every effort to provide accurate estimates to support implementation planning. 

<table><thead><tr><th width="148">Release</th><th>Beta release date</th><th>Full release date</th></tr></thead><tbody><tr><td>v1.8.0</td><td>28 April 2025</td><td>21 July 2025</td></tr><tr><td>v1.9.0</td><td>05 September 2025</td><td>17 October 2025</td></tr><tr><td>v1.10.0</td><td>TBC</td><td>TBC</td></tr></tbody></table>

## Future product scope

The scope for future releases of OpenCRVS is primarily determined based on confirmed system requirements coming from current and future OpenCRVS implementations.&#x20;

Get in touch via [OpenCRVS Github Discussion ](https://github.com/opencrvs/opencrvs-core/discussions/categories/feature-requests)to share your priority feature requests.


---

# 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://documentation.opencrvs.org/v1.7/general/product-roadmap.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.