Skip to content
The science

Anyone can predict a protein structure. The hard part is doing it for every patient, affordably, with an audit trail.

Navi8’s Personalized High-Throughput Compound Side-Effect, Interaction, Repurposing & Alternatives pipeline — PHT-CSEIRA — turns a person’s sequence and their actual medication list into a bounded, cached, provenance-complete set of GPU jobs. That is the system, and it is what we spent the last year building.

Schematic: an amino-acid sequence folds into a kinase structure whose ATP-site cleft is used for later screening
Sequence → fold → protein state. Schematic; not a live Navi8 fold, not a patient proteome.
Step one · sequence to structure

Fold what changed. Nothing else.

Your genome contains millions of variants. Only a small fraction change a protein, and only some of those sit in a protein a medication touches. Navi8’s protein service reads a VCF, computes consequence, collapses variants in the same gene into haplotype states and folds those states — with reference structures and alignments shared across every subject.

  • Non-protein-changing variants never trigger compute.
  • Multiple rows in one gene collapse to a single haplotype state.
  • Structures are keyed on sequence hash and model version — the second person with the same state is free.
Step two · structure to screen

Then ask the structure a question.

Each medication resolves to a canonical molecule and expands into a compound manifest: same-class members, repurposing candidates that bind the same target, and — where bounded — natural-product candidates. Navi8’s proprietary structure and binding-affinity engine then evaluates each compound against the patient’s protein states, in both a standard mode and a wild-type-versus-variant mode.

  • Three job families: side-effect risk rank ordering, multi-drug adverse-reaction analysis, and alternatives.
  • Every candidate carries why it exists; every structure carries what produced it.
  • Structural signal, clinical evidence and model confidence stay separable all the way to the screen.
Schematic of a ligand posed in a kinase active site, with hinge, N-lobe, C-lobe and ligand labelled
Structure-based screen schematic. Not a live Navi8 screen, not a rank, not a measured affinity.
The PHT-CSEIRA pipeline

Three service boundaries, a dependency-aware job planner, and caching at every layer.

The orchestrator owns the lifecycle, not the domain logic. Domain services produce manifests. The job manager turns manifests into an atomic, cache-keyed job graph. GPU and API tiers are decoupled, so jobs fail, retry and resume independently.

Navi8 App · Family Dashboard · Clinician Dashboard · Partner APIConsumer mobile app, household view, clinician pilot dashboard, employer reporting
POST /v1/analysesCompact request: subject · 1–10 medications · analysis intents · genomics artifact → returns an analysis id immediately
Analysis OrchestratorOwns lifecycle, not domain logic · validation · immutable analysis version + config snapshot · stage state · provenance
Drug ResolverRxNorm · PubChem · openFDA · RxClass · ChEMBL · natural-product libraries → CompoundManifest
Protein ServiceVCF → consequence → patient protein states · reference structure & alignment reuse → ProteinStateManifest
Job ManagerJob families → dependency-aware atomic job DAG · cache keys · resource classes → ExecutionPlan
Durable Job Queue / DAGAPI tier and GPU tier are decoupled — jobs fail, retry and resume independently
CPU / API WorkersProvider lookups · VCF normalization · alignment generation · interaction profiling · ranking
GPU WorkersNavi8 structure & affinity engine — standard mode and wild-type / variant comparison mode
Result & Comparison EngineWT ↔ variant · single ↔ pair · compound ↔ compound deltas
Evidence + Ranking LayerStructural signal, clinical evidence and model confidence stay separable
Measured, not quoted

Running on our own GPU cluster today.

These are not benchmarks from a paper. They were measured on Navi8’s internal cluster, and the first subject-specific protein state has been folded from sequence data on that hardware — the step everything else depends on.

  • Signed patient-haplotype fold with high structure confidence (pLDDT 0.91, pTM 0.92) on a 327-residue kinase domain.
  • Documented-pair smoke test of a known kinase–inhibitor complex reproduced with ligand interface confidence 0.97.
  • Capacity model driven by onboarding rate and analysis volume — never a static GPU count.
52×speed-up on eight GPUs versus a single CPU, measured
929structures per hour on an eight-GPU node at L = 256
0.153 MBof storage per structure, measured
81%compute-phase efficiency at eight GPUs
Discipline

What Navi8 will not say.

A structural screen is a powerful research signal. It is not a diagnosis. These rules are enforced in the product, not just the marketing.

Navi8 saysNavi8 never says
Same-class alternative — a discovery candidate for a clinician conversationA replacement for a prescribed treatment
Structural risk signal — where a compound sits on your off-target panelThe probability of an adverse event
Predicted affinity — a model estimate with a stated confidenceA measured binding constant
Natural-product candidate — bounded, screened, sourcedA natural replacement for a medication
Protein panel — the states relevant to your medicationsYour proteome
Pending evidence — when the evidence layer has not returned“No known interaction”

Want the technical walkthrough?

Clinicians, partners and investors can request the full PHT-CSEIRA architecture deck and a live demonstration.