DhokoAuthaz
DocumentationAPI Reference
  • Get Started

    • Authaz
    • Core Concepts
    • Quickstart — cURL
  • Authentication

    • Authentication Settings
    • Signup
    • Password Authentication
    • Multi-Factor Auth
    • Magic Link
    • OAuth / Social Login
    • Passkey (WebAuthn)
    • SAML SSO
    • Machine-to-Machine (M2M)
    • API Keys
    • Invitations
  • Authorization

    • Authorization
    • Resources
    • Policies
    • Roles
    • Access Explorer
  • Tenancy

    • Multi-tenancy
    • Tenancy Customization
  • Brand & Host

    • Branding
    • Custom Domains
    • Communications & Email Templates
  • Operate

    • Users
    • Analytics
    • Audit Logs
    • Application Settings
  • SDK Quickstarts

    • Quickstart — Next.js
    • Quickstart — React SPA
    • Quickstart — Hono
    • Quickstart — .NET (Authaz.Sdk)
  • Reference

    • Tokens
    • API Reference
  1. Authaz
  2. Docs
  3. Get Started
  4. Authaz

Get Started

Authaz

3 min read·Updated Apr 29, 2026

Authaz is an authentication and authorization platform built for B2B SaaS. Drop it into your application and you get login pages, social sign-in, multi-factor auth, role-based permissions, multi-tenant isolation, and machine-to-machine credentials — without writing any of it yourself.

curl https://your-app.authaz.io/api/v1/users \
  -H "X-API-Key: your_api_key"

That's the whole hello-world: a typed, paginated user list scoped to your application.

Why Authaz#

  • Multi-tenant by design. Your customers each get their own user pool, roles, and configuration. Pick shared-pool or fully-isolated tenancy — the API is the same either way.
  • Fine-grained authorization. A Zanzibar-style relation engine (Zeratul) checks permissions in under a millisecond, even with millions of users and resources.
  • Universal Login out of the box. Hosted login, signup, MFA, social sign-in, and password reset pages. Customizable to your brand and domain.
  • Every common auth method. Email/password, social (Google, Microsoft, GitHub, Apple), magic links, machine-to-machine, API keys, passkeys.
  • Standards, not ceremony. OAuth 2.0 with PKCE, OIDC userinfo, JWKS for token verification. Bring any OAuth-aware client.

How it works

Next
Core Concepts
#

Your app sends users to Authaz Universal Login. Authaz authenticates them using whichever providers you've enabled, then redirects back with an authorization code. Your backend exchanges the code for an access token and an ID token. Done.

                ┌─────────────┐
   ┌─────────── │  Your App   │ ────────────┐
   │            └─────────────┘             │
   │ 1. redirect to                         │ 4. session
   │    Universal Login                     │    cookie set
   ▼                                        │
┌──────────────────────────────────────────────┐
│         Authaz Universal Login               │
│  Password │ OAuth │ Magic Link │ Passkey     │
└──────────────────────────────────────────────┘
   │ 2. user authenticates                   ▲
   │                                         │ 3. exchange code
   ▼                                         │    for tokens
┌──────────────────────────────────────────────┐
│              Authaz API (HTTPS)              │
│   /oauth2/authorize  /oauth2/token  /v1/...  │
└──────────────────────────────────────────────┘

Permission checks (Can this user delete this invoice?) hit the same backend through /api/v1/authorization/check — typically returning in under a millisecond.

Concepts in 30 seconds#

  • Organization — your company. One per Authaz customer. Holds billing and team members.
  • Application — a product you're shipping. Has its own auth providers, users, roles, and branding. One organization can run several applications.
  • Tenant (optional) — your customers' workspaces inside an application. Skip if your app isn't multi-tenant.
  • User — someone who signs in to your application.
  • Role — a named set of permissions assigned to users, optionally scoped to a single tenant.
  • Provider — a way to sign in (password, social, magic link, passkey, M2M, API key).

The full picture lives in Core Concepts.

Get started#

Pick the path that matches your stack:

QuickstartWhen to pick it
cURL / any languageYou want to see the OAuth flow end-to-end before committing to an SDK. 5 minutes.
Next.jsApp Router app. Uses @authaz/next.
React SPAVite, CRA, or any React app talking to its own backend. Uses @authaz/react.
HonoHono backend (Node, Bun, Cloudflare Workers, Deno). Uses @authaz/hono.
.NETASP.NET Core service calling the Management API. Uses the Authaz.Sdk NuGet package.

After the quickstart, the Multi-tenancy guide is the most useful read — it covers the model that drives everything else.

What's covered#

The docs mirror the dashboard's per-application tabs.

Foundations

  • Core Concepts — Organizations, applications, tenancy, providers, users, roles, Universal Login.
  • Multi-tenancy — Single, shared-pool, and isolated-pool models.
  • Tenancy Customization — what each tenant can customize (branding / emails / auth stack).

Authentication tab

  • Signup · Invitations
  • Password · Multi-Factor Auth · Magic Link
  • OAuth / Social · Passkey · SAML SSO
  • Machine-to-Machine · API Keys
  • Authentication Settings — redirect URIs, scopes, token lifetimes, session policy

Authorization tab

  • Authorization overview
  • Roles · Policies · Resources · Access Explorer

Other application tabs

  • Users · Branding · Custom Domains
  • Communications & Email Templates
  • Analytics · Audit Logs · Application Settings

Reference

  • Tokens — access, ID, and refresh tokens. Claims, lifetimes, JWKS, rotation, userinfo, introspection.
  • API Reference — auth, sections, and an interactive endpoint browser.

If something feels missing, that's likely on the roadmap — Authaz is shipped continuously.