Introduction

Axowl is an authentication and identity platform built around one idea: authority is a sealed, verifiable history of decisions — not a mutable snapshot. Every consequential action (a login, a role grant, a key rotation, a permission check) is recorded into a tamper-evident, cryptographically sealed chain that can be independently verified.

What you get

Authentication

Passkeys (WebAuthn), magic links, social login, and enterprise SSO (OIDC + SAML) — for your end users and your org members.

Organizations & RBAC

Multi-tenant organizations, members, roles, and a fine-grained permission model with a sealed audit trail.

Sealed integrity

Records are hash-chained and sealed; tampering is detectable and decisions are independently verifiable.

SDKs

Identity, Integrity, Eventing, and Korean-Identity client SDKs for consumer apps.

Two audiences, two surfaces

Axowl serves two distinct callers, and the docs are organized around that split (see Authentication model):

Org members sign in to the Axowl dashboard to manage their organization (members, roles, applications, keys).
End users sign in to your application through Axowl-hosted login or the SDK; you never handle their credentials.

Where to start

Quickstart Stand up hosted login for your app in minutes.

Authentication model Understand org-native vs. end-user auth before you build.