Genetic History

Add ancestry to NGS reports. Patient data stays at your lab.

Our Self-Hosted Historical Genetic Narrative Module installs in your own infrastructure and runs offline after a periodic library sync. Your module pulls library updates at a cadence your lab controls — no patient data ever flows the other way.

Request a technical demo

30-minute walkthrough. No commitment.

Read the technical brief

Architecture, sync protocol, deployment options.

Genetic History push-model architecture: 5-step data flow with patient data staying at the partner lab. Push-model architecture data flow. The partner NGS lab runs sequencing locally and outputs VCF or BAM files at the partner site. The Genetic History module ingests these files locally at the partner lab and generates an ancestry narrative in prose. The partner delivers the narrative to the patient. The partner module pulls library updates from versioned HTTPS endpoints published by Genetic History, at a cadence the partner controls (weekly, monthly, or quarterly). Key differentiator: patient data never transfers to Genetic History infrastructure. Genetic History Module 1 Partner runs NGS sequencing 2 Outputs VCF/BAM at partner 3 Module ingests files locally 4 Module generates ancestry narrative 5 Partner delivers narrative to patient Library updates: lab pulls at controlled cadence from Genetic History. Patient data never transfers to Genetic History.
  1. Partner runs NGS sequencing
  2. Outputs VCF/BAM at partner
  3. Module ingests files locally
  4. Module generates ancestry narrative
  5. Partner delivers narrative to patient

Library updates: lab pulls at controlled cadence from Genetic History.

Patient data never transfers to Genetic History.

  • Push model — patient data never leaves your lab
  • EU hosting — Scaleway France (DC2 Vitry-sur-Seine, Val-de-Marne); library distribution only
  • ~12-year YFull substrate — Y-DNA + mtDNA tree
  • Non-clinical — exempt under Ley 14/2007 + IVDR
  • VCF + BAM — industry-standard formats

Technical contract

Input

  • Format: VCF (any modern version) or BAM (aligned reads)
  • Granularity: one sample per request
  • No patient-identifier metadata required

Output

  • Structured JSON narrative + HTML and PDF presentations
  • Languages v1.0: English and Spanish
  • SVG choropleth heatmap per subclade (adaptive granularity: administrative-level when ≥500 reference samples, country-level otherwise)
  • Non-clinical disclaimer included in every response

Deployment

  • Docker image, standard container registry
  • Single install command; verifiable with --network none (offline operation guaranteed)
  • Typical footprint: 500 MB – 1 GB image, 1–2 GB RAM, 5–30 s per sample

Library updates

  • New versioned image tags
  • Cadence controlled by your laboratory (weekly / monthly / quarterly per stability preference)
  • No silent auto-updates; you decide each version transition

Compliance

Full summary in the compliance posture. 1-page technical brief: api-module.

To start an integration conversation: acgt@genetichistory.es.