# Roadmap 2026 & Beyond

Here we present the product roadmap for **MOSIP** Identity for the calendar year 2026 and our strategic horizon forward.

This roadmap outlines the planned features, progress, and release details for 'MOSIP Identity and Modules'.

> Annual product cycle of **MOSIP** commences in **January** and concludes in **December**.

For detailed and module-wise roadmaps, please refer to the respective sections; [MOSIP Identity](#mosip-identity), [Resident Portal](#resident-portal), [Android Registration Client](#android-registration-client) and Partner Management System.

## MOSIP Identity

<details>

<summary>Vision</summary>

In 2026, MOSIP will be a **secure, intelligent, and high-performance digital identity platform** that empowers countries to manage citizen identities efficiently while enabling innovation in biometrics, cryptography, and handle-based identity management. Alongside delivering advanced features such as adaptive biometric learning, policy-driven UIN updates, and quantum-safe cryptography, the platform will prioritize **clearing technical debts and enhancing maintainability**, addressing infrastructure, code quality, security, and operational improvements. This dual focus ensures MOSIP remains **reliable, scalable, and future-ready**, providing countries with a robust foundation for inclusive and secure identity services.

</details>

<table><thead><tr><th width="98.92578125">Priority 🗓️</th><th width="157.0625">Module</th><th width="293.5078125">Features 🛠️</th><th width="121.02734375">Details📝</th><th width="100.13671875">Status 📊</th><th>Release 📌</th></tr></thead><tbody><tr><td>P1</td><td><strong>Registration Processor &#x26; Packet Processing</strong></td><td><br>Performance Enhancement</td><td><i class="fa-github">:github:</i> <a href="https://github.com/mosip/registration/issues/2283">2283</a></td><td>🟠 In Progress</td><td></td></tr><tr><td>P1</td><td><strong>Key Manager</strong></td><td>Support for ECC Algorithm during encryption &#x26; decryption.</td><td><i class="fa-github">:github:</i> <a href="https://github.com/mosip/keymanager/issues/523">523</a></td><td>🔵 Planned</td><td></td></tr><tr><td>P1</td><td><strong>Registration Processor</strong></td><td>Draft API Re implementation.</td><td><i class="fa-github">:github:</i> <a href="https://github.com/mosip/registration/issues/2198">2198</a></td><td>🔵 Planned</td><td></td></tr><tr><td>P1</td><td><strong>Registration Processor/ Biometrics</strong></td><td>Enhancing the quality classifier stage.</td><td><i class="fa-github">:github:</i> <a href="https://github.com/mosip/registration-client/issues/770">770</a></td><td>🔵 Planned</td><td></td></tr><tr><td>P1</td><td><strong>ID Repository</strong></td><td>Array of Handle - Phase 1.</td><td><i class="fa-github">:github:</i> TBA</td><td>🔵 Planned</td><td></td></tr><tr><td>P1</td><td><strong>Registration Client &#x26; Processor</strong></td><td>Enabling Custom Handles feature.</td><td><i class="fa-github">:github:</i> TBA</td><td>🔵 Planned</td><td></td></tr><tr><td>P1</td><td><strong>Registration Processor</strong></td><td>Biometric Adaptive Learning.</td><td><i class="fa-github">:github:</i> TBA</td><td>🔵 Planned</td><td></td></tr><tr><td>P1</td><td><strong>ID Repository</strong></td><td>Enhancement of ID Repository.</td><td><i class="fa-github">:github:</i> TBA</td><td>🔵 Planned</td><td></td></tr><tr><td>P1</td><td>Registration Processor</td><td>Update UIN through policy.</td><td><i class="fa-github">:github:</i> TBA</td><td>🔵 Planned</td><td></td></tr><tr><td>P1</td><td><strong>Registration Processor</strong></td><td>Enhancing Manual Adjudication.</td><td><i class="fa-github">:github:</i> TBA</td><td>🔵 Planned</td><td></td></tr><tr><td>P1</td><td><strong>Key Manager</strong></td><td>Supporting Quantum Safe Algorithms.</td><td><i class="fa-github">:github:</i> TBA</td><td>🔵 Planned</td><td></td></tr><tr><td>P1</td><td><strong>Admin</strong></td><td>Enhancement of Admin features.</td><td><i class="fa-github">:github:</i> TBA</td><td>🔵 Planned</td><td></td></tr><tr><td>P2</td><td><p><strong>Platform/ Biometrics</strong></p><p><strong>(Reg Client &#x26; Reg Proc)</strong></p></td><td>Biometric Quality Enhancement during Registration.</td><td><i class="fa-github">:github:</i> TBA</td><td>🔵 Planned</td><td></td></tr><tr><td>P2</td><td>Reporting/Dashboard</td><td>Anonymous Profile &#x26; Reporting Enhancement.</td><td><i class="fa-github">:github:</i> TBA</td><td>🔵 Planned</td><td></td></tr><tr><td>P2</td><td><strong>Platform</strong></td><td>Deactivation of SBI/FTM Partner.</td><td><i class="fa-github">:github:</i> TBA</td><td>🔵 Planned</td><td></td></tr><tr><td>P2</td><td><strong>Registration Client</strong></td><td>Auto upgrade during the slow / low network.</td><td><i class="fa-github">:github:</i> TBA</td><td>🔵 Planned</td><td></td></tr><tr><td>P2</td><td><strong>Platform/ Notification Services</strong></td><td>Notification Service Enhancement.</td><td><i class="fa-github">:github:</i> TBA</td><td>🔵 Planned</td><td></td></tr><tr><td>P3</td><td><strong>Registration Client</strong></td><td>Support for Document Scanner.</td><td><i class="fa-github">:github:</i> TBA</td><td>🔵 Planned</td><td></td></tr><tr><td>P3</td><td>ID Authentication</td><td>Data Insertion for IDA.</td><td><i class="fa-github">:github:</i> TBA</td><td>🔵 Planned</td><td></td></tr><tr><td>P3</td><td><strong>Admin</strong></td><td>General ID issuance features.</td><td><i class="fa-github">:github:</i> TBA</td><td>🔵 Planned</td><td></td></tr><tr><td>P3</td><td><strong>ID Authentication</strong></td><td>Age-Based Credential Attributes.</td><td><i class="fa-github">:github:</i> TBA</td><td>🔵 Planned</td><td></td></tr><tr><td>P3</td><td><strong>Key Manager</strong></td><td>Support for BBS+ in Key Manager.</td><td><i class="fa-github">:github:</i> TBA</td><td>🔵 Planned</td><td></td></tr><tr><td>P3</td><td><strong>Key Manager</strong></td><td>Key manager to support for software based key stores/vaults.</td><td><i class="fa-github">:github:</i> TBA</td><td>🔵 Planned</td><td></td></tr><tr><td>P4</td><td><strong>Registration Client</strong></td><td>Metadata Enhancement.</td><td><i class="fa-github">:github:</i> TBA</td><td>🔵 Planned</td><td></td></tr><tr><td>P4</td><td><strong>ID Repository</strong></td><td>Array of Handle - Phase 2.</td><td><i class="fa-github">:github:</i> TBA</td><td>🔵 Planned</td><td></td></tr></tbody></table>

### Resident Portal

<details>

<summary><strong>Vision</strong></summary>

The Resident Portal will become a modern, secure, and universally accessible gateway for residents to manage their identity services. A refreshed UI will deliver a cleaner, more intuitive experience, while alternative login options will ensure access even when all biometric modalities are locked. Strengthened by performance testing, automation, and security enhancements, the portal will offer faster, safer, and more reliable service delivery. With added USSD support, it will extend access to residents in low-connectivity and feature-phone environments, ensuring inclusivity for all.

</details>

<table><thead><tr><th width="91.03515625">Priority 🗓️</th><th width="327.39453125">Feature 🛠️</th><th width="142.5625">Details 📝</th><th width="136.19140625">Status 📊</th><th>Release 📌</th></tr></thead><tbody><tr><td>P1</td><td>Revamp of Resident Portal UI.</td><td><a href="https://github.com/mosip/resident-ui/issues?q=state%3Aopen%20label%3AResident_UI_Revamp">Revamp of Resident UI</a></td><td>🟠 In-Progress</td><td></td></tr><tr><td>P1</td><td>Allow resident services to log in even when all the modalities are locked.</td><td><i class="fa-github">:github:</i> <a href="https://github.com/mosip/resident-services/issues/1534">1534</a></td><td>🔵 Planned</td><td></td></tr><tr><td>P1</td><td>Performance testing + Automation + Security fixes.</td><td><i class="fa-github">:github:</i> <a href="https://mosip.atlassian.net/browse/MOSIP-32001">32001</a></td><td>🔵 Planned</td><td></td></tr><tr><td>P1</td><td>As a resident, User should be able to use all the services offered by resident portal using USSD services.</td><td><i class="fa-github">:github:</i> <a href="https://github.com/mosip/resident-services/issues/1535">1535</a></td><td>🔵 Planned</td><td></td></tr></tbody></table>

### Android Registration Client

<details>

<summary>Vision</summary>

The Android Registration Client will provide a faster, more accurate, and reliable registration experience. With integrated third-party Quality SDKs, unified quality scoring, and combined match and biometric scores, the client will ensure high-assurance biometric capture. Streamlined demographic, block-listed words, acknowledgment, and packet approval pages will reduce errors and simplify operator workflows. OCR will speed up data entry, and telemetry will offer real-time operational insights.\
Overall, the client will evolve into a smart, efficient, and quality-driven registration platform.

</details>

<table><thead><tr><th width="96.08203125">Priority 🗓️</th><th width="343.12890625">Feature 🛠️</th><th width="131.12109375">Details 📝</th><th width="128.82421875">Status 📊</th><th>Release 📌</th></tr></thead><tbody><tr><td>P1</td><td>JAVA 21 Migration</td><td><i class="fa-github">:github:</i> <a href="https://github.com/mosip/android-registration-client/issues/828">828</a></td><td>🟠 In-progress</td><td></td></tr><tr><td>P1</td><td><strong>Quality SDK</strong>: Support for 3rd party SDK to measure quality of biometrics captured.</td><td><i class="fa-github">:github:</i> <a href="https://github.com/mosip/android-registration-client/issues/643">643</a></td><td>🔵 Planned</td><td></td></tr><tr><td>P1</td><td>Centre Remapping</td><td><i class="fa-github">:github:</i> TBA</td><td>🔵 Planned</td><td></td></tr><tr><td>P1</td><td><p>Restrict Block listed Words:</p><ul><li>Demographic details</li><li>Acknowledgement</li><li>Packet Approval</li></ul></td><td><i class="fa-github">:github:</i> <a href="https://github.com/mosip/android-registration-client/issues/644">644</a></td><td>🔵 Planned</td><td></td></tr><tr><td>P1</td><td>Calculation of Quality Score.</td><td><i class="fa-github">:github:</i> <a href="https://github.com/mosip/android-registration-client/issues/645">645</a></td><td>🔵 Planned</td><td></td></tr><tr><td>P1</td><td>SDK match score along with biometric score.</td><td><i class="fa-github">:github:</i> <a href="https://github.com/mosip/android-registration-client/issues/646">646</a></td><td>🔵 Planned</td><td></td></tr><tr><td>P1</td><td>OCR Integration.</td><td><i class="fa-github">:github:</i> <a href="https://github.com/mosip/android-registration-client/issues/647">647</a></td><td>🔵 Planned</td><td></td></tr><tr><td>P2</td><td>Telemetry.</td><td><i class="fa-github">:github:</i> <a href="https://github.com/mosip/android-registration-client/issues/648">648</a></td><td>🔵 Planned</td><td></td></tr></tbody></table>

### PMS (Partner Management System)

<details>

<summary>Vision</summary>

In 2026, the Partner Management System (PMS) will achieve a complete revamp with the GA release, focusing on enhanced partner lifecycle management, improved usability, multi-tenancy, and stronger governance controls. The module will support flexible partner configurations, streamlined onboarding, richer approval workflows, and better visibility into system impacts, while modernizing legacy components to deliver a scalable, secure, and user-friendly platform.

</details>

<table><thead><tr><th width="104.421875">Priority 🗓️</th><th width="343.12890625">Feature 🛠️</th><th width="93.796875">Details 📝</th><th width="153.96484375">Status 📊</th><th>Release 📌</th></tr></thead><tbody><tr><td>P1</td><td><strong>OIDC Client: Enhanced Configuration Support:</strong><br>Additional configurable fields with built-in multi-language support to address diverse client and regional requirements.</td><td><i class="fa-github">:github:</i> TBA</td><td><span data-gb-custom-inline data-tag="emoji" data-code="1f7e2">🟢</span> Completed</td><td><a href="https://github.com/mosip/partner-management-services/tree/1.3.0-beta.4">1.3.0-beta.4</a></td></tr><tr><td>P1</td><td><strong>ABIS Partner Management:</strong><br>Enable Partner Admins to manage the complete ABIS partner lifecycle, including partner creation, certificate management, and policy mapping.</td><td><i class="fa-github">:github:</i> TBA</td><td><span data-gb-custom-inline data-tag="emoji" data-code="1f7e2">🟢</span> Completed</td><td><a href="https://github.com/mosip/partner-management-services/tree/1.3.0-beta.4">1.3.0-beta.4</a></td></tr><tr><td>P1</td><td><strong>Simplified Partner Admin Onboarding:</strong><br>Enable direct login for Partner Admin users provisioned in keycloak with the Partner Admin role, eliminating the self-registration step in the PMS UI.</td><td><i class="fa-github">:github:</i> TBA</td><td><span data-gb-custom-inline data-tag="emoji" data-code="1f7e2">🟢</span> Completed</td><td><a href="https://github.com/mosip/partner-management-services/tree/1.3.0-beta.4">1.3.0-beta.4</a></td></tr><tr><td>P1</td><td><strong>Manual Adjudication Partner Flow by Partner Admin:</strong><br>Enable Partner Admins to manage the complete Manual Adjudication partner lifecycle, including partner onboarding, certificate configuration, and policy association through a unified administrative flow.</td><td><i class="fa-github">:github:</i> TBA</td><td>🟠 In-progress</td><td>1.3.0-beta.5</td></tr><tr><td>P1</td><td><strong>Print / Credential Partner Flow by Partner Admin:</strong><br>Supports end-to-end lifecycle management of Print and Credential partners by Partner Admins, from onboarding to certificate and policy setup.</td><td><i class="fa-github">:github:</i> TBA</td><td>🟠 In-progress</td><td>1.3.0-beta.5</td></tr><tr><td>P1</td><td><strong>Online Verification Partner Flow by Partner Admin:</strong><br>Unified admin flow for managing Onoine verification partner partners with certificate and policy configuration.</td><td><i class="fa-github">:github:</i> TBA</td><td>🔵 Planned</td><td></td></tr><tr><td>P1</td><td><strong>SDK Partner Flow by Partner Admin:</strong><br>Provides a dedicated admin workflow for managing SDK partners, covering onboarding, secure certificate handling, and policy configuration.</td><td><i class="fa-github">:github:</i> TBA</td><td>🔵 Planned</td><td></td></tr><tr><td>P2</td><td><strong>Multi-Partner Type Management for Partner Users:</strong><br>Enables partner users to onboard, switch between, and manage multiple partner types through a unified experience.</td><td><i class="fa-github">:github:</i> TBA</td><td>🔵 Planned</td><td></td></tr><tr><td>P2</td><td><p><strong>Multi-Tenancy and Partner Admin Enhancements:</strong></p><p>Enable organisation-specific data visibility across all users of a given partner organisation (Multi-tenancy). In the Partner Admin portal:</p><ul><li><strong>Partner Type Management</strong> – Approve, reject, or add new partner types.</li><li><strong>User Management</strong> – Approve, reject, or add new users.</li></ul></td><td><i class="fa-github">:github:</i> TBA</td><td>🔵 Planned</td><td></td></tr><tr><td>P2</td><td><strong>Legacy PMS API cleanup</strong></td><td><i class="fa-github">:github:</i> TBA</td><td>🔵 Planned</td><td></td></tr><tr><td>P3</td><td><p><strong>Partner Management System Enhancements:</strong></p><p>Improve PMS usability and governance with a unified landing page, in-context help, and UI refinements. Enable partner-type specific admin roles, richer approval workflows with comments, controlled partner policy deactivation, and visibility into the impact of deactivating OIDC clients, API keys, SBIs, devices, and FTMs across modules.</p></td><td><i class="fa-github">:github:</i> TBA</td><td>🔵 Planned</td><td></td></tr><tr><td>P4</td><td><strong>UI Design for mobile devices</strong></td><td><i class="fa-github">:github:</i> TBA</td><td>🔵 Planned</td><td></td></tr></tbody></table>

### Integrations

**CRVS**

<table><thead><tr><th width="343.12890625">Feature 🛠️</th><th width="131.12109375">Details 📝</th><th width="141.125">Status 📊</th><th width="250.1171875">Release 📌</th></tr></thead><tbody><tr><td>CRVS initiated infant demographic update flow support</td><td><i class="fa-github">:github:</i> TBA</td><td>🟠 In-progress</td><td></td></tr><tr><td>Add eSignet user info token validation for all requests coming to MOSIP</td><td><i class="fa-github">:github:</i> TBA</td><td>🔵 Planned</td><td></td></tr><tr><td>Support user information updates using handles (BRN, email, phone, etc.)</td><td><i class="fa-github">:github:</i> TBA</td><td>🔵 Planned</td><td></td></tr><tr><td>Implement ID schema constraints to limit CRVS modifications to death-specific fields in Death Registration workflows</td><td><i class="fa-github">:github:</i> TBA</td><td>🔵 Planned</td><td></td></tr><tr><td>Perform cleanup and deprecation of legacy components in the existing OpenCRVS integration (GitHub, properties, Camel routes)</td><td><i class="fa-github">:github:</i> TBA</td><td>🔵 Planned</td><td></td></tr><tr><td>Enhancement to return PSUT as the default credential to external partners following successful UIN generation</td><td><i class="fa-github">:github:</i> TBA</td><td>🔵 Planned</td><td></td></tr></tbody></table>

### Automation

<table><thead><tr><th width="100.4921875">Priority 🗓️</th><th width="169.44140625">Feature 🛠️</th><th width="319.6953125">Details 📝</th><th>Status 📊</th></tr></thead><tbody><tr><td>P1</td><td>UI automation clean up</td><td><ul><li>Clean up all platform modules.</li><li>Refactor reports for better readability.</li><li>Add a “Known Modules” bucket for tracking.</li></ul></td><td>🔵 Planned</td></tr><tr><td>P1</td><td>Independent API run execution</td><td><ul><li>Remove interdependency in API test rigs, to make the module wise test rigs run independent of other module</li></ul></td><td>🔵 Planned</td></tr><tr><td>P1</td><td>Infrastructure &#x26; Deployment Automation</td><td><ul><li>Enable automation using localhost/Docker Compose for services and applications (across modules).</li></ul></td><td>🔵 Planned</td></tr><tr><td>P1</td><td>DSL Development &#x26; Enhancement</td><td><ul><li>Add 25 new scenarios per quarter.</li><li>Ensure regular DSL releases (1 per quarter).</li></ul></td><td>🔵 Planned</td></tr><tr><td>P1</td><td>Enhance DSL to check for all notifications and their templates</td><td><ul><li>Have a DSL step check if the data in the templates are properly replaced or not as various notifications are sent by system at various stage</li><li><a href="https://mosip.atlassian.net/browse/MOSIP-28750">https://mosip.atlassian.net/browse/MOSIP-28750</a></li></ul></td><td>🔵 Planned</td></tr><tr><td>P2</td><td>Automation Coverage Target</td><td><ul><li>Achieve 75% automation coverage across all modules.</li></ul></td><td>🔵 Planned</td></tr><tr><td>P2</td><td>Documentation &#x26; Governance</td><td><ul><li><p>Documentation Update</p><ul><li>Update MOSIP docs for API, UI, and DSL.</li></ul></li></ul></td><td>🔵 Planned</td></tr><tr><td>P2</td><td>inji DSL Coverage</td><td><ul><li>Initiate DSL for Inji module (end-to-end flow).</li></ul></td><td>🔵 Planned</td></tr><tr><td>P2</td><td>Enhance inji automation coverage</td><td><ul><li>Review NA test cases.</li><li>Automate camera-related test cases.</li><li>Implement QR code generation using PixelPass library.</li><li>Validate QR code variations in Inji Verify.</li></ul></td><td>🔵 Planned</td></tr><tr><td>P2</td><td>Browser stack Integration</td><td><ul><li>Browser Stack integration need to do for Admin UI, PMP UI and Resident UI</li></ul></td><td>🔵 Planned</td></tr><tr><td>P2</td><td>To ensure the process adheres to the validation of the VC data model 1.1 or 2.0</td><td><a href="https://mosip.atlassian.net/browse/MOSIP-37656">https://mosip.atlassian.net/browse/MOSIP-37656</a><br><a href="https://mosip.atlassian.net/browse/MOSIP-37658">https://mosip.atlassian.net/browse/MOSIP-37658</a><br><a href="https://mosip.atlassian.net/browse/MOSIP-37655">https://mosip.atlassian.net/browse/MOSIP-37655</a><br><a href="https://mosip.atlassian.net/browse/MOSIP-37657">https://mosip.atlassian.net/browse/MOSIP-37657</a> <a href="https://mosip.atlassian.net/browse/MOSIP-31526">https://mosip.atlassian.net/browse/MOSIP-31526</a></td><td>🔵 Planned</td></tr><tr><td>P3</td><td>Infrastructure &#x26; Deployment Automation</td><td><ul><li><p>Deployment Testing Automation</p><ul><li>Automate deployment testing workflows.</li></ul></li></ul></td><td>🔵 Planned</td></tr><tr><td>P3</td><td>DSL Development &#x26; Enhancement</td><td><ul><li>Add 25 new scenarios per quarter.</li><li>Ensure regular DSL releases (1 per quarter).</li></ul></td><td>🔵 Planned</td></tr><tr><td>P3</td><td>Automation to Detect Changes in Stoplight</td><td><ul><li>Implement checks to ensure no changes in stoplight post-release/handover.</li></ul></td><td>🔵 Planned</td></tr><tr><td>P3</td><td>Commons Automation</td><td><ul><li>Automate MOSIP libraries/services.</li><li>Build a common library for UI test rigs.</li></ul></td><td>🔵 Planned</td></tr><tr><td>P4</td><td>DSL Development &#x26; Enhancement</td><td><ul><li>Add 25 new scenarios per quarter.</li><li>Ensure regular DSL releases (1 per quarter).</li></ul></td><td>🔵 Planned</td></tr><tr><td>P4</td><td>Documentation &#x26; Governance</td><td><ul><li><p>Reporting &#x26; Monitoring</p><ul><li>Maintain dashboards for DSL releases, coverage, and failures.</li></ul></li></ul></td><td>🔵 Planned</td></tr><tr><td>P4</td><td>Security and Sonar coverage</td><td><ul><li>Fix Security/Sonar bugs</li></ul></td><td>🔵 Planned</td></tr><tr><td>P4</td><td>Documentation &#x26; Governance</td><td><ul><li><p>Documentation Update</p><ul><li>Update MOSIP docs for API, UI, and DSL.</li></ul></li></ul></td><td>🔵 Planned</td></tr></tbody></table>

***

**Acronyms and Legends**:

<i class="fa-github">:github:</i> TBA - 'Github Issues Link - To Be Added'


---

# Agent Instructions: 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:

```
GET https://docs.mosip.io/1.2.0/roadmap-and-releases/roadmap/roadmap-2026.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.