HelixIAM by KubeDNA

Early access/now onboarding launch partners

Identity infrastructure you control — with European eID connectors and your own keys.

Self-hosted IAM from KubeDNA, a Dutch vendor. DigiD, eHerkenning and eIDAS connectors you configure in the console, for use with your own agreements, plus SSO and MFA, with signing keys in your HSM or Vault. Workloads and AI agents get their own identity on the same platform.

Commercial licence · KubeDNA B.V., the Netherlands

Reference architectureRuns in your cluster
HelixIAM reference architecture People, workloads and AI agents authenticate to HelixIAM, which runs inside your own infrastructure on Kubernetes with PostgreSQL. HelixIAM brokers European eIDs (DigiD, eHerkenning, eIDAS, and the EU Digital Identity Wallet in early access), keeps signing keys in your HSM over PKCS#11 or in Vault or OpenBao Transit, and issues tokens to applications, APIs and MCP tool servers. EUROPEAN eIDs · CONNECTORS INCLUDED DigiD eHerkenning eIDAS EUDI Wallet · early access brokered sign-in HELIXIAM IN YOUR KUBERNETES CLUSTER HelixIAM realms · policy · tokens · sessions · audit OpenID Connect · OAuth 2 SAML 2.0 Token exchange · RFC 8693 SCIM 2.0 Passkeys · MFA DPoP · PAR PostgreSQL · Redis (optional) · Helm chart, HA no message broker · no telemetry signing keys Key custody HSM · PKCS#11 Vault / OpenBao Transit Peopleemployees · customers · citizenspasskeys · MFA · SSO WorkloadsKubernetes pods · CI pipelineskeyless JWT exchange AI agentsassistants · MCP clientson-behalf-of · narrowed scope Applicationsweb, SaaS and existing appsOIDC · SAML 2.0 APIsresource serversaudience-restricted tokens MCP tool serversAI tool endpointsRFC 9728 tokens HelixIAM reference architecture People, workloads and AI agents authenticate to HelixIAM, which runs inside your own infrastructure on Kubernetes with PostgreSQL. HelixIAM brokers European eIDs (DigiD, eHerkenning, eIDAS, and the EU Digital Identity Wallet in early access), keeps signing keys in your HSM over PKCS#11 or in Vault or OpenBao Transit, and issues tokens to applications, APIs and MCP tool servers. EUROPEAN eIDs · CONNECTORS DigiD eHerkenning eIDAS EUDI Wallet · early access PeoplepasskeysMFA · SSO WorkloadsK8s · CIkeyless AI agentson-behalf-ofnarrowed IN YOUR CLUSTER HelixIAM realms · tokens · audit OpenID Connect · OAuth 2 SAML 2.0 Token exchange · RFC 8693 SCIM 2.0 Passkeys · MFA DPoP · PAR Key custody HSM PKCS#11 Vault / OpenBao Transit tokens AppsOIDC · SAML APIsaudience-restricted MCP toolsRFC 9728
Reference architecture. HelixIAM runs in your Kubernetes cluster with PostgreSQL. Signing keys stay in your HSM or in Vault / OpenBao. European eID connectors are included; you connect DigiD or eHerkenning under your own agreement. Your applications, APIs and agents can run in the same infrastructure.
  • Open standardsOIDC · SAML · SCIM · FIDO2
  • Self-hostedno telemetry
  • Your keysHSM or Vault / OpenBao
  • Signed releasescosign · SBOM
  • Backed by KubeDNAthe Netherlands

European sovereignty, backed by KubeDNA

Your infrastructure. Your keys. European eID connectors included.

HelixIAM runs on your own infrastructure: you decide where data lives, and there is no telemetry. KubeDNA offers deployment and operations support for HelixIAM on your own or a European cloud, with the scope set per contract.

  • Per-tenant signing keys with safe rotation; bring your own CA-signed keys.
  • Keep signing keys in your HSM over PKCS#11, or in HashiCorp Vault or OpenBao Transit.
  • A dedicated HSM partition or Vault credential per tenant, and online key-encryption-key rotation.
  • DigiD, eHerkenning and eIDAS connectors included, for use with your own agreements.
  • Sign in with the EU Digital Identity Wallet, tested with the EU reference wallet. Early access

The identity challenge

Your systems now act for people, not just with them.

A single request can pass through an employee, an AI agent acting for them, and a chain of workloads. People need SSO, MFA and federation across every app. Agents need an owner, a principal and limits. Workloads need identity without long-lived secrets in pipelines and pods.

