HelixIAM by KubeDNA

Keycloak alternative

A Keycloak alternative with keys you hold and European eID connectors included.

Keycloak is a capable and widely used identity server; if it meets your needs, keep it. Organisations come to HelixIAM when they need several things together: EU eID connectors, agent governance, HSM-held keys and one accountable vendor.

When organisations look furtherSeveral needs, together
European eIDs
DigiD, eHerkenning and eIDAS connectors included
AI agents
Owner, lifecycle and delegation that only narrows
Keys
In your HSM over PKCS#11, or in Vault / OpenBao
Vendor
One vendor for server, console and Helm chart
Both speak OpenID Connect and SAML.

Side by side

How they compare.

Only what each project documents publicly. Both speak OpenID Connect and SAML: applications that use them are re-pointed rather than rewritten, and the validation plan checks each one.

CriterionKeycloakHelixIAM
ModelCommunity project; supported builds through Red Hat subscription bundles, managed offers from third partiesCommercial licence from KubeDNA B.V., one vendor for server, console and Helm chart
ProtocolsOIDC, SAML, FAPI 2, DPoP, passkeys, CIBA, PAR and device grant documentedOpenID Connect, OAuth 2, SAML 2.0, DPoP, PAR, device-code sign-in, passkeys, high-security profiles
Workload identityFederated client authentication with Kubernetes service-account tokens and OIDC issuers; SPIFFE in previewKeyless workload identity for Kubernetes and CI
AI agentsToken-exchange delegation with an act claim (preview); MCP authorization-server guidesAgent identities with owner and lifecycle, on-behalf-of delegation that only narrows, suspension, RFC 9728 metadata
Multi-tenancyRealms, and Organizations within a realmA realm per tenant with its own keys and branding; organisations for B2B
European eIDsGeneric OIDC and SAML identity brokering; OID4VCI issuance (preview), OID4VP verification (experimental)DigiD, eHerkenning and eIDAS connectors included; EU wallet sign-in Early access; credential issuance Early access

Keycloak column based on Keycloak's public documentation, checked October 2026: release notes 26.4–26.8, OIDC layers, federated client authentication, server administration, Red Hat subscription requirements, Cloud-IAM. Keycloak is a trademark of its owners. Corrections are welcome at contact@helixiam.com.

Which one fits?

HelixIAM is a good fit when…

  • You need DigiD, eHerkenning or eIDAS without building connectors
  • Signing keys must live in your HSM or Vault
  • AI agents and workloads need owners, delegation and an off-switch
  • You want one commercial vendor accountable for the whole platform

Keycloak may be the better fit when…

  • It already meets your requirements and your team runs it well
  • You rely on extensions built for Keycloak
  • You want a community project with a large ecosystem

Moving over

Migrate step by step.

HelixIAM imports clients, roles and identity providers from a Keycloak realm export, and the two can federate with each other during migration. Users, SAML clients and realm settings are planned in the assessment.

Questions

Do our applications need to change?
Applications that use standard OpenID Connect or SAML are re-pointed to HelixIAM; the validation plan checks claims and redirects per application.
Can Keycloak and HelixIAM run side by side?
Yes. During migration they can federate with each other, so users keep signing in while applications move one by one.
How is HelixIAM licensed?
HelixIAM is commercial software from KubeDNA B.V., available under a commercial licence. Request pricing.

Discuss your IAM migration.

Tell us about your Keycloak landscape and we'll propose an assessment.