UC Launch Spring 2026 · Enterprise Preview

Audit-Grade Evidence for AI Agents — In Your Cluster

Your FFIEC, SOC 2, HIPAA, or FedRAMP auditor will ask what your AI agents did, who authorized it, and where the evidence lives. Hexr puts signed, control-mapped evidence rows into your own Postgres — per process, per agent call, any framework. Nothing leaves your VPC.

Any FrameworkAny Agentic PatternSub-Agent SPIFFE IdentityCross-Cloud Trust PolicyA2A ProtocolSOC 2 · HIPAA · FedRAMP ReadyEvidence Stays in Your VPC

Book an Auditor Demo

Per-Process

SPIFFE Identity

Customer-Owned

Evidence in Your Postgres

Auditor-Mapped

SOC 2 · HIPAA · IL5 Controls

Like Iru for audit maps · Like CrowdStrike for per-process attestation · Like Datadog for OTel spans. Built for the auditor, not the SRE.

Built on Open Standards

Live Demos — Real Clusters, Real Evidence

EKS (Acme) and AKS (Globex) are running right now. Pick a scenario.

A CrewAI agent attempts a tool call. OPA fails it closed. Hexr writes a signed evidence row tagged SOC 2 CC6.1 and NIST-SSDF PW.4 into the customer's own Postgres on EKS. The auditor sees the deny, the policy version, and the SPIFFE identity of the process that triggered it.

Built for the Auditor and the Engineer

FFIEC, SOC 2, HIPAA, FedRAMP IL5 — every capability maps to a control your auditor recognises. Identity flows into policy, policy fires OPA, OPA writes a signed evidence row, evidence rows produce the PDF.

Per-Process Identity

Unique SPIFFE IDs per process inside containers, not just pods. Pure userspace, no kernel modifications.

CLI Pipeline

Source-to-deployment in three commands. Auto-generates container images, K8s configs, identity mappings from your code.

Credential Cache

Multi-level cache: in-process (<1ms), distributed cluster (1-3ms), cloud exchange. Proactive background refresh. Per-process isolation. Zero-latency hexr_tool() calls.

Cross-Cloud Trust Policy

SPIFFE identities federate to AWS IAM, GCP Workload Identity, and Azure AD without static credentials. Per-tenant Terraform modules and a `hexr trust-policy` CLI provision the cloud-side trust in one command.

Policy Engine

OPA Rego policies at every service boundary. Fail-closed enforcement. GitOps-driven. Full decision audit logging.

A2A Protocol

Purpose-built agent-to-agent communication. Durable task state, cooperative cancellation, real-time streaming, all over mTLS. Our own protocol, not a wrapper.

Vault

SPIFFE-native secrets. Zero API keys. AES-256-GCM encryption. Tenant + agent + path isolation via OPA.

LLM Observability

Complements existing LLM observability tools by adding the identity layer they lack. Per-process SPIFFE-attributed traces, per-agent cost tracking, and full OpenTelemetry spans any platform can consume.

Framework Detection

AST-based engine detects agents across any Python framework: CrewAI, LangChain, Strands, or custom. Zero configuration.

Gateway

Converts OpenAPI v3 specs to MCP tools automatically. SPIFFE-authenticated tool invocations with semantic search.

Hybrid + Air-Gapped

One source-available SDK (HSAL v1) drops into any framework on your own Kubernetes (EKS, GKE Standard, AKS, or on-prem). Cloud-connected (Hexr CP as SPIRE UpstreamAuthority) or fully offline (`cloud.enabled=false`, no phone home, FIPS-140 builds) for FedRAMP High, IL5, and CMMC L3. Same evidence schema, same auditor PDF in both.

Topology Analysis

AST-based pattern detection at build time. Orchestrated, hierarchical, peer-to-peer, or mixed topologies identified automatically from source.

Audit-Ready Policies

Pre-built OPA/Rego templates mapped to SOC 2 Type II, NIST 800-53, HIPAA §164.312, ISO 27001, and EU AI Act. Deploy entire control frameworks in one Helm value.

One SDK. Two Routes.

The Hexr SDK is the universal entry point — source-available under HSAL v1, the same decorators on every framework and every runtime. Then pick how your data plane reaches the Hexr Control Plane: cloud-connected (Hybrid) or fully offline (Air-Gapped).

Hybrid

Cloud-connected — Team, Enterprise (Mode A Hexr-managed root or Mode B BYO Vault PKI)

Default route. The Hexr SDK in your agent code plus a Helm chart on your own Kubernetes (EKS, GKE, AKS, or on-prem) — nested SPIRE Server, hostPID DaemonSet for sub-process attestation, gateway, evidence-api, a2a-sidecar, llm-guard. The Hexr Control Plane mints licenses, distributes trust bundles, and acts as SPIRE UpstreamAuthority. Evidence, prompts, and PHI/PII never leave your data plane — only signed trust-bundle exchange crosses the boundary, and the data plane always initiates.

The Honest Comparison

Against the two most distribution-rich agent-governance platforms. Hexr is not a replacement for AgentCore or Agent 365 — it's the per-process evidence layer regulated buyers need that neither hyperscaler can ship from their own cloud.

Dimension	AWS AgentCore	MS Agent 365	Hexr
Runs on any K8s (EKS / GKE / AKS / on-prem)	AWS only	Microsoft cloud only
Air-gapped deploy (FedRAMP High / IL5)
Per-process host attestation (SPIFFE + hostPID)	Pod-level only	Device / endpoint	Per process
Catches forked / unattested binary
Sub-agent SPIFFE identity
Evidence stays in customer VPC	Sent to AWS	Sent to Microsoft
Auditor-mapped (SOC 2 / HIPAA / NIST / OWASP ASI)	Generic CloudTrail	Generic admin logs
BYO Root CA (Vault PKI)
Framework-agnostic instrumentation	SDK contract	Per-vendor SDC integration	Below the framework
A2A mTLS between agents
Open standards (SPIFFE, OPA, OTel)	Proprietary	Proprietary

AgentCore on EKS, ADK on GKE, or Copilot Studio on Microsoft 365? Keep them. Hexr installs in the same cluster (or as a customer-hosted evidence-api alongside a managed runtime) and produces the auditor-mapped, per-process evidence trail none of them can.