Introduction

NamoID provides branded Hosted Auth for consumer applications. Your application starts sign-in using a Client ID, NamoID performs the authentication ceremony, and the application receives a short-lived authorization code through standard OpenID Connect Authorization Code with S256 PKCE.

Use an official SDK to keep discovery, PKCE, state, nonce, callback validation, token exchange, refresh, revocation, and logout out of application code.

What you configure

Each application belongs to one project environment:

Workspace
└── Project
    ├── Test environment
    │   ├── Applications
    │   ├── End users
    │   └── Managed test users
    └── Live environment
        ├── Applications
        └── End users

An application has its own Client ID, registered callback URLs, application type, and sign-in policy. Confidential applications also have a Client Secret. Test and Live applications are separate trust boundaries and use different credentials, users, and issuers.

Choose an application type

Application	Credential	Recommended integration
Browser SPA	Client ID	@namoidhq/react or @namoidhq/js with PKCE
Server-rendered web app	Client ID and Client Secret	@namoidhq/nextjs or another confidential backend
Mobile or desktop	Client ID	OpenID Connect Authorization Code with PKCE

A Client ID identifies an application and is safe to expose. A Client Secret authenticates confidential server code and must never be placed in a browser, mobile binary, public repository, analytics event, or URL.

Supported sign-in experience

• Hosted redirect for the simplest and safest integration.
• Hosted popup for applications that want an in-page launch experience.
• Branded sign-in, sign-up, account, and waitlist pages when enabled.
• Email, password, passkey, social-provider, and MFA ceremonies configured in the Console.
• Managed Test users for repeatable email OTP testing without sending email.
• JavaScript, React, and Next.js SDKs.

NamoID keeps credentials, provider tokens, WebAuthn challenges, MFA, recovery, and consent inside Hosted Auth. See Login delivery modes before choosing a custom presentation.

Where to next

• Use Choose an integration to select the correct application type and SDK.
• Understand workspaces, projects, and Instances.
• Follow Getting started for your first integration.
• Read the NamoID Auth flow.
• Use the Next.js SDK, React SDK, or JavaScript SDK.
• Use Test users for safe email OTP testing.
• Review feature availability before relying on provider-specific or preview functionality.
• Complete the production launch checklist before moving real traffic to Live.
• Consult the Authentication API for the underlying protocol.