What is Sudomimus

Sudomimus is an identity provider and authentication platform designed to be embedded into web, desktop, native, and OIDC-compatible applications. It provides a unified way to:

• Authenticate end users via multiple methods — passkeys (WebAuthn), email one-time passwords, social sign-in (Google, GitHub, Discord, Battle.net, X), Steam (in-game ticket or “Sign in with Steam”), and AccessKey credentials for headless clients — with more being added over time.
• Exchange short-lived tokens through the Connect flow, device authorization, native direct-issue, or standard OIDC.
• Act as a standard OpenID Connect provider for relying parties that prefer authorization_code + PKCE over the Connect protocol.
• Manage users by domain — claim a domain you own, then decide platform-wide how its users authenticate: allow, block, or force them through your own identity provider.
• Apply a three-layer allowlist to session admission and identity disclosure. Integrating applications remain responsible for their own business roles, permissions, resources, and authorization policy.

Why Sudomimus

Most applications end up reinventing the same authentication primitives: session storage, password resets, email verification, social login, MFA. Sudomimus separates the identity layer from the application layer, so authentication runs on Sudomimus and your application only deals with verified tokens.

Public services

Sudomimus exposes four peer integration paths across six public services. Choose an integration path is the current capability map for their audiences, endpoints, and protocol responsibilities.

Where to go next

• Building a web app with Connect? Start with the Quickstart, then the Connect flow.
• Building a CLI, launcher, or public client? Go to Device authorization.
• Integrating a desktop app, game, or client with Steam/AccessKey/PublicKey credentials? Go to Native integration.
• Wiring up an OIDC relying party? Go to the OIDC flow.
• Want to understand the shared model first? Read Authentication philosophy and Accounts and credentials.

Registering your application

Applications are created and managed through the developer portal at with.sudomimus.com — that is where you obtain your applicationAnchor, receive the application-creation client-auth private key, and configure the three layers of rules. The private key is not available from ordinary application reads; an unchanged uncertain-result retry can recover the exact create result for ten minutes. Quickstart links to the exact pages.