Frequently asked questions

Every identity in your environment and the relationships behind it — your own people, third-party organizations and the staff they bring with them, non-human identities such as service accounts, workload identities and API credentials, and AI agents. Each source keeps its native shape, and new entity types resolve at query time.

Existing tools govern accounts inside the systems that own them. The gap is between those systems: every relationship type is managed in its own system, by its own owner, on its own cycle — separate sources of truth that never reconcile. idGenius sits across them and governs the relationships, rather than replacing what sits underneath.

No. idGenius reads from the sources you already run and leaves them in place. There is no ETL program, no migration, and no integration spend each time a new entity type appears.

Service accounts, workload identities, API credentials and AI agents — anything that authenticates and acts without a person driving it. idGenius discovers, governs, secures, observes and audits all of them in one place.

As enterprise identities with an owner, a purpose, an authority, tool boundaries, a delegation chain and an expiry — not as traffic. That is what makes it possible to see an agent whose sub-agent chain has widened past its grant, or one still running and still billing after the project that justified it has closed.

The same cycle runs every time: discover, learn, govern, enforce, observe, audit. A business decision changes a relationship, the long-tail impact is traced across everything that relationship touched, and the result lands as reduced risk, reduced CAPEX and reduced OPEX.