Skip to main content
The gateway and verifier are open source. Verification separates source labels from the hardware-bound measurement used to accept a release.

​
Source labels and release identity

Every attestation report includes attestation.source_provenance:
These fields identify the source claimed by the workload. They are useful for finding code to review, but are not cryptographic proof that the workload was built from that commit. The verifier instead checks that sha256(app_compose) matches the compose hash measured into RTMR3. After reviewing a release, publish that hash through an authenticated channel and require it through acceptedComposeHashes. A match then proves that the approved measured compose is running in the attested workload.

​
Repositories

private-ai-gateway

The Attested Confidential Inference gateway: the API surface, attestation reports, receipts, and provider verification.

dstack

The dstack TEE runtime and KMS the gateway uses for workload identity and quotes.

RedPill on GitHub

The organization, clients, and tooling.

​
What you can check from source

  • Attestation handling. How the gateway builds the report, binds the nonce and keyset into the quote, and endorses its signing keys.
  • Provider verification. How each confidential provider is verified and which channel binding is enforced before forwarding.
  • Receipts. How the transparency event log is built and signed, and that bodies are hashed, not stored.
  • Fail-closed forwarding. That a required upstream which cannot be verified or bound is rejected.

​
Reporting a vulnerability

Report security issues privately to support@redpill.ai rather than in a public issue. Include reproduction steps.

Attestation report

Verify a response