Core Concepts

The Veil — Confidential execution

Every job runs in a sealed enclave. The operator supplies compute but never sees your prompt, working data, or output — enforced by hardware, not policy.

How it works

Each job is dispatched into a confidential environment on the chosen node. Techniques in scope span the confidential-computing spectrum:

  • TEE — hardware trusted execution environments: CPU enclaves (Intel TDX, AMD SEV-SNP) paired with confidential GPUs (NVIDIA H100 / H200 Confidential Computing), so the model runs at near-native speed inside the sealed boundary — the primary path for real-time inference. Even the host cannot read the workload.
  • FHE — fully homomorphic encryption for select, non-interactive workloads (orders of magnitude too slow for real-time chat) that compute directly on ciphertext.
  • MPC — secure multi-party computation splits trust across parties, also for select workloads.

What's sealed

Inside the Veil, the node operator cannot observe:

  • Your prompt and system instructions
  • Working data — documents, embeddings, retrieved context
  • The model's output
  • Agent memory, tools, and API keys, for sealed agent runs

Privacy attestation

On completion the enclave emits a signed privacy attestation, rooted in hardware attestation, proving the workload ran in an approved confidential environment. This attestation is bound into the job's Green Compute Certificate — so privacy is a receipt you can audit, not a promise on a landing page.

Status: hardware-attested enclaves (H100 / H200 CC) are on the Phase 1 roadmap, not live yet. Today the gateway emits the attestation in its final wire shape with a cryptographic stand-in, so certificates stay comparable as real TEE quotes get wired in. We list this explicitly rather than pretending it already runs on hardware.

Use cases

  • Regulated data — health, legal, finance — that can't leave your control in the clear.
  • Confidential fine-tuning and private RAG over your own documents.
  • Bring-Your-Own-Model hosting where weights are never exposed to operators.
"Send it to someone else's GPU" is a non-starter for proprietary data — unless it comes back with a verifiable receipt. The Veil is that receipt.