Where the sovereign agent already lives.

Anonymized by policy

Why our customer page doesn't name names.

Most companies that buy AZMX are buying it because they cannot, by procurement policy, be on a public AI-vendor logo strip. Customer attribution is opt-in. The pattern of who deploys AZMX matters more than the name.

Industry archetypes

Who deploys AZMX, and what trust shape they chose.

Why they switched

Five reasons we hear in procurement reviews.

• The trust property is structural, not contractualAZMX is not on the network path. The vendor literally cannot read prompts, code, or audit logs. CISOs no longer need to negotiate a contract for a property the architecture already enforces.
• The audit log was freeMost coding AI tools sell auditing as an Enterprise upgrade. AZMX bakes a hash-chained, tamper-evident audit log into Free. Pro+ adds signed SIEM export — that's the upgrade.
• BYOK economicsA 50-engineer team's annual AI spend dropped ~75% switching from per-seat coding subscriptions to AZMX Teams + a shared org-level OpenAI account. Same productivity. Different shape of bill.
• Air-gapped operation is real, not theoreticalFederal and defense buyers want air-gap. AZMX gives them: local-only AI lock, customer-rooted license issuer, manual update channel, verifiable at the firewall.
• The trust floor doesn't change between Free and EnterprisePer-call approval, secret-path screen, hash-chained log are the same on Day-1 Free and Day-1000 Enterprise. The wrapper changes; the property doesn't.

Selected reference cases

Anonymized, but real.