~/aver $ about --mission

Validation that keeps pace with the pipeline.

Aver fingerprints every dependency, benchmarks against public reference standards and records the effect of every change, so a lab always knows where its validation stands.

Why Aver exists

Revalidation is manual, so it falls behind.

A clinical pipeline must be revalidated whenever it changes. Today that looks like this.

Step 01
Re-run reference samples by hand.
Step 02
Tabulate results in a spreadsheet.
Step 03
Write a report for the quality system.
Step 04
The pipeline changes again. Steps 1 to 3 don't repeat.
Validation debt

Founder

Built to make the evidence hold up.

Talk to the person building it, directly.

founder.note · 001transmitting

Labs validate a pipeline once, carefully. Then it keeps changing, and the paperwork falls behind what is actually running.

I started Aver to close that gap with engineering, not paperwork: fingerprint every dependency, benchmark against public reference materials, measure every change, and produce evidence an inspector can verify.

Two decisions came first. Aver never touches patient data. And Aver produces evidence, not verdicts; your laboratory and your accreditor decide.

If revalidation keeps slipping in your lab, I'd like to hear how you handle it today.

Sadeeq KhanFounder, Aver

Principles

What we hold ourselves to.

Design constraints, enforced and tested in the code.

No patient data, ever

Only registered public reference materials are accepted.

Rules, not models

Every flag stores the rule that fired it.

Deterministic

Same inputs, byte-identical evidence, anywhere.

Read-only

Never asks for write access to your code or registry.

Append-only record

A hash-chained audit history, verified nightly.

Open-source core

The CLI is Apache-2.0, on PyPI as aver-bio.

Tell us how your lab revalidates today.

A short conversation about your pipelines and your last inspection. Or try the product first.

Book a demo

Follow Aver