Roadmap 2025
Here we present the product roadmap for the entire Inji Stack for the calendar year 2025. The annual product cycle for the Inji Stack begins in January and concludes in December.
For detailed module-wise roadmaps, please refer to the following:
Prioritization: Through this roadmap the startegic or adaptive prioritization, if there is, has been indicated as below:
Add [ ➕ ]: Added new.
Strategic priortization [ ↑ ] : Brought ahead in schedule.
Adaptive reschedule [ ↓ ]: Is moved to approaching quarters.
Inji Wallet
Vision
In 2025, Inji Wallet will continue to ensure compatibility with diverse ecosystems by supporting multiple credential formats, such as mDoc/mDL, SD-JWT, and JWT. The wallet will also incorporate privacy-preserving mechanisms such as BBS+, selective disclosure, and one-time credentials, empowering users to retain full control over their personal information. Additionally, the wallet will enable multi-user credential sharing, addressing family-based use-cases such as ration cards and property deeds, further enhancing its versatility and real-world applicability.
The wallet’s roadmap includes critical features like OpenIDVP enhancements for cross-device and same-device flows, Shamir’s secret sharing for secure key recovery, ECC K1 and R1 key support. By enabling the seamless integration of features like credential offer endpoints and pre-authorized code flows (OpenID4VCI), Inji Wallet will cater to real-world use cases with ease.
The mobile and web interfaces of Inji Wallet will support high-performance operations, maintaining accessibility even in low-connectivity environments. With robust user login and profile management features, along with integration of play integrity on Android, the wallet will ensure a scalable, secure, and privacy-focused user experience.
By 2025, Inji Wallet aims to be a reliable, standards-compliant digital wallet, empowering users to manage their credentials while fostering trusted data exchange and seamless interoperability within the verifiable credentials ecosystem.
Inji Mobile
Q2
Cross-Device Enhancements for Credential Sharing
( OpenIDVP :Verifier Metadata Management)
🟢 Completed
Moved to Q2
Q2↑
Same Device Flow: Multiple credential requests during the presentation (OpenIDVP)
🟢 Complete
Moved to Q2 to Q3
Q3
OpenID4VCI Support for credential offer endpoint and pre-authorised code flow
🟢 Complete
Q4↓
W3C Data Model 2.0 & SVG Render Method
🟢 Complete
Moved to Q4 from Q2
2026↓
Presentation During Issuance
Moved to 2026 & Beyond
v0.22.0
Q4 Moved to 2026
2026↓
Support for Advanced Cryptographic Keys (ECC R1)
Moved to 2026 & Beyond
NA
Q4
Moved to 2026
2026↓
Secure Key Recovery with Shamir’s Secret Sharing
Moved to 2026 & Beyond
NA
Q3
Moved to 2026
2027↓
One-Time Use Credentials for Privacy
Moved to 2026 & Beyond
NA
Q4
Moved to 2027
Inji Web
Q4+
Enable Ed25519 2018 and 2020 Signature Suites for Guest Login (Without Login)
🟢 Complete
Added to Q4
2026↓
Support for Advanced Cryptographic Keys (ECC R1)
Moved to 2026 & Beyond
NA
Q4
Moved to 2026
2026↓
Secure Key Recovery Using Shamir’s Secret Sharing
Moved to 2026 & Beyond
NA
Q2
Moved to 2026
2026↓
OpenID4VCI Support for credential offer endpoint and pre-authorised code flow
Moved to 2026 & Beyond
NA
Q3
Moved to 2026
2026↓
Unified Key Management for Web & Mobile
Moved to 2026 & Beyond
NA
Q1
Moved to 2026
2027↓
One-Time-Use Credentials for Privacy
Moved to 2026 & Beyond
NA
Q3
Moved to 2027
Inji Certify
Vision
The goal of Inji Certify for the rear 2025 is to provide a comprehensive and user-centric platform for issuing, managing, and verifying credentials, tailored to meet the diverse needs of individuals, organizations, and issuers. With support for multiple credential formats (e.g., SD-JWT, mDoc/mDL), advanced cryptographic standards (ECC, BBS), and privacy-preserving mechanisms, the platform ensures secure and flexible credential handling.
By enabling features like multi-issuer onboarding, deferred issuance, subject-holder relationship management, and one-click authorization during issuance, Inji Certify addresses real-world scenarios such as sharing family credentials, automating bulk credential generation, and simplifying issuer interactions. The integration of offline capabilities (e.g., printable QR-embedded credentials) and scalable architecture ensures accessibility, even in low-connectivity environments, while maintaining performance benchmarks of up to 1 million credentials per day.
Inji Certify’s vision is to foster trust and interoperability in the digital identity ecosystem, empowering users with control over their credentials while providing issuers with a reliable and standards-compliant platform.
Q3↓
Credential Formats Support for - SD JWT
🟢 Completed
Moved to Q3 from Q1
Q3↓
Presentation during issuance of Credential
Moved to 2026 & Beyond
0.14.0
Moved to Q3 from Q2
Q3+
Claim 169 Support with QR Code Generation
Moved to 2026 & Beyond
0.14.0
Added to Q3
Q3
VC Generation: Create Credentials from the Request Payload
Moved to 2026 & Beyond
TBD
Inji Verify
Vision
Our vision for 2025 is to position Inji Verify as the go-to tool for seamless and secure credential verification. We aim to deliver easily configurable UI components for third-party verifier portals, tailored to meet the diverse needs of organizations across the globe. With support for multiple credential formats (SD-JWT, mDoc/mDL, W3C) and advanced cryptographic standards (ECC), Inji Verify ensures flexible and secure credential handling.
Inji Verify fosters trust and interoperability in the digital identity ecosystem. By introducing features like multi-proof capabilities, QR Based Verifiable Presentation in Same Device, SVG Rendering post VC verification, able to identify revoked credentials during verification, able to support credential correction, verification of documents with multiple QR codes, BLE Based verifiable presentation - Inji Verify will redefine user experience and reliability. With a focus on performance , enhanced design for an intuitive look and feel, and adherence to global standards (Data Model 1.1/2.0), the GA release will set new benchmarks for stability, usability, and excellence in digital verification.
Q1
OpenIDVP: Cross Device Flow (QR code based Verifiable Presentation)
🟢 Completed
Q1
Inji Verify SDK: OpenID4VP- VP Verification component (cross device flow) and publish as an NPM module
🟢 Completed
Q1
Migration of Inji Verify backend from H2 in memory DB to PostgreSQL DB
🟢 Completed
Q2
Inji Verify SDK: Scan/ Upload Component and publish as an NPM module
🟢 Completed
Q2
Server Setup for VC and VP Proof Verification in vc-verifier library
🟢 Completed
Q3
OpenIDVP Same Device Flow (via deeplink): Integrate to Inji Verify SDK
🟢 Completed
Q3
OpenID4VP Draft 23: Implement DID-based client_id Scheme
🟢 Completed
Q3
OpenID4VP: Authorization Request via request_uri for did client id
🟢 Completed
Q3
OpenIDVP: Same Device Flow in Inji Verify SDK (mobile device)
🟢 Completed
2026↓
Inji Verify SDK Support apart from React applications for Wider Framework Compatibility
Moved to 2026 & beyond
TBD
2026↓
OpenID4VP - Cross device and same device flows alongside Web wallets
Moved to 2026 & beyond
TBD
2026↓
Multi-language Support for VC during verification
Moved to 2026 & beyond
TBD
2026↓
Support for multi proof: Single credential should support multiple proofs
Moved to 2026 & beyond
TBD
Last updated
Was this helpful?