What is AtmanID
AtmanID is an AI-native Identity & Access Management (IAM) platform: runtime enforcement for AI agents, with humans and agents governed on one identity model and one tamper-evident audit trail. It is for organizations that need to govern who — and what — has access to which applications, data, and capabilities. The “and what” is load-bearing: AtmanID treats AI agents and service accounts as first-class identities, not afterthoughts retrofitted onto a human-centric data model.
The shorter version: AtmanID covers the core IGA functions — provisioning, access certification, segregation of duties, audit, joiner/mover/leaver lifecycle — that legacy enterprise IGA platforms (SailPoint, Saviynt, Okta IGA, Microsoft Entra ID Governance) ship as their feature surface, but built from the ground up around the assumption that an AI assistant should be the primary interface, not a chatbot bolted onto a 2010-era admin UI. Connector breadth is intentionally narrower in v1 — cloud-first identity providers and IGA-shaped SaaS, not the long tail of legacy on-prem systems.
Three things that make AtmanID different
1. Iris is the primary interface, not a feature. Every other IAM tool has a chatbot somewhere. In AtmanID, the chat IS the product surface for most operator workflows. Ask “how many users haven’t logged in for 90 days” and Iris answers with a count + breakdown. Ask “revoke Sarah’s PAM access to the production database” and Iris proposes the action with a confirmation gate. Ask a question no pre-built tool covers — “which users with admin entitlements haven’t logged in for 90 days, by department?” — and Iris builds a structured query over curated, tenant-scoped read-only views; the server checks it and writes the SQL, so the model never runs SQL of its own. Iris is not a search box that returns documentation — it’s the operational interface to your IAM data, with a natural-language router that knows when to use a pre-built aggregation tool, when to build a query, and when to refuse a question outside its scope.
2. The audit chain is tamper-evident by construction, not by policy. Every action AtmanID takes — every access grant, every role assignment, every certification decision, every Iris-mediated mutation — writes to an audit log row with a sequence_num (monotonic per tenant), a previous_hash, and an integrity_hash (SHA-256 over the full event including previous_hash). The chain head is also signed every few minutes with a key the database never holds. The most recent entries are re-verified every night and the whole history every week, and compliance, audit and admin roles can check the chain on demand — from the Audit Log page, or by asking Iris. Most IAM tools have audit logs. AtmanID’s audit log can prove it hasn’t been edited.
3. AI agents and non-human identities are first-class. The data model has explicit support for: humans (employees, contractors, partners), service accounts (machine-to-machine), and AI agents (autonomous capabilities). Each has its own lifecycle, its own credential rotation policy, its own capability scoping, its own delegation model. The agent-specific surface includes things SailPoint doesn’t have because AI agents weren’t a category when SailPoint was designed: trust chains, capability catalogs, just-in-time elevation with HITL gates, anomaly detection on agent behavior, scope attenuation for delegated agent access. None of this is bolted-on; it’s how the data model thinks about identity from row 1.
And for agents, AtmanID does not stop at governance on paper. Agent tokens are scoped to specific MCP servers and tools and can be DPoP-bound to the agent’s key; every agent → MCP tool call passes through the AtmanID gateway, which checks scope, intent policy and rate limits, can hold a call for human approval, and records the decision. New enforcement starts in shadow mode and is promoted to enforce when you are ready.
Who AtmanID is for
The honest answer: mid-market to enterprise security teams who currently use a legacy IAM tool (or no IAM tool) and are feeling pain from one of:
- Operator velocity — the security team can’t keep up with access requests, certifications, joiner-mover-leaver events, audit responses. The current tool requires too many clicks. Iris collapses most operator workflows from “navigate to the right page → run the right report → export → analyze” to “ask Iris.”
- AI agent governance — the org is deploying AI agents (Slack bots, Cursor sidebars, custom internal LLM tools, AutoGPT-style automations) and the security team has no central registry of what those agents can do, who authorized them, what credentials they hold, or how to revoke them. AtmanID’s NHI + agent identity surface is purpose-built for this.
- Audit-readiness friction — SOC2 / ISO 27001 / SOX evidence collection currently takes weeks of manual work. AtmanID’s tamper-evident chain + structured event taxonomy makes evidence collection a SQL query, not a project.
- Cost vs incumbent tools — SailPoint and Saviynt are priced for F500 enterprise IT budgets. AtmanID is built for organizations that want F500-grade IAM capability without F500-grade pricing or implementation timelines.
Who AtmanID is NOT for (yet)
Worth being honest about the boundary:
- Single-app shops with <50 users — Google Workspace’s built-in admin tools are sufficient. The IAM problem only becomes painful at scale (multiple apps × many users × complex access patterns × compliance requirements).
- Pure SSO/MFA-only buyers — for people, AtmanID is governance + lifecycle + audit, not authentication. Okta and Auth0 own the SSO/MFA layer. AtmanID lives downstream of authentication, governing what authenticated users can do. (The runtime enforcement it does provide is for AI agents’ tool calls, not human sign-in.)
- Organizations that mandate on-premise deployment — AtmanID is cloud-native. Hybrid/air-gapped deployment isn’t on the roadmap.
- Organizations that fear AI in their security stack — Iris is the primary interface; if the security team needs every action mediated through a deterministic UI with no LLM in the loop, AtmanID isn’t the right fit. The alternative tools they probably want are SailPoint or Saviynt.
The core promise in one sentence
AtmanID lets a small security team operate the IAM program of a much larger organization — by collapsing operator workflows into natural-language interactions, by making compliance evidence a query instead of a project, and by treating the next decade’s identity types (AI agents, NHIs, machine identities) as first-class instead of legacy retrofits.
Where to go next
- For the mental model that makes the product make sense: How AtmanID thinks about IAM
- For who uses what surface: Personas
- For the architecture deep-dive: Architecture overview (or the security-review-grade version at Architecture & Security)
- For the differentiator narrative: Iris explained
- For the API and SDK: Reference
© AtmanID · Privacy