One request, three kinds of identityA person signs in, an AI agent acts on their behalf, a workload calls an API. Each hop carries its own token: a session for the person, a delegated token naming both user and agent, a short-lived workload token without a stored secret, and an audience-restricted token at the API. Person signs in with a passkey AI agent acts on the person's behalf Workload Kubernetes pod or CI job API resource server session · MFAsub=user · act=agentno stored secretaud=api One request, three kinds of identityA person signs in, an AI agent acts on their behalf, a workload calls an API. Each hop carries its own token: a session for the person, a delegated token naming both user and agent, a short-lived workload token without a stored secret, and an audience-restricted token at the API. Person signs in with a passkey session · MFA AI agent acts on the person's behalf sub=user · act=agent Workload Kubernetes pod or CI job no stored secret API resource server aud=api
Every hop needs an identity you can trace, limit and revoke.

The solution

One platform for every identity.

Two propositions on one identity core: HelixIAM Sovereign for enterprise IAM, HelixIAM AI Identity for agents and workloads. One product, one licence.

Human identity & enterprise IAM

A standards-based OpenID Connect and OAuth 2 provider and a SAML 2.0 identity provider, with passkeys, MFA, LDAP/AD and SCIM.

  • Single sign-on and single logout across OIDC and SAML apps
  • Multi-tenant realms with their own users, keys and branding
  • Broker sign-in from other OIDC, SAML and social providers
Explore HelixIAM Sovereign

Non-human & AI-agent security

Every agent gets its own identity with an owner and a lifecycle. When it acts for a user, the token carries both, and its authority only ever narrows — on your own infrastructure, with tokens signed by keys you hold, from a Dutch vendor.

  • Standard OAuth token exchange (RFC 8693)
  • Suspend an agent and it gets no new tokens
  • Ready for MCP: protected-resource metadata (RFC 9728)
Explore HelixIAM AI Identity

Workload identity & cloud-native security

Keyless workload identity for Kubernetes and CI: no long-lived secrets.

  • Sender-constrained tokens with DPoP
  • Audience-restricted tokens with resource indicators
  • Prometheus metrics and alert rules out of the box
Explore the developer documentation

For sovereign clouds and integrators

Offer European IAM as a service, on your own cloud.

Run HelixIAM as a multi-tenant service on your platform, with KubeDNA behind you for identity and Kubernetes support, scope set per agreement.

  • Each customer gets its own realm with its own users, keys, flows and branding.
  • A dedicated key store per tenant.
  • Provision tenants with the admin REST API, and manage applications with Terraform.

Enterprise capability overview

The enterprise IAM you expect, with standards to match.

Everything below is in the product today; early-access items are marked.

Sign-in

  • Passkeys (WebAuthn/FIDO2)
  • Authenticator-app MFA, recovery codes
  • Optional magic-link sign-in
  • Adaptive step-up authentication
  • Argon2id, lockout and breached-password checks
  • Push approval with number matching Early access

Federation & SSO

  • OpenID Connect and OAuth 2 provider
  • SAML 2.0 identity provider
  • Single sign-on and single logout
  • LDAP and Active Directory
  • OIDC, SAML and social brokering
  • SCIM 2.0, inbound and outbound

Tokens & APIs

  • DPoP sender-constrained tokens
  • Pushed authorization requests (PAR)
  • Device-code sign-in
  • Resource indicators
  • Token exchange (RFC 8693)
  • High-security profiles: mTLS-bound tokens, PS256
  • Dynamic client registration

Tenancy & admin

  • Multi-tenant realms
  • Organisations for B2B
  • Fine-grained admin permissions
  • Documented admin REST API
  • Terraform for applications, roles and wallet connections

Security & audit

  • Audit events as JSON lines
  • Per-tenant routing through your log collector
  • GDPR data export and erasure per user
  • Per-tenant signing keys
  • HSM and Vault / OpenBao key custody

European identity

  • DigiD, eHerkenning and eIDAS connectors
  • EU Digital Identity Wallet sign-in Early access
  • Credential issuance to EU wallets Early access
  • EU trusted lists as trust anchors Early access

One console

Configure eID, keys and agents in one console.

The HelixIAM admin console covers eID connectors, realms, applications, users, roles, sessions, keys and audit settings — and the agent inventory, with owners, status and an owner review that flags agents whose owner has left.

HelixIAM admin console, AI agents screen: agent counts by status, an owner review flagging an agent whose owner has left, and a table of agents with owner, status, authentication method and bound application. HelixIAM admin console, AI agents screen: agent counts by status, an owner review flagging an agent whose owner has left, and a table of agents with owner, status, authentication method and bound application.
HelixIAM console · AI agentsIllustrative data

Migration

Moving from Keycloak or a legacy IdP?

Your applications speak OpenID Connect and SAML, and so does HelixIAM. Import clients, roles and identity providers from a Keycloak realm export, then validate and cut over application by application.

  • Migration assessment of your realms, clients and flows.
  • A validation plan agreed before any cut-over.
  • Phased cut-over with both identity providers running.

Early access/now onboarding launch partners

See HelixIAM on your own stack.

Start with a technical session on a running system — European eID, SSO and your deployment, workload identity and AI agents — then a paid pilot on your own use case, working directly with the engineers who build HelixIAM.