No compliance badges
Zephr does not claim SOC 2, ISO 27001, HIPAA, GDPR certification, or any other third-party attestation. When an audit is completed, the report will be linked here — not a logo.
Use cases / Enterprise
AI governancethat doesn't slow you down.
The governance primitives are shipped and running in local mode today: authorization before retrieval, immutable scope binding, consent receipts on every operation, and abstention when the evidence does not hold. The organization-level controls layered on top of them require the managed cloud and are not built.
Primitives shipped · Org controls plannedauth-before-retrievalimmutable scopeaudit receipts
The problem
Vendor-native memory is siloed and unverified.
AI tools capture decisions without provenance, carry no audit trail, and cannot enforce policy across clients. Each editor is its own island, which means duplicated risk and no reliable governance surface to point a reviewer at.
No provenance
Decisions are remembered as opaque summaries. When a reviewer asks what a claim rests on, there is nothing to traverse.
No audit trail
What the AI read, wrote, or approved is trapped inside one client on one machine, and evaporates when that session closes.
No enforced policy
Project rules live in advisory files. Enforcement depends on whether each tool chose to read them, which is not a control.
What exists today
The governance primitives are already real.
Even in local mode Zephr ships the trust primitives that organization governance would scale: the policy engine, immutable scope binding, consent receipts, and honest abstention. The four controls above them are designed and not built.
Trust Firewall policies
ShippedDeterministic, worktree-scoped policies gate both capture and retrieval. A refusal names what was missing rather than returning a generic block.
policy engine · Guard cluster
Immutable scope binding
ShippedProject, repository, and worktree are admitted once and bound for the lifetime of the connection. Changing scope requires a newly admitted connection, not a parameter.
ScopeSnapshot · binding_epoch CAS
Per-request consent + audit receipts
ShippedEvery read and write carries explicit consent and produces a durable receipt scoped to digest, operation, identity, and timestamp.
receipts as durable objects
Honest abstention
ShippedBelow the confidence bar the system returns a typed abstention naming the gap, rather than assembling a plausible sentence from fragments.
honest-or-absent law · ADR-016
Organization-level controls
Planned (managed cloud)Organization-wide policy, project admission gates, and role-scoped permissions above the per-worktree primitives.
gated on the ADR-010 tenancy gate
Team-scoped policies
Planned (managed cloud)Rules that travel with the project rather than with one user or one advisory file, enforced identically for every connected client.
designed; not built
Audit export
Planned (managed cloud)Long-form evidence ledger and action history exported for compliance review, rather than read one receipt at a time.
designed; not built
Data residency options
Planned (managed cloud)Tenant-level control over where source, evidence, and derived indexes are stored and processed.
gated on the ZEP-1 security review
Shipped primitives run locally. Organization-level scaling requires the managed cloud and a security review that has not yet passed.
How it works
Authorization before retrieval.
The Trust Firewall proves who may see what before any memory is injected into a prompt. Every step produces a durable, inspectable receipt — all three stages below are shipped and run locally.
- 01
Scope admission
Every connection is bound to an explicitly approved project, repository, and worktree. A scope change is a new admission, not a mutable field on the session.
- 02
Policy evaluation
The Trust Firewall evaluates policy before retrieval or capture — never after. Refusals are specific enough to act on, which is what makes them auditable.
- 03
Receipt chain
Every operation produces a durable receipt scoped to digest, operation, identity, and timestamp. The audit trail is a by-product of the request path, not a separate logger.
Honest boundaries
What is not claimed.
Zephr does not market certifications, scores, or enterprise readiness that do not exist. This section is a public commitment to that boundary, and it is meant to be held against us.
Not claimedNot held Not claimedNot held No customer logos
There are no external design partners or customer references on this page, because there are none to reference.
Not claimedNot held No ROI promises
No savings figures, velocity gains, or risk-reduction numbers are stated, because none have been measured. TrustBench publishes what has.
Read the security model.
The trust page covers the TrustBench suite, the Trust Firewall, scope binding, and the evidence chain in detail — each linked to the source document rather than summarised.