Primary Function
Traditional Guardrails (Post-Mortem Logs)
Traffic Routing & Rate Limiting
Kovera Runtime Firewall
Inline Blocking & Human Intervention
Intercept · Decide · Prove
AI agents can move money, read database tables, and modify critical systems. Kovera sits between your agents and your tools—automatically blocking high-risk actions, routing anomalies to human oversight, and issuing tamper-proof compliance receipts your auditors can verify instantly.
[ Categorized by Enterprise Auditors as the Agent Protocol of Record — APoR ]
Why APoR?
A protocol layer for agentic governance—not another monitoring add-on.
Guardrails score text; APoR governs the execution path—including tool calls, bridge traffic, and delegation hops.
Every decision anchors to the Kovera Ledger (Merkle-secured activity ledger); proof remains independent of production logs.
Forensic-ready packs (EU AI Act, ISO 42001) + Open Evidence API for third-party, independent verification.
Differentiation
AI gateways are a prerequisite for delivery. They handle routing, authentication, and wire-level limits. Kovera adds runtime interception and tamper-proof activity receipts. You can verify those receipts without trusting our UI.
{
"lvl": "INFO",
"_trace": "chunked…",
"ts": "2026-05-13T18:42:01.883Z",
"svc": "ai-gateway",
"rid": "req_9f2c4a",
"route": "/v1/chat/completions",
"body": "{\"messages\":[…]}",
"model": "gpt-4o",
"latency_ms": 842,
"policy_ref": null,
"signed_decision": null,
"flush": "pending_batch_7"
}
{
"v": "kovera.sovereignty_receipt.v1",
"receipt_id": "sr_01k8q2x7hmz",
"decision": "PERMIT",
"decision_hash": "sha256:e3b0c44…9c2d",
"parent_anchor": "merkle:0x4a91f…",
"policy_bundle_ref": "pol_v2026.05.1",
"mediation": {
"latency_ms": 8,
"human_gate": "not_required"
},
"signature_alg": "RS256",
"signature": "MGUCMFE…",
"verify": "https://verify.kovera.tech/r/sr_01k8q2x7hmz"
}
Traditional Guardrails (Post-Mortem Logs)
Traffic Routing & Rate Limiting
Kovera Runtime Firewall
Inline Blocking & Human Intervention
Traditional Guardrails (Post-Mortem Logs)
Operational Telemetry (Logs)
Kovera Runtime Firewall
Cryptographic Attestation
Traditional Guardrails (Post-Mortem Logs)
Mutable JSON Logs
Kovera Runtime Firewall
Tamper-Proof Activity Receipts
Traditional Guardrails (Post-Mortem Logs)
Internal Database Only
Kovera Runtime Firewall
Independent Public Verification Path · verify.kovera.tech
Traditional Guardrails (Post-Mortem Logs)
Post-incident Reviewer
Kovera Runtime Firewall
Real-time Veto Authority
| Feature | Traditional Guardrails (Post-Mortem Logs) | Kovera Runtime Firewall |
|---|---|---|
| Primary Function | Traffic Routing & Rate Limiting | Inline Blocking & Human Intervention |
| Trust Model | Operational Telemetry (Logs) | Cryptographic Attestation |
| Evidence Type | Mutable JSON Logs | Tamper-Proof Activity Receipts |
| Verification | Internal Database Only | Independent Public Verification Path · verify.kovera.tech |
| Human Role | Post-incident Reviewer | Real-time Veto Authority |
Deploy gateways for how traffic flows. Deploy Kovera for what was permitted. You get proofs your auditors can recompute.
The Evidence Gap
Legacy gateways record damage after the fact. The APoR prevents it on the execution path. Enterprise compliance teams face an Evidence Gap: they cannot cryptographically sign off on autonomous agent deployments using logs alone.
verify.kovera.tech · no login · independent verification
Route traffic through api.kovera.tech — complementary to your AI gateway — so policy, receipts, and verification stay aligned.
Apply runtime interception checks: intent binding, schema validation, provider attestation, content redaction, and collective defense.
Generate SHA-256 signed event records.
Auto-sync evidence to Vanta, Drata, or your Auditor.
Kovera routes every agent intent through two enforcement paths. Routine actions clear in milliseconds. High-stakes actions pause for a human decision — and that decision becomes a tamper-proof activity receipt.
Tamper-Proof Receipt
Every high-risk intervention generates a tamper-proof activity receipt. This isn't just a log entry; it's a non-repudiable artifact.
dh_sha256:a3f9e1c2b804d57f3a91e6c4d2b30e7a1f58c9d6e2a04b73f1c8d5e9a2b30c74
What changes when Kovera is deployed
Agent actions are unaudited — no cryptographic record of what ran or why
Every action cryptographically logged — SHA-256 hash chain, tamper-evident from first call
Incidents discovered in post-mortem, days or weeks after damage is done
High-risk actions blocked at runtime in <12ms — before damage, not after
Compliance evidence assembled manually — weeks of engineer time per audit
Audit evidence auto-generated — signed PDF/JSON exports ready on demand
High-risk agent actions proceed silently — security team has no visibility or veto
Security team gets Slack Approve/Deny on every escalation — full context, one click
~$4.88M average cost of an uncontrolled incident (IBM Cost of a Data Breach 2024)
Human decisions sealed as tamper-proof activity receipts — permanent, auditor-grade record
IBM Cost of a Data Breach 2024 · Ponemon Institute AI Incident Research · conservative $75K/intervention floor used in SAVI dashboard
Five inline blocking checks translate policy rules into clear outcomes—not mutable logs you discover after an incident.
RSA-2048 signing locks the agent's system prompt. Any material deviation from the bound intent triggers an immediate session revocation.
Static analysis of tool-call payloads ensures malformed schemas and injected parameters are rejected at the edge.
Cryptographic binding between your policy and the LLM endpoint prevents mid-session model-hijacking or unverified routing.
Real-time scanning for PII leakage and policy violations ensures compliance before data egress.
Cross-session analysis detects coordinated, multi-turn prompt injection sequences across your entire agent workforce.
Trust must be open-source. Enforcement must be enterprise-grade.
liability-receipt/v1 standard specification and canonical JSON schema@kovera/verify — fully stateless, zero-dependency cryptographic verification engineaegis/1 ledger pre-image, hash-chain verification, and Art. 12 manifest bundlesValue: Auditors, third-party SIEMs, and partners can independently verify the cryptographic integrity of any session receipt offline—free of vendor lock-in.
Developers
@kovera/verify
Offline
import { verifyReceipt } from '@kovera/verify'; const result = verifyReceipt(receiptJson); if (result.isValid) { console.log('Session cryptographic integrity verified.'); }
When Kovera intercepts a policy violation, your team receives an instant Slack alert with full context: the agent, the blocked action, and the specific rule triggered.
Kovera runs alongside your AI gateway for runtime interception, tamper-proof activity receipts, and verification—without replacing routing, auth, or quotas.
Request path
Kovera: the protocol layer enterprises use to govern agents at machine speed.
Sidecar enforcement
<10ms overhead on typical policy paths.
Fails-open architecture
High availability by default when runtime interception is unavailable.
Non-custodial
We never touch your provider keys; they stay in your vaults and gateway.
Centralize agentic oversight. The dashboard provides a real-time feed of agent calls, policy enforcements, and the cryptographic proof backing every decision. Vanguard highlights materially sensitive paths so reviewers can prioritize without leaving the stream.
External audit validation
External reviewers expect continuity between live operations and reproducible artifacts: a visible record of who can approve a privileged path, and evidence that survives export. The first frame shows the Kovera Ledger with PERMISSION_REQUESTED and the human gate in-line; the second frame shows the enforced outcome anchored with a tamper-proof activity receipt you can verify independently.
Not a testimonial—illustrative validation framing only. Technical detail in the proof model overview.
Every agent action is captured as a SHA-256 signed record, anchored to a tamper-evident log. We don’t just log history; we notarize it.
Tamper-evident, chronologically ordered event records. Each row binds to the prior anchor so silent edits fail verification.
Machine-readable packs designed for forensic auditors and internal review workflows.
Automated evidence pipelines for Business and Vanguard tiers.
JSON-Signed Audit Log
Enterprise ready
Threat model, data boundaries, failure modes, receipt verification, and PII posture—what security reviews need before a pilot.
Kovera
Runtime security tiers for agentic teams — feature comparison below. For pricing and procurement, contact contact@kovera.tech.
Kovera
Self-serve governance POC — ship a verifiable receipt to your security buyer
Kovera
For growing teams
Kovera
For security-first teams
Contact for pricing
contact@kovera.techKovera
For enterprise AI workforces
Kovera
For global enterprises
KVR-105b · Pay-as-you-Mint
Verification on verify.kovera.tech stays free for auditors and third parties. Production ledger mints consume anchor credits — email contact@kovera.tech for pack pricing and capacity.
Contact for anchor creditsSHA-256 Hash Chained
AES-256 Encrypted
Runtime interception, tamper-proof activity receipts, and how Kovera differs from gateway-only stacks or plain audit logs.
Open full FAQCompliance exports, retention, integrations, and deployment patterns.
Click our email below to copy it to your clipboard, then paste into your mail client.
Compliance-ready infrastructure for Global Standards
Audit-ready infrastructure with complete cryptographic traceability and immutable evidence logs.
Data sovereignty guaranteed. Local processing with edge-first security perimeter and zero code storage.
Enterprise-grade encryption (AES-256) with audit trail integrity and access control federation.
RSA-2048
SHA-256
AES-256