Appearance
Federated Clean Room
Availability
Federated Clean Rooms require an Enterprise subscription. The feature is gated by the clean_room feature flag.
The Federated Clean Room enables multiple organizations to run joint computations on combined data without exposing raw inputs to each other. Each party attests to the exact computation environment, results are held in encrypted escrow until all parties approve release, and independent provenance records are generated per organization.
Use Cases
- M&A due diligence -- model revenue overlap and customer concentration risk without exposing either party's raw financial data
- Joint research -- combine clinical datasets from multiple institutions under HIPAA-compliant governance
- Supply chain analysis -- benchmark cross-org logistics without sharing proprietary cost data
- Regulatory collaboration -- share aggregated findings while keeping individual submissions confidential
Lifecycle
Clean rooms follow a strict state machine:
1. Create
The initiating organization creates a clean room with a name, description, and optional computation template.
2. Invite and Accept
The initiator invites partner organizations by org ID. Each invited org must explicitly accept the invitation to become a participant.
3. Set Computation Template
The computation template defines the exact code that will run. When the template is set, an attestation bundle is generated containing SHA-256 hashes of:
- Image hash -- the PhD sandbox Docker image
- Code hash -- the computation template
- Config hash -- sandbox configuration and governance policies
- Combined hash -- a single hash of all three for convenience
The bundle moves the clean room to attesting status.
4. Mutual Attestation
Each participating organization reviews the template, image, and configuration, then submits their attestation with the bundle hash. This confirms that General Counsel or the designated reviewer has approved the exact code and environment.
When all participants have attested, the clean room moves to ready.
5. Execution
Computation runs in a gVisor-isolated PhD sandbox. Each organization's data enters through its own governance channel (Dymium connection with per-org column masking). The clean room enforces the intersection of all governance policies -- the most restrictive rules from any party apply.
Results are encrypted with AES-256-GCM and placed in escrow.
6. Release or Reject
Each organization's designated approver reviews a summary of the results (without seeing the full payload). All parties must approve for results to be released. If any party rejects, encrypted results are destroyed and provenance records note the rejection.
7. Provenance
Each organization receives independent provenance records proving:
- What computation code ran (SHA-256 verified)
- What sandbox environment executed it (image hash verified)
- What their side contributed (input lineage -- the other party's inputs are not visible)
- What the output was (shared, identical hash)
- When each party attested and approved
Security Model
| Control | Implementation |
|---|---|
| Data isolation | Each org's data enters through its own Dymium connection with org-specific masking |
| Policy intersection | Most restrictive governance rules from all parties apply |
| Attestation | Cryptographic hash verification of image, code, and config |
| Escrow | AES-256-GCM encrypted results, dual-approval release gates |
| Provenance | Per-org audit records with row-level security in PostgreSQL |
| Sandbox | gVisor-isolated PhD container with no network, read-only filesystem |
| TTL | Escrowed results auto-expire after configurable period (default 7 days) |
Configuration
| Variable | Default | Description |
|---|---|---|
CLEAN_ROOM_ENABLED | false | Master toggle |
CLEAN_ROOM_MAX_PARTICIPANTS | 10 | Max organizations per clean room |
CLEAN_ROOM_RESULT_TTL_HOURS | 168 | Escrow expiry (7 days) |
CLEAN_ROOM_REQUIRE_ATTESTATION | true | Require all orgs to attest before execution |
Clean Room also requires PHD_MODE_ENABLED=true and SANDBOX_ENABLED=true.
Related
- GhostScience -- PhD computing engine overview
- Workspaces -- notebook-style workspaces with clean room linking
- Clean Room API Reference -- REST endpoint documentation
- SDK Reference -- Python client library
- Admin Configuration -- all environment variables
- Examples -- scripts 11-15 cover the full clean room lifecycle