Customer Identity · public betaBuild your first Test integration.Create a Test project
NamoID

Product

Customer IdentityPublic beta · Hosted customer authenticationMCP AuthorizationDeveloper preview · Scoped AI-client accessAgent AccessDesign partner · External provider accessWorkforce IdentityDesign partner · Employee lifecycle and SSO
Startups

Developers

OverviewHosted Auth, OAuth/OIDC, and MCPDocumentationGuides & integrationAPI referenceEndpoints & schemas
Pricing

Trust

DPDP readinessChecklist & readiness reviewSecurityHow we protect your dataPrivacyHow we handle your data

Company

AboutWho we are & why we build thisCommunityBuild, learn, and collaborate on SlackSponsorshipsHackathons & tech fests we backBlogProduct & engineering notesBrandOfficial logos & usage guidanceInvestorsRequest the pitch deckContacthello@namoid.in
ConsoleTalk to an engineer Create Test project
For developers

Pick the identity path your application needs today.

Add Hosted Auth, complete the callback, and create your application session. Or use the environment issuer with a standards-compliant OpenID Connect library. MCP Authorization is available now for protected resources and scoped AI-client access.

Read the Hosted Auth quickstart View the API referenceStart with Next.js

Integrate with your stack

Use a NamoID package where one is available, or connect a standards-compliant OIDC client to your environment issuer. Support levels are labelled below.

  • NamoID packages: JavaScript, React, and Next.js
  • Standard OIDC clients: Node.js and Python
  • Standard OIDC clients: Java and Go
  • Standard OIDC clients: Ruby, PHP, .NET, and Rust
  • Protocol integration with discovery, JWKS, and curl

github.com/namoidhq/namoid-examples

Integration paths

Start Hosted Auth

Send the browser to your environment Auth URL and let NamoID render sign-in and sign-up.

Complete the callback

Verify state, exchange the single-use code on your backend, and create your application session.

Validate OIDC tokens

Read discovery from the environment issuer and verify signed tokens locally against public JWKS.

Protect an MCP server

Register one protected resource and enforce its audience, scopes, and expiry.

Keep application sessions server-side

Complete confidential callbacks and create your own application session without exposing credentials to the browser.

Move from Test to Live

Keep users, credentials, callbacks, providers, and policy inside explicit environment boundaries.

Standards, not surprises

Customer Identity today: OAuth · OpenID Connect (discovery + JWKS) · PKCE S256 on authorization-code requests · RS256 / JWKS · WebAuthn / passkeys · TOTP MFA · refresh-token rotation with replay detection · MCP resource authorization. In development: Workforce Identity, DPoP, and governed Agent Access.

No implicit grant. No password grant. PKCE required even for first-party clients.

Built for developers to trust

  • Public docs and API reference
  • JavaScript and Next.js integration packages
  • JavaScript, React, and Next.js SDK guidance
  • A status page
  • Release notes and changelog
Create a Test project Read the docsBook an integration review