Documentation
Build sign-in your users trust
Guides and references for adding Authio to your apps, securing your APIs and running your own dedicated environment.
Popular guides
QuickstartCreate a realm and a client in the console, then sign a user in to a Next.js app with Auth.js — in about ten minutes.Next.jsUse authio-provider-nextauth in production: Auth.js v5 or NextAuth v4, scopes, typed claims, refresh tokens, protected routes and sign-in in a popup..NETProtect ASP.NET Core APIs, call APIs from workers with client credentials and sign SPAs in through a Backend-for-Frontend with the Authio .NET packages.MCP serversProtect an MCP server so MCP clients such as Claude Code find your realm, sign the person in and call your tools with a token issued for your server alone.Dedicated environmentA complete Authio deployment for your account alone — its own API, console, PostgreSQL and Redis — provisioned once you pay and operated from your console.OpenID Connect endpointsEvery protocol address of a realm — discovery, JWKS, authorization, token, UserInfo, introspection, revocation, end session and device authorization — with parameters and examples.
Browse by topic
Get started
What Authio is, the ideas it is built on, and a signed-in user in a few minutes.
Authentication
The hosted login, passkeys, multi-factor, connections, sessions and the policies behind them.
Authorization
Roles, scopes, organizations and the APIs your tokens are issued for.
Integrate
Next.js, .NET, MCP servers, any OpenID Connect client, services and devices.
Platform
Webhooks, audit, the AI advisor, connected accounts and migrating users in.
Dedicated environment
Your own Authio on infrastructure of its own: how it is provisioned, run and reached.
Account and billing
Plans, the trial, usage billing, your team and its access.
Reference
Endpoints, the admin API, error codes and the vocabulary used everywhere.