How Ferriskey has been taking shape, release after release.

• Implements the complete OAuth 2.0 Device Authorization Flow (RFC 8628): device authorization endpoint, device_code token grant, verification page, and CIAM console configuration.
• Ships a portal theming builder with per-page layouts, design tokens, live preview, and an iframe-based editor to fully customize the hosted login portal.
• Adds CIAM application management, resume-OAuth-after-password-reset, basic auth support, and several OIDC discovery and nonce compliance fixes.

With operational control settled in 0.6, the 0.7 line turns toward developer-facing protocol coverage and end-user branding — making FerrisKey both more standards-complete and more customizable.

• Ships a first-class maintenance mode across the full stack, letting administrators halt user-facing operations gracefully during upgrades or incidents while retaining admin access.
• Adds user attributes support so realms can store arbitrary key-value metadata on users and propagate them into tokens via protocol mappers.
• Integrates OpenTelemetry tracing and OTLP log bridge for seamless compatibility with observability stacks such as Grafana Tempo and Jaeger.

Building on the passwordless and multi-tenant foundations of 0.5.0, this release shifts focus to operational control and extensibility — giving platform teams the tools to manage identity infrastructure with greater confidence.

• Adds native WebAuthn passkeys for passwordless authentication without heavy external infrastructure.
• Introduces Magic Link sign-in for teams that want a simpler passwordless user experience.
• Ships organizations and email builder theming so tenants and transactional emails can be managed directly from Ferriskey.

After the 0.4 line focused on observability, recovery, and token control, 0.5.0 turns that foundation into a more complete end-user and multi-tenant experience.

• Introduces client scopes, mappings, migrations, and API support for better token composition.
• Launches Compass runtime, database layer, API endpoints, and UI to inspect authentication flows.
• Adds password reset and SMTP management building blocks, including UI and infrastructure.

Once federation was established in 0.3.0, the next logical move was to improve policy control, visibility, and recovery across the sign-in journey.

• Adds the Abyss federation module and user federation entities and migrations.
• Ships social auth APIs, LDAP provider CRUD, sync and connection test endpoints.
• Improves login UX, error detail quality, and permissions hydration in the app.

At this point the project stops being only an internal IAM console and starts addressing real-world enterprise identity integration problems.

• Introduces webhook notifications and required actions in the authentication journey.
• Expands admin UX with realm settings, login settings, IdP overview, and UI polish across clients and roles.
• Lays groundwork for SeaWatch and strengthens deployment support with TLS and Docker improvements.

From here the roadmap opens up: not just authenticating users, but integrating identity events into the rest of the platform.

• Delivers the foundational IAM surface: realms, clients, roles, permissions, users, and authentication endpoints.
• Ships the first admin portal flows, including login, client management, role management, and user management.
• Adds Helm, operator, Docker, metrics, and documentation so Ferriskey can be evaluated as a real platform.