Esacode

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.

Run evidence record: a summary card with job, inputs hash, preset version, hardware, metrics and a verification status

What a record will contain

In development

Inputs

Hashes of the scene, dataset and configuration files a job read.

In development

Code and preset

Preset version, container image digest and parameters.

In development

Hardware

Worker, GPU models and driver version the job ran on.

In development

Outputs and metrics

Hashes of outputs and the metrics the job reported.

In development

Timeline

Queued, started and finished times with the user who launched it.

In development

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.

Job detail page showing the recorded spec, worker and output index

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.