Cardio-renal cohort
4 hospitals · EU + US + CH
“Multi-jurisdiction cohort study with on-chain co-approval. The aggregate is signed; the rows are not.”
1.6M records
zero rows leave silos · DP-aggregate out
Private AI-Daten · Compute-to-Data
Am Ursprung versiegelt. On-chain per Multi-Sig. Nur das vereinbarte Aggregat verlässt die CVM, signiert.
Daten-Topologie · 5 versiegelte Quellen
Daten haben Gravitation · Compute reist
EU-West · sealed
Hospital A
820k EHR
EU-North · sealed
Hospital B
410k imaging
US-East · sealed
Bank C
12M tx
APAC · sealed
Research D
56k samples
CH · sealed
Lab E
230k assays
analysis CVM
TDX + H100
cohort risk model
cpu
gpu
mem
multi-sig owner · 5 / 5
DstackApp.sol · 0x73c2…be09
signed output
dp-aggregate
ε = 1.5 · ✓ verified
receipt
sig chains TDX root + on-chain DstackApp
multi-party studies on dstack
Each consortium pins a single compose-hash; KMS only releases per- dataset keys when every owner has signed off through the multi-sig DstackApp owner.
name
owners
records
criteria 1
criteria 2
criteria 3
status
Cardio-renal cohort study
healthcare research
Cross-bank fraud signals
financial · AML
Rare-disease genomics
genomics · research
Supply-chain risk benchmark
B2B intelligence
ICU readmission cohort
clinical operations
Insurance claim adjudication
insurance · ops
Match / partial / miss reflect on-chain state of each consortium's DstackApp multi-sig vs the criteria.
Schalten Sie dstack aus, um zu sehen, wie die zentrale Pipeline wieder Zeilenzugriff erhält.
Versiegelte Daten bleiben am Ursprung · das Modell reist · Freigaben durch mehrere Eigentümer für jeden Schlüssel-Release
Jeder Eigentümer führt ein lokales Sealing-CLI aus: HKDF(kms_root_pubkey, analysis_app_id, analysis_compose_hash, owner_id). Verschlüsselt den Datensatz und veröffentlicht Ciphertext. Eigentümer senden niemals Klartext oder Schlüssel. Rezept ändern → Schlüssel passt nicht mehr.
CLI · Versiegelung
Each owner runs the local sealing script (HKDF-derived wrap-key bound to the analysis compose-hash). Plaintext never leaves the silo; only ciphertext + a recipe-bound envelope is published.
Freigabekonsole
Owners review the public compose-hash, then sign the multi-sig that owns DstackApp. Threshold-of-N before any key is released.
REST + Sign-RPC
Submit the analysis compose, fetch the signed aggregate. Every response carries a Sign-RPC envelope chained to TDX root + on-chain DstackApp.
Python in der CVM
Inside the analysis CVM, unwrap_dataset() asks dstack-guest-agent for per-owner keys. Joins, embeddings, and model passes — all in TDX-encrypted memory.
sealed dataset · cohort-A.tar
1.6M rows
Each owner's wrap key is HKDF(kms_root, app_id, compose_hash, owner_id). Change the recipe and the key changes — old ciphertext is permanently locked out. The wrap key itself only re-derives inside an attested CVM whose compose-hash matches.
DstackApp.sol · 0x73c2…be09
multi-sigDstackApp.sol holds the compose-hash. KMS only releases per-owner keys when every required owner has signed off through the multi-sig. Any single owner can revoke globally with one on-chain transaction — no coordination needed.
in production today · 3 live consortia
Cohorts where one breach used to mean everyone’s breach. Now: sealed at source, approved on-chain, signed aggregate out.
4 hospitals · EU + US + CH
“Multi-jurisdiction cohort study with on-chain co-approval. The aggregate is signed; the rows are not.”
1.6M records
zero rows leave silos · DP-aggregate out
6 banks · US + UK + SG + DE
“Joint AML model trained without any bank seeing another bank’s ledger. The model file IS the receipt.”
78M transactions
k-of-n quorum · Sign-RPC envelope
8 vendors · US + EU + APAC
“Federated benchmark whose output type is locked to the registered compose. No back-channel exfiltration.”
12M records
output type bound to compose-hash
HIPAA-grade
sealed clinical cohorts
GDPR / UK GDPR
data residency preserved
PCI / FFIEC
cross-bank joins on-chain gated
SOC 2 Type II
attested run history
KI-Lösungswege
Der private Modell-Endpunkt ist der erste Einstiegspunkt. Dieselbe Datenschutz-Primitive lässt sich auf Agents, Daten-Workflows und Training ausweiten.
OpenAI-kompatible Modellaufrufe bereitstellen, bei denen Prompts, Outputs und Kundenkontext Schutz durch Verschlüsselung während der Nutzung benötigen.
128K
$0.27/M input
256K
$0.40/M input
128K
$0.15/M input
128K
$0.10/M input
200K
$3.00/M input
1M
$1.25/M input
Agenten mit Schlüsseln, Tools, Speicher und Aktionen in einer verifizierten Laufzeit ausführen statt in einer sichtbaren Automatisierungs-Cloud.
Passe Modelle an proprietäre Daten an, während Datensätze, Gradients, Checkpoints und Evaluations-Traces innerhalb der Grenze bleiben.
private training run
01
sealed
02
running
03
private
04
verified
loss curve
proof attached
attestation.json
Run compute-to-data
Datensätze an der Quelle versiegelt. Multi-Sig-Freigabe on-chain. Nur die vereinbarte Aggregation verlässt die CVM, signiert.
© 2026 Hashforest Technology. Alle Rechte vorbehalten. Datenschutz • Nutzungsbedingungen