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, Resident Portal, Android Registration Client and Partner Management System.
MOSIP Identity
Vision
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.
P1
ID Repository
Array of Handle - Phase 1.
TBA
🔵 Planned
P1
Registration Client & Processor
Enabling Custom Handles feature.
TBA
🔵 Planned
P1
Registration Processor
Biometric Adaptive Learning.
TBA
🔵 Planned
P1
ID Repository
Enhancement of ID Repository.
TBA
🔵 Planned
P1
Registration Processor
Update UIN through policy.
TBA
🔵 Planned
P1
Registration Processor
Enhancing Manual Adjudication.
TBA
🔵 Planned
P1
Key Manager
Supporting Quantum Safe Algorithms.
TBA
🔵 Planned
P1
Admin
Enhancement of Admin features.
TBA
🔵 Planned
P2
Platform/ Biometrics
(Reg Client & Reg Proc)
Biometric Quality Enhancement during Registration.
TBA
🔵 Planned
P2
Reporting/Dashboard
Anonymous Profile & Reporting Enhancement.
TBA
🔵 Planned
P2
Platform
Deactivation of SBI/FTM Partner.
TBA
🔵 Planned
P2
Registration Client
Auto upgrade during the slow / low network.
TBA
🔵 Planned
P2
Platform/ Notification Services
Notification Service Enhancement.
TBA
🔵 Planned
P3
Registration Client
Support for Document Scanner.
TBA
🔵 Planned
P3
ID Authentication
Data Insertion for IDA.
TBA
🔵 Planned
P3
Admin
General ID issuance features.
TBA
🔵 Planned
P3
ID Authentication
Age-Based Credential Attributes.
TBA
🔵 Planned
P3
Key Manager
Support for BBS+ in Key Manager.
TBA
🔵 Planned
P3
Key Manager
Key manager to support for software based key stores/vaults.
TBA
🔵 Planned
P4
Registration Client
Metadata Enhancement.
TBA
🔵 Planned
P4
ID Repository
Array of Handle - Phase 2.
TBA
🔵 Planned
Resident Portal
Vision
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.
P1
As a resident, User should be able to use all the services offered by resident portal using USSD services.
🔵 Planned
Android Registration Client
Vision
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.
P1
Centre Remapping
TBA
🔵 Planned
PMS (Partner Management System)
Vision
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.
P1
OIDC Client: Enhanced Configuration Support: Additional configurable fields with built-in multi-language support to address diverse client and regional requirements.
TBA
🟢 Completed
P1
ABIS Partner Management: Enable Partner Admins to manage the complete ABIS partner lifecycle, including partner creation, certificate management, and policy mapping.
TBA
🟢 Completed
P1
Simplified Partner Admin Onboarding: Enable direct login for Partner Admin users provisioned in keycloak with the Partner Admin role, eliminating the self-registration step in the PMS UI.
TBA
🟢 Completed
P1
Manual Adjudication Partner Flow by Partner Admin: Enable Partner Admins to manage the complete Manual Adjudication partner lifecycle, including partner onboarding, certificate configuration, and policy association through a unified administrative flow.
TBA
🟠 In-progress
1.3.0-beta.5
P1
Print / Credential Partner Flow by Partner Admin: Supports end-to-end lifecycle management of Print and Credential partners by Partner Admins, from onboarding to certificate and policy setup.
TBA
🟠 In-progress
1.3.0-beta.5
P1
Online Verification Partner Flow by Partner Admin: Unified admin flow for managing Onoine verification partner partners with certificate and policy configuration.
TBA
🔵 Planned
P1
SDK Partner Flow by Partner Admin: Provides a dedicated admin workflow for managing SDK partners, covering onboarding, secure certificate handling, and policy configuration.
TBA
🔵 Planned
P2
Multi-Partner Type Management for Partner Users: Enables partner users to onboard, switch between, and manage multiple partner types through a unified experience.
TBA
🔵 Planned
P2
Multi-Tenancy and Partner Admin Enhancements:
Enable organisation-specific data visibility across all users of a given partner organisation (Multi-tenancy). In the Partner Admin portal:
Partner Type Management – Approve, reject, or add new partner types.
User Management – Approve, reject, or add new users.
TBA
🔵 Planned
P2
Legacy PMS API cleanup
TBA
🔵 Planned
P3
Partner Management System Enhancements:
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.
TBA
🔵 Planned
P4
UI Design for mobile devices
TBA
🔵 Planned
Integrations
CRVS
CRVS initiated infant demographic update flow support
TBA
🟠 In-progress
Add eSignet user info token validation for all requests coming to MOSIP
TBA
🔵 Planned
Support user information updates using handles (BRN, email, phone, etc.)
TBA
🔵 Planned
Implement ID schema constraints to limit CRVS modifications to death-specific fields in Death Registration workflows
TBA
🔵 Planned
Perform cleanup and deprecation of legacy components in the existing OpenCRVS integration (GitHub, properties, Camel routes)
TBA
🔵 Planned
Enhancement to return PSUT as the default credential to external partners following successful UIN generation
TBA
🔵 Planned
Automation
P1
UI automation clean up
Clean up all platform modules.
Refactor reports for better readability.
Add a “Known Modules” bucket for tracking.
🔵 Planned
P1
Independent API run execution
Remove interdependency in API test rigs, to make the module wise test rigs run independent of other module
🔵 Planned
P1
Infrastructure & Deployment Automation
Enable automation using localhost/Docker Compose for services and applications (across modules).
🔵 Planned
P1
DSL Development & Enhancement
Add 25 new scenarios per quarter.
Ensure regular DSL releases (1 per quarter).
🔵 Planned
P1
Enhance DSL to check for all notifications and their templates
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
🔵 Planned
P2
Automation Coverage Target
Achieve 75% automation coverage across all modules.
🔵 Planned
P2
Documentation & Governance
Documentation Update
Update MOSIP docs for API, UI, and DSL.
🔵 Planned
P2
inji DSL Coverage
Initiate DSL for Inji module (end-to-end flow).
🔵 Planned
P2
Enhance inji automation coverage
Review NA test cases.
Automate camera-related test cases.
Implement QR code generation using PixelPass library.
Validate QR code variations in Inji Verify.
🔵 Planned
P2
Browser stack Integration
Browser Stack integration need to do for Admin UI, PMP UI and Resident UI
🔵 Planned
P2
To ensure the process adheres to the validation of the VC data model 1.1 or 2.0
🔵 Planned
P3
Infrastructure & Deployment Automation
Deployment Testing Automation
Automate deployment testing workflows.
🔵 Planned
P3
DSL Development & Enhancement
Add 25 new scenarios per quarter.
Ensure regular DSL releases (1 per quarter).
🔵 Planned
P3
Automation to Detect Changes in Stoplight
Implement checks to ensure no changes in stoplight post-release/handover.
🔵 Planned
P3
Commons Automation
Automate MOSIP libraries/services.
Build a common library for UI test rigs.
🔵 Planned
P4
DSL Development & Enhancement
Add 25 new scenarios per quarter.
Ensure regular DSL releases (1 per quarter).
🔵 Planned
P4
Documentation & Governance
Reporting & Monitoring
Maintain dashboards for DSL releases, coverage, and failures.
🔵 Planned
P4
Security and Sonar coverage
Fix Security/Sonar bugs
🔵 Planned
P4
Documentation & Governance
Documentation Update
Update MOSIP docs for API, UI, and DSL.
🔵 Planned
Acronyms and Legends:
TBA - 'Github Issues Link - To Be Added'
Last updated
Was this helpful?