Home-grown
One Identity Manager
Exclusively through its REST API, so the same connector covers both on-premises and SaaS deployments. Nothing is read from the database directly.
Get One Identity datasheet →AI layer for SailPoint, One Identity, Entra ID and more
Connected to your data. Present wherever you work.
Two kinds of integrations: connectors that read the identity data you already have, and channels that bring IAMONES to your people.
-
Connectors for the IGA you already own.
Out of the box and bidirectional, for SailPoint, One Identity, Entra ID and Agent 365, Okta, OpenText and Oracle, plus the Universal Connector for home-grown apps. Your system of record stays where it is.
-
One graph, every source.
Data and change events flow through the Identity Gateway into the Temporal Identity Graph, with a complete timeline, where the Identity Brain reasons over them.
-
Channels for your people.
A chat in Microsoft Teams, a tool for your AI assistants through MCP, a component inside your portal, the REST API, or the IAMONES app.
Your data
Your IGA stays. It just starts talking.
Out-of-the-box connectors for traditional IAM vendors. Nothing to migrate, and every integrated platform keeps a complete event timeline.
SailPoint
Both IdentityIQ and Identity Security Cloud, using two deliberately different models, landing in the same Temporal Identity Graph.
Get SailPoint datasheet →
Microsoft Agent 365 and Entra ID
Through the Microsoft Graph API. The connector captures both types of Entra agentic identities alongside human users, plus their consent mapping.
IAMONES for Microsoft →
Okta
Entirely through its management REST API, using a dedicated service credential.
Get Okta datasheet →
OpenText (NetIQ) Identity Manager
Reading the Identity Vault directly over LDAP.
Get OpenText datasheet →
Oracle Identity Governance
Through its REST API only, with no direct reads from the OIG database.
Get OIG datasheet →IAMONES Universal Connector
Everything else. Home-grown included.
Build your own integration for home-grown IAM applications. Publish events to the IAMONES ingestion queue and get data and change events on the same timeline.
Wherever you work
Not another tool. A conversation where your people are.
The same Identity Consigliere, with the same answers and the same controls, in four more places besides the IAMONES app.
Microsoft Teams
A chat, where work already happens.
Requests, approvals and questions answered in Teams, without opening another tool.
MCP
An identity expert for your AI assistants.
Any assistant or agent that speaks the Model Context Protocol can ask IAMONES about identities, access and risk.
Web component
Inside the portal you already have.
Drop the IAMONES web component into your IGA portal or intranet, and the conversation sits next to the page.
API
Everything, from your own code.
A REST API, so your workflows, ticketing and reports can use the same answers.