Skip to main content
Phala Confidential AI is designed so privacy and integrity claims can be checked with technical evidence: attestation reports, source provenance, signed receipts, and provider verification records.
Read Trust Boundary first. The gateway is attested and receipts do not retain request bodies, but plaintext is visible inside the attested gateway after TLS termination or E2EE (end-to-end encryption) decryption.

​
Technical Controls

ControlHow Confidential AI provides it
Data isolationGateway and confidential providers run in TEEs.
Hardware-backed identityThe gateway publishes an attestation report with a TEE quote.
Per-response auditabilityReceipts bind request and response hashes to the attested workload.
No body retention in receiptsReceipts store hashes and facts, not prompt or response text.
Confidential upstreamsFor confidential responses, the upstream is verified and channel-bound before forwarding.
Encryption in transitTLS for all requests, with optional E2EE.

​
Regulatory Fit

RequirementHow the architecture helps
Data minimizationGateway receipts avoid storing request and response bodies.
Confidential processingTEE isolation and attestation provide verifiable runtime identity.
Audit evidenceAttestation reports, receipts, sessions, and source provenance can be retained by the customer.
Provider separationReceipts distinguish confidential upstreams from routed third-party providers.
For regulated data, use confidential responses and verify upstream.verified.result = verified, required = true, and the provider claims your policy requires.

​
Source Provenance

Every gateway attestation report includes attestation.source_provenance: 
{
  "repo_url": "https://github.com/Dstack-TEE/private-ai-gateway.git",
  "repo_commit": "9d45c7e3d48d2f74c31cd85f1fb5c6cee1435ef3",
  "image_digest": null,
  "image_provenance": null
}
Use these fields to compare the running workload against the source release you are willing to trust.

​
Relevant Repositories

private-ai-gateway

ACI gateway, attestation reports, receipts, and provider verification.

dstack

TEE runtime and KMS used for workload identity and quote generation.

​
What to Audit

  • Attestation report generation and nonce binding.
  • Keyset endorsement and receipt signing keys.
  • Provider verification and channel binding.
  • Receipt event log construction.
  • Fail-closed behavior when confidential upstream verification is required.
  • Source provenance and image provenance for production releases.

​
Enterprise Documentation

Compliance reports, enterprise security reviews, DPAs, BAAs, and certification scope can change over time. Request current documents from Phala through your account or enterprise support channel.

Attestation Report

Receipts and Sessions