Realms and IAM objects
availableManage realms, clients, users, roles, organizations, client scopes, and protocol mappers from the IAM surface.
Roadmap
A directional view of what is being worked on now, what is coming next, and which longer-term bets matter most.
On desktop, scrolling down moves the roadmap forward from Now to Next to Later.
Current capabilities
What Ferriskey already provides today across IAM, deployment, security, and operations.
Manage realms, clients, users, roles, organizations, client scopes, and protocol mappers from the IAM surface.
Support OIDC, LDAP, and external identity providers for federated authentication scenarios.
Cover Magic Link, Passkeys, reset password, TOTP, and core grant types including password, client credentials, and refresh token.
Configure mail templates, token lifetimes, and authentication-related communication flows.
Ship with Helm, Docker, and Kubernetes support for platform-oriented deployments.
Use Compass and SeaWatch to audit authentication flows, debug behavior, and inspect IAM event logs.
Expose webhooks and bitwise permissions for event-driven integrations and fine-grained IAM administration rights.
Next steps
The next product areas being shaped to make Ferriskey more complete and easier to operate.
Build a configurable portal experience and a clearer way to define authentication journeys.
Define and specify the dedicated authorization service before turning it into a stable product surface.
Add organization groups and a session management API for better administration of tenants, users, and active access.
Introduce brute-force protection, rate limiting, OAuth 2.1 compliance, and Token Exchange support based on RFC 8693.
Deliver user self-service accounts, client evaluation tooling, and a CLI for operators and developers.
Document and support migration paths from Supabase, Keycloak, Auth0, and other existing identity stacks.
Move toward first-class multi-tenancy with quotas and stronger tenant isolation semantics.
Explore device trust and device binding as first-class building blocks for passwordless authentication.
Long term
Longer-horizon bets for policy, authorization, secrets, identity standards, and adaptive security.
Use OPA to attach policy rules directly to authentication flow decisions.
Store critical material such as keys and client secrets in a Vault-backed architecture.
Evaluate AuthZEN compliance and fine-grained authorization as the authorization surface matures.
Expose Ferriskey capabilities through an MCP server for agentic and automation-oriented workflows.
Explore DID and Verifiable Credentials for decentralized identity use cases.
Use risk scoring to adapt authentication requirements to context and suspicious behavior.
Current capabilities
What Ferriskey already provides today across IAM, deployment, security, and operations.
Manage realms, clients, users, roles, organizations, client scopes, and protocol mappers from the IAM surface.
Support OIDC, LDAP, and external identity providers for federated authentication scenarios.
Cover Magic Link, Passkeys, reset password, TOTP, and core grant types including password, client credentials, and refresh token.
Configure mail templates, token lifetimes, and authentication-related communication flows.
Ship with Helm, Docker, and Kubernetes support for platform-oriented deployments.
Use Compass and SeaWatch to audit authentication flows, debug behavior, and inspect IAM event logs.
Expose webhooks and bitwise permissions for event-driven integrations and fine-grained IAM administration rights.
Next steps
The next product areas being shaped to make Ferriskey more complete and easier to operate.
Build a configurable portal experience and a clearer way to define authentication journeys.
Define and specify the dedicated authorization service before turning it into a stable product surface.
Add organization groups and a session management API for better administration of tenants, users, and active access.
Introduce brute-force protection, rate limiting, OAuth 2.1 compliance, and Token Exchange support based on RFC 8693.
Deliver user self-service accounts, client evaluation tooling, and a CLI for operators and developers.
Document and support migration paths from Supabase, Keycloak, Auth0, and other existing identity stacks.
Move toward first-class multi-tenancy with quotas and stronger tenant isolation semantics.
Explore device trust and device binding as first-class building blocks for passwordless authentication.
Long term
Longer-horizon bets for policy, authorization, secrets, identity standards, and adaptive security.
Use OPA to attach policy rules directly to authentication flow decisions.
Store critical material such as keys and client secrets in a Vault-backed architecture.
Evaluate AuthZEN compliance and fine-grained authorization as the authorization surface matures.
Expose Ferriskey capabilities through an MCP server for agentic and automation-oriented workflows.
Explore DID and Verifiable Credentials for decentralized identity use cases.
Use risk scoring to adapt authentication requirements to context and suspicious behavior.