Your site stops storing passwords, verifying email and dealing with second factors. It gets an answer to one question — who just arrived.
Prices depend on how many people sign in to your site. Pricing
# everything your library needs
https://auth.my/.well-known/openid-configurationSign-in by one-time emailed code, by passkey, through Google or Microsoft Entra. A password that does not exist cannot be stolen, guessed or reused elsewhere.
No proprietary protocol, no mandatory SDK. Whatever you already use will do: Auth.js, passport, Spring Security, mozilla-django-oidc.
Signing algorithm, PKCE, token refresh, CORS for single-page apps — set up the way your library expects out of the box. Nothing left to tune.
A company verifies its domains with a DNS record and gains authority over accounts in them. Joining once opens every application in the group.
Connected sites, last sign-in time, a revoke button. Plus a session log with devices.
Email addresses and phone numbers are stored encrypted; lookup goes through a separate index that cannot reveal the address.
In the console: a name and a redirect URI. The path is filled in for your library.
One. It fetches endpoints, keys and algorithms from there itself.
That is all. The user comes back to you already identified.
providers: [{
id: 'authmy', name: 'auth.my', type: 'oidc',
issuer: 'https://auth.my',
clientId: process.env.AUTHMY_CLIENT_ID,
clientSecret: process.env.AUTHMY_CLIENT_SECRET,
}]The full Next.js example is in the quickstart. There is also a version without a framework and one on plain HTTP.
So you do not go looking: document verification (KYC/KYB), SAML support — OpenID Connect only — separate sandbox and production environments, SCIM and automated user provisioning.
This list was last reviewed on
If one of these blocks your use case, write to [email protected] — it changes the order of work.