IntelliAuth gives your app authentication, sessions, and authorization without you having to maintain any of it. Drop an SDK in, point it at your tenant, and your users can sign in with email + password, social providers, WebAuthn, SAML, or whatever you've enabled on the tenant. Tokens, refresh, MFA, risk signals — all handled.
This is the developer audience of the docs. You'll find here:
- Quickstarts that get you to a working login in under five minutes. React and Node are the two entry points.
- Concepts — the small vocabulary you need to read the rest of the docs. Tenants, applications, scopes, sessions, AAL, MFA — none of these are unique to IntelliAuth but each has our specific shape worth knowing.
- OAuth + OIDC flow guides — authorization code with PKCE, client credentials, device code, token exchange, refresh rotation. Pick the flow that matches your app shape.
- SDK reference — every method on
@intelliauth/react-sdkand@intelliauth/node-sdk, with parameters + returns + error codes. - API reference — the HTTP surface, generated from the OpenAPI specs. Same endpoints the SDKs use under the covers.
- Tutorials — longer-form recipes (build a SaaS, migrate from Auth0, add step-up MFA to Next.js).
- Troubleshooting — common errors mapped to causes + fixes.
Where to start
Section titled “Where to start”The honest answer depends on what you're building:
- Browser app (React, Vue, Svelte) → Quickstart — React. The React SDK works as a drop-in; the same shape applies to other frameworks via the framework-agnostic
AuthClient. - Backend API (Node, Express, Next.js API routes) → Quickstart — Node. The Node SDK gives you session validation middleware + a management client for admin actions.
- Mobile / native app → start with the authorization code + PKCE for native flow guide; SDKs for iOS and Android are on the roadmap.
- Machine-to-machine integration → client credentials flow. No user, no consent, just tokens.
If you're not sure what shape you have, read Core concepts first — five minutes to understand the vocabulary, then come back here.
What you'll need before you start
Section titled “What you'll need before you start”Two things:
- An IntelliAuth organisation. Sign up at your IntelliAuth control plane URL (your platform admin can share it; if you're the platform admin, you set it up).
- A tenant under your organisation. Your platform admin provisions tenants in the IntelliAuth admin console — ask them, or do it yourself if you're the admin too.
Once you have a tenant, you have a tenant URL (https://<tenant-slug>-<org-slug>.<domain>). The quickstarts walk you through registering an application inside the tenant + dropping the SDK into your code.