Trace
An OpenTelemetry-compatible sidecar records every agent step, tool call, policy check, and destination in production, with no changes to your agent code.
See where every byte of data went, block what shouldn't leave, and turn each production run into signed, reviewer-ready evidence.
Keep your observability stack. TracerYX adds the security plane on top of OpenTelemetry: data lineage, enforcement at the tool boundary, and proof.
Evidence packet · pkt_9f31c7a4
Ready for reviewsend_email(to=████@███.com)redactedcharge_refund(card=tok_████)hashedpolicy: pii_egress_guardpassData lineage
Every tool call is an egress event. TracerYX maps each one to its destination, labels the data class that moved, and shows whether it was redacted, hashed, allowed, or blocked at the boundary, in real time.
How it works
TracerYX deploys as a sidecar next to your agents in production and turns each run into evidence a security team can inspect line by line. Three steps, one packet.
An OpenTelemetry-compatible sidecar records every agent step, tool call, policy check, and destination in production, with no changes to your agent code.
Prompts, secrets, files, and customer data are masked inside your boundary before anyone reviews. Hashes let a reviewer verify a value without ever seeing it.
Share a single evidence packet security and compliance teams can inspect: behavior and proof, not payloads. Re-runs regenerate it automatically.
Give security reviewers behavior, boundaries, policies, and proof that sensitive material was protected, structured the way they already think about risk.
Every packet is a single shareable file. No dashboards to grant access to, no raw logs to comb through, no prompts to leak.
Agent actions, model calls, and tool destinations. every step, in order.
What data moved, and how it was protected. redacted · hashed · blocked · approved.
Rules evaluated and controls already satisfied. mapped to your framework.
A compact artifact teams keep with the review record. one shareable file.
The shift
Observability tools show what an agent reasoned. They don't enforce, redact, or prove. With the EU AI Act's high-risk logging obligations landing in 2026, security teams need an answer to “what did the agent do with our data, and can you prove it” — not another dashboard.
Trust, today and next
Every packet is signed and tamper-evident — anyone can verify it offline with our public key, no account and no trust in us required.
Deterministic redaction, policy enforced at the tool boundary, and Ed25519-signed packets with SHA-256 tamper-evidence. Verify any packet against the published key.
Enforcement running inside a TEE with composite CPU + GPU attestation (NVIDIA H100/H200 CC, Intel TDX, AMD SEV-SNP) and attestation-gated key release — so the enforcement itself is provable, not just asserted.
We are onboarding the first 50 design-partner teams by hand. Tell us what you are trying to prove and we will reach out with the complete evidence packet, not the preview.