Question 1

Does the AI provider ever receive the raw records?

Accepted Answer

No. It runs next to the data under the contract's field and output limits. The provider gets the permitted outputs and the bundle. The raw records never move.

Question 2

What stops a workload doing something outside the agreed scope?

Accepted Answer

The Pipeline Contract declares permitted operations, field scope and output restrictions before execution. The Compex runtime sits inside a Trusted Execution Environment, where memory is encrypted at runtime and isolated from the host operating system and hypervisor. The workload cannot bypass the contract even if the underlying host machine or container orchestrator is compromised. An out-of-scope operation is refused while the job is running, and the refusal is written into the evidence bundle as a blocked action.

Question 3

How do we verify the evidence bundle is genuine?

Accepted Answer

Each event and each export file is hashed independently, and the hashes are chained in order. The bundle also carries a cryptographic remote-attestation quote anchored to the underlying TEE hardware (AMD SEV-SNP, Intel TDX or NVIDIA Confidential Computing). That proves the hashes were generated inside a genuine, un-tampered enclave running the exact signed Pipeline Contract. Checksum verification compares stored values against computed ones, and the bundle exports as JSON, PDF and CSV for your reviewer to check directly.

Question 4

Where does the data sit, and where does processing happen?

Accepted Answer

Deploy Compex in your existing cloud VPC on confidential instances (AWS, GCP and Azure Confidential VMs, including Confidential H100 and Blackwell GPUs) or on-premises on air-gapped hardware. Data never leaves your residency boundary.

Question 5

Does Compex make our project GDPR compliant?

Accepted Answer

No. That is your assessment to make. We give you what it needs: the signed contract, the runtime, and the run record.

Question 6

What happens to outputs and data after a run?

Accepted Answer

Duration and retention are fields in the Pipeline Contract, agreed before execution. Output restrictions limit what may leave, and the bundle records what was produced and what was blocked.

Architectural layer	Cloud Confidential VPC	On-Premise / Air-Gapped
Where the data lives	A sovereign cloud enclave inside the hospital's VPC, next to the EHR.	Hospital-owned GPU servers behind the clinical firewall, including air-gapped research wings.
TEE hardware target	AWS Nitro Enclaves; Azure/GCP Confidential VMs on AMD SEV-SNP or Intel TDX; NVIDIA H100 confidential GPUs for imaging.	Bare-metal AMD EPYC (SEV-SNP), Intel Xeon (TDX) and NVIDIA H100/Blackwell GPU TEEs over encrypted PCIe.
Who is locked out by the TEE?	Cloud provider admins, the host OS/hypervisor and the external AI vendor.	Internal root sysadmins, hypervisor operators and third-party model/agent developers.
Network & egress rule	VPC-peered zero-egress subnet; keys are released only after the attestation quote matches the contract.	Strictly air-gapped: 0.0.0.0 outbound blocked. The local verifier checks the silicon signature offline.

Run clinical AI inside the hospital's trust boundary, not around it.

The policy gate holds when the workload does not.

One trust anchor. Two perimeters.

The file your CISO and legal reviewer can check themselves.

Bring one clinical AI pilot.