One identity product, built from India.
NamoID starts with customer identity and expands into authorization for AI clients. India operations, DPDP-readiness workflows, explicit consent, and environment-scoped OAuth provide the initial wedge; open standards provide the path to a wider market. Investor materials are shared by request.
One expanding identity product
Customer authentication and MCP authorization on one tenant, project, environment, issuer, and audit model.
Standards-led product surface
OAuth, OpenID Connect, PKCE, WebAuthn, JWKS, and refresh-token rotation as the baseline rather than a later enterprise add-on.
India and DPDP as the wedge
DPDP-focused consent, data-principal operations, audit history, minimisation, and India deployment context create a differentiated starting point.
Built for compounding adoption
A team can start with customer authentication, protect MCP resources, and later add broader delegated access without replacing its identity layer.
Identity is expanding from human login into delegated agent authorization.
Product teams already authenticate customers. Now AI clients need permission to reach tools, resources, and user data without inheriting a broad session or durable secret. The opportunity is a shared identity control plane where environment isolation, revocation, consent, and audit evidence compound across both surfaces.
Pitch deck request
A short note helps us route it.
- Your name, fund or angel profile, and investment focus
- Preferred email and LinkedIn profile
- Stage, cheque size, and whether you lead or follow
- Any specific questions you want covered before the first call
This page is not an offer to sell securities or a public solicitation. Investor materials are shared selectively after review.