Authaz logoAuthaz
DocumentationAPI Reference
  • Get Started

    • Authaz
    • Core Concepts
    • Set up your app
    • Quickstart — cURL
  • Authentication

    • Authentication Settings
    • Signup
    • Invitations
    • Password Authentication
    • Multi-Factor Auth
    • Magic Link
    • OAuth / Social Login
    • Passkey (WebAuthn)
    • SAML SSO
    • Machine-to-Machine (M2M)
    • API Keys
  • 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)
  • Recipes

    • Recipes & Cookbook
    • Next.js — first integration
    • Next.js — B2B SaaS (multi-tenant)
    • Hono — first integration
    • Hono — B2B SaaS (multi-tenant)
    • React SPA — first integration
    • React SPA — B2B SaaS (multi-tenant)
    • .NET — first integration
    • .NET — B2B SaaS (multi-tenant)
  • Reference

    • Tokens
    • API Reference
    • Errors & Troubleshooting
  • Documentation

    • How Authaz is Built
  1. Authaz
  2. Docs
  3. Recipes
  4. Recipes & Cookbook

Recipes

Recipes & Cookbook

2 min read·Updated Jun 19, 2026

End-to-end configurations for common project shapes. Each recipe walks from "create the application" to "user is signed in and protected routes work" in one page, using the Authaz SDK for that stack.

If you're new to Authaz, read getting-started and architecture first; the recipes assume you've seen those.

Pick a recipe#

Next.js (@authaz/next)Hono (@authaz/hono)React SPA (@authaz/react).NET (Authaz.Sdk)
Single-tenantNext.js — first integration
Previous
Quickstart — .NET (Authaz.Sdk)
Next
Next.js — first integration
Hono — first integration
React — first integration
.NET — first integration
Multi-tenantNext.js — B2B SaaSHono — B2B SaaSReact — B2B SaaS.NET — B2B SaaS

The React recipes pair with a backend that runs the Authaz handler — typically the Hono recipe on the same column. Pick a row × column based on your stack.

Single-tenant = one user pool per application. Best for consumer apps, internal tools, or any app where users don't belong to "workspaces" or "tenants."

Multi-tenant = your customers are tenants, each with their own users and roles. The shared-pool model (used here) lets one user belong to multiple tenants with different roles in each.

How to read a recipe#

Every recipe follows the same nine sections:

  1. What you'll build — the goal in one sentence.
  2. Application setup — Dashboard or POST /api/v1/applications.
  3. Install — exact package command.
  4. Configure — env vars or settings file.
  5. Wire it up — minimum-viable code.
  6. Read the user (and tenant, where applicable).
  7. Protect a route.
  8. Common gotchas — real failure modes, not generic advice.
  9. Next steps — three deeper-reading links.

Snippets are copy-paste runnable. Replace placeholder values (client IDs, secrets, your domain) with your real ones.

Going deeper#

  • Architecture — how Authaz fits together at a system level
  • Authentication providers — every login method available
  • Multi-tenancy — tenancy models and isolation guarantees
  • Authorization — roles, permissions, the Zeratul engine
  • Security policies — password, session, MFA, lockout
  • Management API reference — the full API surface