Faable Auth guides
Each guide solves one real problem end to end, with code you can copy. New to Faable Auth? Do Get Started or a Quickstart first — the guides assume a tenant and a client already exist.
Build
| Guide | What it covers |
|---|---|
| Next.js: Face ID & Passkeys | Sign in with Face ID, Touch ID, Windows Hello or a hardware key — no password — plus step-up for sensitive actions. |
| MCP servers: add OAuth | Protect a remote MCP server with OAuth 2.1 — Dynamic Client Registration for Claude, Cursor and VS Code, and per-tool scopes. |
| PLCs & industrial gateways | A cryptographic identity per Node-RED gateway and short-lived tokens on the path to your API. |
| OPC UA servers → your API | Send OPC UA data from a gateway in the DMZ to your API, authenticated with Faable Auth. |
| Test and production tenants | Run a separate tenant for development — which values change and how to read the errors when one is left over. |
Migrate
| Guide | What it covers |
|---|---|
| Migrate from Auth0 | Map tenants, applications, connections and Actions, export your users and switch your OAuth integration. |
| Migrate from Clerk | Move from prebuilt components to a standards-based OAuth 2.0 / OIDC server hosted in Europe. |
| Migrate from NextAuth.js / Auth.js | Replace the route handler, auth() and the middleware; recreate providers as connections. |
| Migrate from Keycloak | Map realms, clients and identity providers, and stop running Keycloak yourself. |
| Import & export password hashes | Keep users’ existing passwords: bcrypt, scrypt, Firebase scrypt, PBKDF2 and Argon2id. |
Still deciding? See how Faable Auth compares to Auth0, Clerk & Keycloak.
Last updated on