Live demo: HG002 30× WGS, NVIDIA GB10 verified

Run metadata

Sample

HG002 (NIST GIAB, public reference)

Coverage

30×, paired-end short read

Reference

GRCh38_no_alt_analysis_set

Pipeline

Parabricks 4.7.0-1, DeepVariant germline (fq2bam + variantcaller)

Image digest

sha256:5bc63974…086f5287e2b (linux/arm64, pinned in PIPELINE_LOCK §2)

Hardware

NVIDIA GB10 (driver 580.142) — a single under-desk GPU

Wall-clock

1h 52m 13s, fq2bam + DV-germline end-to-end

Signed at

2026-05-10T21:58:31Z

Job ID

df1513436092423fb129c16913b53ea5

Verify the signature offline (≈5 seconds, no infra)

Download the three files below and run the verifier from this repo. Exit code 0 proves Ed25519 signature validity over the JCS-canonical manifest. The verifier ships standalone — no compute layer required.

# 1. Install the verifier (one-time)
pip install genomics-analysis  # or clone the repo and pip install -e .

# 2. Verify
genomics-verify manifest.json signature.json --public-key showcase-public.pem
# Expected:  OK — signature valid for this manifest.
#            public key id: d72135b46db8ae1d…2276e3e

Public key fingerprint: d72135b46db8ae1d211a6e6e44f9efb2d1717efe5a18c276e543aab2d2276e3e. This is the showcase signing key; a production-rooted KMS key replaces it for paid runs (per SIGNING_KEY_PUBLISHING).

Deliverable artifacts real bytes

Click any row to download. SHAs match what's pinned inside the signed manifest.

The full VCF (96 MB) and BAM (66 GB) are large clinical artifacts; we gate them behind LOI signature in the real customer flow. Their SHA-256s are pinned in the signed manifest above — your QMS reviewer can audit the chain-of-custody without seeing the bytes themselves.

QC report (real, schema-validated)

Every per-sample delivery ships a JSON QC report against QC_REPORT_SCHEMA. This is the actual JSON from the run above:

{
  "schema_version": 1,
  "job_id": "df1513436092423fb129c16913b53ea5",
  "sample_id": "HG002-WGS-30x-SHOWCASE-2026-05-10",
  "pipeline_version": "0.1.0-substrate-showcase",
  "generated_at": "2026-05-11T13:00:00Z",
  "qc_status": "PASS",
  "qc_reasons": [],
  "metrics": {
    "alignment_rate_pct": 99.55,
    "mean_coverage": 32.49,
    "ti_tv_ratio": 1.99,
    "het_hom_ratio": 1.42,
    "variant_counts": { "snp": 3940122, "indel": 891103 }
  }
}

What's next

You just saw the entire results experience without signing anything. If you want to run a real pilot — your own FASTQ, your own per-customer bucket, your own signed manifest — here's what changes:

• Same artifacts, your sample. Same Parabricks digest, same QC schema, same signed manifest — your sample_id, your job_id, your bucket prefix.
• Per-customer prefix isolation. Your FASTQs land at gs://datamade-genomics-delivery/customers/<sha(your-email)[:16]>/uploads/ with per-prefix scoped IAM (Terraform module on the diligence page).
• Production-rooted signing key. A KMS-backed key replaces this showcase key once your LOI is signed — published fingerprint pinned in your pilot agreement.