Keycloak is the identity engine in Covenant
Keycloak is an open-source identity and access management server. It handles authentication, identity federation and standards-based tokens. A team can run it in its own infrastructure, configure clients and authentication flows, and use its administration interfaces to manage identities.
Covenant uses Keycloak for sign-in in its working pilot. The console manages the work that comes after authentication for a SaaS product with individuals, company workspaces and regional reseller relationships. The choice is how much of that work your team wants to assemble, operate and support.
The Covenant side of this comparison reflects a local pilot verified with synthetic accounts. Keycloak capabilities refer to the upstream project. Production security and availability depend on the infrastructure, configuration and operations for the deployment you choose.
Side-by-side comparison
| Capability | Covenant | Keycloak |
|---|---|---|
| Standards and factors | Local Keycloak-backed OIDC with PKCE and WebAuthn passkeys. Passkey step-up protects privileged console actions. | OIDC, SAML, identity brokering, and configurable WebAuthn authentication flows. |
| Company identities | Personal, company and reseller workspaces with invitations and workspace roles. | Organizations, members, groups, invitations and organization-specific identity brokering within a realm. |
| Reseller onboarding | A company owner grants access for a specific company. A delegate can invite members, and the owner can revoke the grant. | Use Keycloak users, roles and delegated administration as primitives. Model customer assignment and reseller permissions in your app. |
| Directory provisioning | Customer SCIM and directory lifecycle workflows are on the roadmap. | Keycloak 26.8 offers a preview realm-level SCIM API for users and groups. |
| Hosting and operations | Independent Canadian and EU deployments are planned. Production processor verification and recovery drills are pending. | Your team selects the infrastructure, regions, providers, backup policy and support model. |
Keycloak server administrationKeycloak release notesKeycloak production configuration
Where direct Keycloak gives you control
A team that already operates Keycloak can keep its existing realm layout, authentication policies and integration lifecycle. It can tune a realm for a shared application or separate workloads across deployments when isolation warrants it. Organizations add customer context inside a realm. Where a contract requires isolation of keys, databases, backups or operators, the deployment design needs to enforce that boundary.
Direct operation is especially attractive if your enterprise requirements already cover external SAML or OIDC identity providers, your engineers maintain the login experience and customers never need a reseller access model. You get Keycloak’s native tools and choose how the application exposes them. Preview SCIM can inform a test plan. Its release status and realm-level scope matter if your customers expect org-scoped, supported offboarding.
Where Covenant adds a SaaS workspace model
Consider a software company that supports individual subscribers, customer organizations and a reseller who helps a few accounts get started. In Covenant, the reseller works from an assigned-company list. The customer company grants that relationship. It can revoke it when onboarding ends. The delegate has a member-invitation workflow, while the company owner retains administrative changes and the company’s audit history stays with its owner and admins.
This workflow turns a permission model into screens a customer can use. The dashboard shows the current workspace, role, configured region and environment. The browser test exercises account verification and return to the selected workspace, the delegate view and the company admin’s activity view. These are concrete pilot behaviors to evaluate with your own synthetic onboarding scenario.
Security and operating cost
Assess the two layers independently. For the identity engine, ask who patches Keycloak, how operators reach its admin interfaces, which factors privileged sign-in requires, and how signing keys rotate. For the customer application, review each role’s server-side permissions, when grants take effect, where audit events go, and what happens to active sessions during recovery and offboarding.
For self-hosted Keycloak, model compute and database capacity, backups, monitoring and engineering time for incident response and upgrades. For Covenant, request pilot scope and commercial terms as you evaluate the product. Covenant’s production gates include regional isolation, timed restores, processor verification and external security review. Its local evidence is a useful starting point for defining those acceptance tests.
Pilot or migration plan
Inventory clients and realms
Record which issuers, subject identifiers, callbacks, role claims, identity providers and account actions each application depends on. Include external support and mail services in your data-flow map.
Test one representative customer
Keep the existing Keycloak deployment for active users and prove the target sign-in and workspace flow in an isolated environment. Include a company owner, an admin, a reseller invite and revocation, plus a personal account.
Plan the cutover around identities
Decide how existing users map to the destination issuer and subject. Test session handling, recovery and passkey enrollment continuity explicitly. Define a rollback trigger and measure the time it takes to restore access.
Which fits your team?
Run Keycloak directly when you want to own identity infrastructure and your application already handles customer onboarding and permissions. Evaluate Covenant when customer-owned reseller access and regional processing evidence are priorities and your first design partners can start with an invite and passkeys in a synthetic pilot. Teams that need production SAML, managed directory provisioning or a launch SLA today should evaluate a production setup with those capabilities enabled.