Run evidence In development
Results you can prove, not just report
When a result matters to a customer, a regulator or a reviewer, EsaSim will be able to issue a record of exactly what ran: inputs, code version, hardware, outputs and metrics, sealed so it cannot be changed afterwards.

What a record will contain
Inputs
Hashes of the scene, dataset and configuration files a job read.
Code and preset
Preset version, container image digest and parameters.
Hardware
Worker, GPU models and driver version the job ran on.
Outputs and metrics
Hashes of outputs and the metrics the job reported.
Timeline
Queued, started and finished times with the user who launched it.
Independent verification
A record that a third party can check without access to your account.
Already recorded today
Every EsaSim job already keeps its spec, preset or flow version, worker, GPUs, logs and output index, and every dataset version names the run that made it and the versions it came from. Evidence records will be built from this data, so jobs you run now are ready for it.

Build your first study this afternoon
Create a free account, link GitHub, pair a computer and copy a demo, or describe what you need to your assistant. It takes about ten minutes.