Skip to content
Ryedore Logo
Theme
ContactRequest Demo
Industrial machinery with instrumentation

Run the audit yourself

Our proof, packaged. Verify it, reproduce it, run it on your data — yourself.

A signed evidence bundle and an open benchmark harness. Check the integrity and the signature, reproduce the published numbers on public data, then run the same harness against your own dataset on your own machines. Ryedore does nothing on your behalf — and nothing here is a pilot or a trial.

Download the signed bundle (97 KB)How to run it
21+ signed reports
signed reports, re‑runnable
signed · re-runnable as of Aug 2026
17.85 RMSE
remaining life · FD002
signed · re-runnable
0.992 AUC
anomaly · real labels
signed · re-runnable
0 third‑party models
models from outside the stack
attested
in one picture

The whole audit — four offline steps, nothing sent to us

From the signed bundle to your own dataset. Each step is detailed below; none of them needs a conversation with Ryedore.

The bundlesigned .zip1Integrityevery hash checked2AuthenticityRSA-PSS · key in the pack3Reproduceharness + public data4Your datayour machines onlyevery step is offline and self‑serve — nothing is sent to Ryedore, nobody from Ryedore touches your dataget the same numbers — or the signature breaks
Four steps, in a sceptical engineer’s order — and nothing along the way requires talking to us.

swipe → to see the whole diagram

four steps, no trust required

Verify, reproduce, then run it on your data

In the order a sceptical engineer would do it.

IntegrityAuthenticityReproduceYour data

  1. 1 · Integrity

    Download the evidence pack and run sha256sum -c SHA256SUMS. Every file must match its recorded hash — any machine, no dependencies.

  2. 2 · Authenticity

    The whole bundle is signed with RSA‑PSS/SHA‑256 under the public key shipped inside it. Run verify.sh (or the Python one‑liner in VERIFICATION.md): the manifest hash, every file and the signature must all come back true. Each per‑task report is signed independently too.

  3. 3 · Reproduce the numbers

    The benchmark harness is open (Apache‑2.0), isolated, uses public datasets only, and reports multi‑seed mean ± std — no single‑seed cherry‑picking. Provenance, Python version and pinned dependencies are in environment.json. Run it; get the same numbers, or the signature breaks.

  4. 4 · Run it against your own data

    The same harness runs on your machines against your own dataset: point its loader at your data, keep the same metrics and seeds, and compare. Nothing is sent to Ryedore; nobody from Ryedore touches your data. What you see is what it does.

# from inside the unpacked bundle
sha256sum -c SHA256SUMS
./verify.sh # manifest hash · files · RSA‑PSS signature → all True
# reproduce (public datasets + harness, see VERIFICATION.md §3); then point the loader at your own data
Read VERIFICATION.md on the web →Raw file →The report (wins and losses) →The scoreboard →

Don’t take our word. Take the bundle.

We publish our losses on public data for the same reason we hand you the harness: a result you can’t re‑run is marketing. signed · re-runnable

guided · copy-paste

The four commands, with what you should see

Same steps as above, as a walkthrough: copy each command, run it on your machine, compare the output.

1 · Download and unpack

What it proves: You are working from the same bytes we published.

curl -O https://ryedore.com/verify/audit-bundle-2026-09-01.zip
unzip -q audit-bundle-2026-09-01.zip -d ryedore-audit && cd ryedore-audit

You should see: A folder with audit_report.html, audit_report.pdf, evidence/, manifest.json, manifest.sig, license_public.pem, SHA256SUMS, verify.sh.

Nothing runs on this page and nothing is sent to us — these are the commands for your own machine.
questions

Six straight answers

Is this a pilot or a free trial?
No. Ryedore does not run pilots or trials. This page gives you the signed evidence and the open harness so you can check our published numbers and run the same tests on your own data, yourself. Commercial engagements start from the published price list.
What do I need?
Any machine for the integrity check; Python with the cryptography package for the signature check; the public datasets (NASA C‑MAPSS, UCI Hydraulic) and the harness for a reproduction; your own data in the harness’s loader format for a run on your data.
Will Ryedore help me run it?
The bundle’s VERIFICATION.md and the harness README are written so you don’t need us — VERIFICATION.md is also readable on the web at /audit/docs/ before you download anything. Questions about the method are welcome on the contact page; we won’t ask for your data.
Where do the numbers on this site come from?
Every Ryedore figure on the site is read from a number registry whose signed entries trace to this bundle. Comparison figures are quoted from the named publications for disclosure.
How long does it take?
Integrity and authenticity: minutes — two commands on any machine. Reproducing the published numbers: longer, and it depends on your hardware, because the harness trains and evaluates multi‑seed on the public datasets; VERIFICATION.md states the pinned environment. Running on your own data takes as long as your dataset is large.
Can we share the bundle inside our company?
Yes. It is public, unsigned‑for‑nobody‑in‑particular: no NDA, no registration, no licence key. Forward the zip; anyone with it can verify it independently, which is the point.
where next

After the audit

Ready to talk numbers — yours?

Pricing is public. When your own run convinces you, the price list is where the conversation starts.

See pricingRequest a demo