Zero Trust Intelligence (ZTI) · Commercial control plane
ZTIP, the Zero Trust Intelligence Protocol, defines the standard. ZTI Core makes it real.
The operational system that turns protocol into enforcement, in one coherent platform.
Policy engine · Agent registry · Execution receipts · Audit logs
Agents
47
6 pending
Policies
238
12 envs
Recent
hash: a3f9...c7b2
registered agents
47 active
Reframe
ZTIP
ZTIP defines the format, the flow, and the standard. Envelope structure. Hash requirements. Receipt schema. Conformance rules.
What you have: a specification.
ZTI Core
ZTI Core implements and enforces ZTIP. Policy evaluation. Agent identity. Receipt storage. Audit queries. The operational reality of governed AI.
What you get: enforcement.
"ZTIP without ZTI Core is like HTTP without a server. The standard exists. Nothing actually runs."
Without ZTI Core
Implementing ZTIP without an operational platform means rebuilding these capabilities from scratch — for every team, every system, every deployment.
ZTIP envelopes arrive. Nothing evaluates them. Authorization is manual, inconsistent, or non-existent. Policy exists only as documentation.
AI agents operate without identity. You cannot scope their capabilities, bound their actions, or distinguish one agent from another in the audit log.
ZTIP receipts are generated but written to… where? Log files? Databases owned by different teams? There is no single, queryable evidence store.
The "actor" field in the envelope is unverified. Any system can claim any identity. Authorization decisions are made against unverified claims.
Compliance asks "show me all actions taken by ai-agent-7 in Q3." There is no interface. Someone writes a script. The script is different every time.
Policy updates are text file changes reviewed by engineers. No version control, no rollback, no testing, no enforcement at evaluation time.
ZTI Core capabilities
Four core capabilities. One coherent platform. ZTIP-native from the ground up.
01 / Agent Registry
Register agents with defined identities, capability scopes, and operational boundaries. Each agent has a verifiable identity that the policy engine can reference during authorization. No unregistered agent can produce a valid ZTIP receipt.
02 / Policy Engine
Define policies in a structured, auditable format. Policies reference action types, actor identities, target environments, and contextual constraints. The engine evaluates every ZTIP envelope in real time — before execution. Decisions are signed and stored.
03 / Execution Receipts
Every action that passes through ZTI Core produces a ZTIP-conformant execution receipt. Signed by the control plane. Immutable. Queryable. References the original envelope hash, authorization decision, actor identity, and outcome. This is what compliance requires.
04 / Audit Logs
All receipts persist in an append-only, tamper-evident audit store. Query by agent, action type, policy, time range, or outcome. Export for compliance reports. Integrate with your existing SIEM or audit tooling. The evidence is always there.
See it work
The gate at the heart of ZTI Core, replaying the shape of the July 2025 Replit incident: an agent tries to wipe a production database during a code freeze, then reports success. Watch it block the reckless action, refuse the false “done,” and seal a tamper-evident receipt. This enforcement core now ships inside ZTI Core, which is complete and in early access.
Reference gate · narrated walkthrough · sound on
Platform preview
AI Agent
ZTIP
ZTI Core
Execution
Receipt
Actions (30d)
12,769
↑ 14% vs prev.
Policies Active
238
12 environments
Policy Denials
12
0.09% deny rate
Registered Agents
47
6 pending review
Recent Actions
Action Volume (7d)
Public proof · no signup
An agent claimed the work was done. The tests said otherwise. The gate re-ran them, minted a receipt that says failed, and blocked the commit. That same bypass sits caught in public CI right now, merge button dead. No signup, nothing to install.
The plane answering those checks is live. demo.zerotrustintelligence.io is the operator's console, so the login wall you would hit is the product working. Its health endpoint answers anonymously:
$ curl https://demo.zerotrustintelligence.io/v1/health
{"status":"ok"}