Your environment.
A defined run.
A customer-operated runner picks up an approved job. Models, data and compute stay within the configured execution boundary.
Execution, with a record.
Keep supervised ML runs on infrastructure you operate. Carry the signed execution evidence into your next review.
Research preview · Supervised execution · Customer-operated runners
A smaller layer. A clearer record.
CloudTune connects execution, recovery and evidence around the infrastructure you already operate.
A customer-operated runner picks up an approved job. Models, data and compute stay within the configured execution boundary.
Leases and generation fencing separate the current owner from an expired attempt. Late results cannot overwrite a newer generation.
Export signed evidence and verify it offline against a trusted runner key. The record remains inspectable when the control plane is unavailable.
A signature establishes integrity and signer identity against a trusted key. It does not prove model quality or that training occurred.
Touch the evidence.
Generate a signed example, change its contents, and watch verification reject it. The trust anchor is kept separate from the receipt.
Simulated execution.
Real browser cryptography.
This example runs no training and makes no API request. It uses an illustration schema, separate from production runner receipts.
Ready to create a demo receipt
The signing key is created in memory for this demonstration. This is local demonstration trust, not a production identity.
{
"kind": "cloudtune-browser-demo/v1",
"state": "waiting_for_your_first_receipt"
}Nothing to install. No dataset to upload. The receipt is generated on this device.
The current boundary
This is a research preview with reviewed engineering evidence; production qualification is not ready. External validation remains open.
Start with the workflow.
Bring a recent ML run, the review that followed, and the evidence that was missing. That is the conversation CloudTune needs next.