Get practical setup help
Discuss Hosted Auth, OAuth, OpenID Connect, passkeys, MCP authorization, and the integration decisions around them.
Product
Customer IdentityPublic beta · Hosted customer authenticationMCP AuthorizationDeveloper preview · Scoped AI-client accessAgent AccessDesign partner · External provider accessWorkforce IdentityDesign partner · Employee lifecycle and SSODevelopers
OverviewHosted Auth, OAuth/OIDC, and MCPDocumentationGuides & integrationAPI referenceEndpoints & schemasTrust
DPDP readinessChecklist & readiness reviewSecurityHow we protect your dataPrivacyHow we handle your dataNamoID is a developer identity platform for branded customer authentication and scoped authorization when AI clients need access. Join the people building, evaluating, and learning around those boundaries.
Free to join · Developers, founders, and security practitioners welcome
The community is for concrete questions, honest product feedback, and shared learning—not inflated compliance promises or generic AI noise.
Discuss Hosted Auth, OAuth, OpenID Connect, passkeys, MCP authorization, and the integration decisions around them.
Share what you are building, compare approaches with other builders, and give feedback that can shape NamoID.
Learn with people who care about least privilege, inspectable consent, privacy, and safer access for AI clients.
Customer Identity is available in public beta with Hosted Auth, social login, passkeys, MFA, users, sessions, and audit.
MCP Authorization is available now, giving approved AI clients their own resource, scope, audience, expiry, and revocation boundary.