Auth methods
Every way a user can sign in with Radon — email codes, magic links, passwords, Google, and the Pro methods.
A method is a way for a user to prove who they are. In Radon each method is a
provider you enable under providers, and each one is reachable both in code
(auth.emailCode.sendCode(...)) and as an HTTP route (POST /email-code/send)
once you mount a framework integration.
Enable as many as you like — thanks to merge-by-email, a user who signs in with a code today and Google tomorrow lands on the same account.
Free methods
Email code
A 6-digit code to their inbox. The simplest passwordless flow.
Magic link
A one-click sign-in link, no code to type.
Email + password
Classic signup/login with a full password-reset flow.
Sign in with Google — free, no license required.
Pro methods
OAuth (50 providers)
GitHub, Discord, Microsoft, Apple, and 46 more — one engine.
Passkeys / WebAuthn
Phishing-resistant biometric sign-in.
2FA / TOTP
Authenticator-app second factor on top of any method.
Phone / SMS OTP
A code over SMS instead of email.
How every method is shaped
Whichever you pick, the pattern is the same:
- Enable the provider in
providers. - Call it — either through the auto-mounted HTTP route from your frontend,
or directly via
auth.<provider>.<method>()in your own server code. - A session cookie is set on success (for HTTP routes), or you get back a
{ user }object (for direct SDK calls) to issue a session yourself.
Every method page below shows all three: the config, the HTTP route, and the direct SDK call.
Choosing a method
| If you want… | Use |
|---|---|
| The least friction, no passwords | Email code or Magic link |
| A familiar signup/login form | Email + password |
| Social sign-in | Google (free) or OAuth Pro |
| The strongest security | Passkeys Pro + 2FA Pro |
| To reach users without email | Phone / SMS Pro |