Public evidence onlyLast checked 16 October 2026 with AI-assisted research. Editor: Akshay Dubey.MethodologyCorrections log

In short: Aembit (independent; venture-backed, Series A; founded 2021) and Defakto (independent; venture-backed, Series B; founded 2022) both publish documentation for 11 of the 21 NHI capabilities we track. The public evidence differs on 6: evidence for Aembit only on attribution to humans and agent governance; evidence for Defakto only on ownership assignment, access analysis, service accounts and monitoring and detection. Records checked 16 October 2026. This is a reading of what each company has published, not a score or a recommendation.

This page puts two company records side by side. It shows what public evidence establishes for each, using the same labels as the profiles. It gives no score, no ranking and no recommendation. Read the full records for sources: Aembit and Defakto (formerly SPIRL).

Company facts

Scroll sideways to see all columns.

FactAembitDefakto
Record nameAembitDefakto (formerly SPIRL)
OwnershipIndependentIndependent
StageVenture-backed, Series AVenture-backed, Series B
Founded2021 (Verified)2022 (Publicly disclosed)
HeadquartersSilver Spring, Maryland, USA (Verified)Palo Alto, California, United States (Verified)
Total fundingNearly $45M (company statement, September 2024) (Verified)About $50M (Publicly disclosed)
Categories in our directoryWorkload identity, Workload IAM, AI agent accessWorkload identity, Non-human IAM
Record verified2026-10-162026-10-16

Why these two are compared

Each record lists the other as a direct competitor in our analysis of product scope.

  • The Aembit record describes Defakto as: workload identity and secretless access.
  • The Defakto record describes Aembit as: workload identity and secretless access for workloads and agents.

Capability evidence, side by side

Documented by vendor means the company's own documentation describes the capability. It is not independent verification and says nothing about depth. Not publicly verified means we did not find public documentation. It does not mean the product lacks the capability.

Scroll sideways to see all columns.

CapabilityAembitDefakto
NHI discovery Documented by vendor Documented by vendor
NHI inventory Documented by vendor Documented by vendor
Ownership assignment Not publicly verified Documented by vendor
Attribution to humans Documented by vendor Not publicly verified
Access analysis Not publicly verified Documented by vendor
Authorization policy Documented by vendor Documented by vendor
Least privilege Documented by vendor Documented by vendor
Lifecycle management Documented by vendor Documented by vendor
Credential rotation Documented by vendor Documented by vendor
Secrets management Not publicly verified Not publicly verified
Certificate management Not publicly verified Not publicly verified
Service accounts Not publicly verified Documented by vendor
API keys Documented by vendor Documented by vendor
OAuth apps and tokens Not publicly verified Not publicly verified
Workload identity Documented by vendor Documented by vendor
Cloud identity Documented by vendor Documented by vendor
AI agents Documented by vendor Documented by vendor
Agent governance Documented by vendor Not publicly verified
Monitoring and detection Not publicly verified Documented by vendor
Remediation Not publicly verified Not publicly verified
Audit evidence Documented by vendor Documented by vendor

Where the public evidence differs

  • Public evidence found for Aembit and not for Defakto: Attribution to humans, Agent governance.
  • Public evidence found for Defakto and not for Aembit: Ownership assignment, Access analysis, Service accounts, Monitoring and detection.
  • Public evidence found for both: NHI discovery, NHI inventory, Authorization policy, Least privilege, Lifecycle management, Credential rotation, API keys, Workload identity, Cloud identity, AI agents, Audit evidence.
  • Not established for either from public sources: Secrets management, Certificate management, OAuth apps and tokens, Remediation.

A difference in this list is a difference in what each company has published, as read by us on the verification dates above. It is not a count of features and should not be read as a score. Confirm any capability that matters to you with the vendor and in a proof of concept.

Recent developments

Aembit

  • 5 October 2026: Access controls for Meta Muse announced. A company blog post says the MCP Identity Gateway and MCP Authorization Server can now issue short-lived, scoped credentials to the Muse agent under policy. [source]
  • 22 September 2026: Support for Okta Cross App Access launched. Aembit said IAM for Agentic AI now supports Cross App Access, an open protocol introduced by Okta. [source]
  • 28 July 2026: Snowflake integration for third-party AI agents. Aembit announced an integration with Snowflake aimed at controlling how AI agents reach data in Snowflake. Snowflake's Chief Security and Trust Officer was quoted in the release. [source]

