Witbitz · trust

Don't trust us. Check us.

Every privacy page on the internet asks you to believe it. This one gives you commands. Below is exactly what you can confirm from outside, exactly what you can't yet, and the line between them — including the part that doesn't flatter us.

Run the checks Read the render (~600 lines)

The scoreboard

The admission gate enforces. On a gated Space, reads and writes are refused without an allow-listed identity — even if you hold the room key.checkable now
Egress is locked. The app you loaded can reach only a published allowlist of hosts. The browser enforces it, not us.checkable now
Content-blind at rest. The store holds ciphertext sealed to your room key. There is no operator recipient in the envelope.checkable now
The render is a reproducible build. Rebuild from published source and get the same hash AWS runs.checkable now
Unobservable in use. That during the decrypt-and-render instant, the operator can't read plaintext out of memory.built & verifiable — not yet on production traffic

Why the last row is on this page

Because a security claim that lists only what it covers is marketing.

The attested tier is real and it is built: the room key is generated inside AWS Nitro hardware and never leaves it, the image measurement is reproducible from published source, and the whole attestation check — hardware signature, certificate chain to a pinned AWS root, a nonce for liveness — runs in your browser. It has been demonstrated end to end with the real agent answering in a real room.

And no production Space runs inside an enclave today. So it is a demonstrated capability, not a property of your room. When that changes, /cert.json will carry an enclave block naming the measurements and a new test will appear on the verify page. Until then we'd rather you knew.

What is never hidden

Sealing content does not seal its shape, and no amount of cryptography changes that:

  • Metadata. That a room exists, when it changes, and roughly how large each write is.
  • The model provider. A turn's text reaches whichever model answers it — that is what an agent is. Attestation protects the key and the code; it can't make a remote API stop seeing its input.
  • Availability. We can refuse to serve you. We can't read you.
  • Reproducibility isn't behaviour. It proves the running code is the code you can rebuild. Whether that code does what we say is what reading it is for — which is why the render is small and published.

If you'd rather not trust us at all

Run it yourself. The runtime ships as a container: your cloud tenant, your model endpoint, your object store, your identity provider. Same reproducible build — so you can confirm the image you're running is the one we published.

Two routes to the same property. One asks you to check our infrastructure; the other removes it from the question. Neither asks for the benefit of the doubt.