Skip to content
TrustList
News

Omada acquires EmpowerID; EmpowerID customers should ask what happens to their product

Editorial

By TrustList Editorial

Danish identity-governance vendor Omada has bought EmpowerID for its runtime controls over AI agents. Terms were not disclosed, and neither company has said what happens to EmpowerID's existing identity suite or its support.

About Omada acquires EmpowerID; EmpowerID customers should ask what happens to their product

Omada acquires EmpowerID; EmpowerID customers should ask what happens to their product

24 September 2026 — Omada, the Copenhagen-based identity governance and administration (IGA) vendor, announced on 24 September 2026 that it has acquired EmpowerID, a US identity vendor. Omada presents the deal as buying EmpowerID's "runtime agent governance": controls that decide, at the moment an AI agent requests access, whether it may proceed, and can stop it when it steps outside its permissions. Terms were not disclosed.

What was announced

  • EmpowerID's chief executive and co-founder, Patrick Parker, joins Omada as chief innovation officer, to lead development and the integration of EmpowerID's agent governance technology into Omada's platform.
  • Omada says the combined platform will manage human users, applications, workloads and AI agents through the same lifecycle, access and certification services.
  • The deal follows Omada's own Agent Governance product, announced in June 2026.

The announcement does not say whether EmpowerID's existing products will continue to be sold and supported, for how long, or under what name.

Why that matters

EmpowerID is not only an agent-governance tool. It also sells a full identity governance suite, which puts it in the same market as Omada. The analyst firm KuppingerCole, writing on 25 September, describes the overlap: Omada approaches IGA as a standard, off-the-shelf product with a set process framework, while EmpowerID takes a developer-centred approach built on heavy customisation. KuppingerCole's analyst warns that if EmpowerID ends up as a separate product line alongside Omada Identity, most customers would see little benefit, and advises EmpowerID customers to confirm support commitments and the future of the product they run.

Where one IGA product absorbs another, customers of the acquired product usually face a migration at some point. With identity governance, that means re-doing connectors, access reviews and workflows, which is slow and expensive.

Who is affected

Organisations running EmpowerID for identity governance, access management or privileged access, and the integrators that deployed it. Omada customers are less directly affected but should expect agent-governance features to be sold to them as part of the combined roadmap.

What to do

  • If you run EmpowerID, ask Omada in writing whether your product will continue, how long it will be supported, and whether a migration to Omada Identity is planned and on what commercial terms.
  • Check which company your contract, support agreement and data processing agreement now name, and ask for the current sub-processor list.
  • Where your deployment relies on custom workflows or connectors, ask how they will be carried forward, as KuppingerCole suggests.
  • Note your renewal date; a change of owner is a reasonable point to ask for a price hold and a roadmap commitment.
  • If you are evaluating either vendor for AI agent governance, ask for a demonstration on the combined product, not the separate pieces.

Sources