Defakto

  • 1 May 2026: Defakto reports six industry awards. The company listed awards from Cyber Defense Magazine, the Cybersecurity Excellence Awards and the Globee Awards. These are award programmes, not technical evaluations. [source]
  • 4 February 2026: CTO sets out the company's approach to AI agent identity. Eli Nesterov argued that agents should authenticate with short-lived, policy-bound identities, not API keys. [source]
  • 13 November 2025: Company announces a Gartner Cool Vendor listing. Defakto said it was named in Gartner's Cool Vendors in Identity-First Security report dated 24 October 2025. [source]

Positioning

Aembit

What the company says: Aembit describes itself as the identity and access management platform for agentic AI and workloads, enforcing access based on identity, context and centrally managed policies. [source]

Our analysis: Aembit addresses access at runtime more than inventory. It replaces static credentials held by workloads with identity attestation, policy checks and credentials supplied at the moment of access. It extends the same model to AI agents calling tools over MCP.

Defakto

What the company says: Defakto describes itself as a complete Non-Human IAM platform that replaces static secrets and service accounts with short-lived, verifiable identities for workloads, pipelines and AI agents. [source]

Our analysis: Defakto addresses the standing-credential problem at source. Its documented product issues a cryptographic identity to each workload at runtime, so there is no stored key to leak, rotate or inventory. Its product page now also lists discovery, ownership and least-privilege modules for identities that already exist.

Common questions

What is the difference between Aembit and Defakto?

Aembit addresses access at runtime more than inventory. It replaces static credentials held by workloads with identity attestation, policy checks and credentials supplied at the moment of access. It extends the same model to AI agents calling tools over MCP. Defakto addresses the standing-credential problem at source. Its documented product issues a cryptographic identity to each workload at runtime, so there is no stored key to leak, rotate or inventory. Its product page now also lists discovery, ownership and least-privilege modules for identities that already exist. In published documentation, public evidence was found for Aembit and not for Defakto on attribution to humans and agent governance; for Defakto and not for Aembit on ownership assignment, access analysis, service accounts and monitoring and detection. That is a difference in what each company has published, not a feature count or a ranking.

Who owns Aembit and Defakto?

Aembit: Independent. Defakto: Independent. Ownership is taken from company announcements and filings and is dated on each record.

Do Aembit and Defakto support AI agents?

AI agents: Aembit, documented by vendor; Defakto, documented by vendor. Agent governance: Aembit, documented by vendor; Defakto, not publicly verified. Not publicly verified means we did not find public documentation; it does not mean the product lacks the capability.

Which is better, Aembit or Defakto?

We do not rank or recommend either company, and no company pays for coverage. The better fit depends on which identity types you need covered, where your credentials live, and what evidence your auditors expect. Put the questions on this page to both vendors and confirm the capabilities that matter in a proof of concept.

What are the alternatives to Aembit and Defakto?

Other companies in the same categories of our directory, listed alphabetically and not ranked: Andromeda Security, Anetac (part of Quest Software), Astrix Security (part of Cisco), Clutch Security, Corsha, Cremit, Entro Security (part of SailPoint) and Fabrix Security, and 16 more in the company directory. Each has a sourced record on this site.

Questions to put to both

  • Which identity types are discovered without an agent or manual import, and which need configuration?
  • How is a named human owner assigned to each non-human identity, and what happens when that person leaves?
  • What evidence can be exported for an audit, and in what format?
  • Which capabilities are generally available today, and which are in preview?
  • Who owns the company today, and what has been said about the product roadmap since any change of ownership?

See the methodology for how records are researched, and the list of all comparisons.

Monthly change log

Know when the NHI landscape changes.

One email a month from this reference: new deals, standards status changes and corrections. No sponsored content. Unsubscribe from any email.

We first email you a link to confirm. Privacy policy.