Engineering infrastructure for next-generation information storage and computing.
We build software for storing information in DNA and verify it in public.
What VSNexus is
VS Nexus Technologies is a software-first deep-technology company. Our first product, VNX-DNA, implements the digital side of DNA data storage: everything that happens before a sequence is synthesised and after a sequencer returns reads.
We work in the open. The code, the specification, the experiment designs and their results files are public, and every number on this site links to the file it came from. Where a result comes from simulation or from another group's public data, we say so.
The flagship codebase. Version, status and links below are managed as structured data and reused across the site.
VNX-DNA
Computational infrastructure for DNA data storage: archive, encryption, constrained encoding, error correction, simulated channels, consensus and verified decoding.
Architecture, as implemented
The encode stages E0–E15 and decode stages D0–D14 are specified in the VNX-DNA specification (§5) and implemented as two orchestrators in vnxdna.pipeline. The channel in the middle is software: it simulates synthesis, storage, amplification and sequencing errors. No stage touches physical DNA.
- E0–E6
Archive and container
Collect, chunk, identify (SHA-256 or HMAC), deduplicate, compress (zstd, kept only if smaller), seal with AES-256-GCM, write the .vnx container with a canonical manifest and Merkle root.
Implemented - E7–E9
Outer code
Plan geometry; Cauchy Reed-Solomon rows, optional column parity over stripes; superblock.
Implemented - E10–E11
Framing and inner code
Frame = address + payload + CRC-32; scramble; inner Reed-Solomon.
Implemented - E12–E14
DNA mapping and screening
2-bit mapping with in-strand sync markers; GC, homopolymer, repeat and motif screening with up to 256 scrambler variants; ordered strand file.
Implemented - E15
Laboratory export package
vnx.export-package/1 for a synthesis order. Never executed by a laboratory.
Specified only - SIM
Simulated channel
Strand loss, coverage, synthesis / storage / amplification / sequencing stages, bursts, reverse complements; 14 shipped channel models, none fitted to a validated platform.
Simulated - D0–D4
Read ingest and alignment
Parse reads (native parser), probe frame version and layout, orient, marker-template alignment that turns indels into erasures.
Implemented - D5–D7
Inner decoding
Inner Reed-Solomon + CRC acceptance (native AVX2 / AVX-512BW). Opt-in: smart indel recovery, soft-decision decoding, retry band.
Implemented - D8–D11
Outer recovery
Superblock selection, consensus per address, outer erasure decoding, stripe (column) decoding.
Implemented - V7–V9
Cluster pass
When outer rows still lack symbols, a second pass clusters the reads and builds indel-aware full-template consensus (native polish kernel since V9; candidate E is opt-in), then feeds the outer decoder again.
Implemented - D12–D14
Verify and publish
Verify against the superblock SHA-256 and Merkle root; atomic publish of SUCCESS, or PARTIAL with only individually verified files; otherwise write nothing.
Implemented
Files go in on the left and come back out, verified, on the right. Choose a part to focus on it.
Engineering evidence
Selected V9 results. Each item names its classification and the committed file it comes from; the benchmark pages give methodology and limitations.
A defensive control plane merged into VNX-DNA at V9.
VNX-Secure
Defensive control plane for VNX-DNA: deny-by-default policy, deterministic detectors, HMAC-chained audit, integrity snapshots, recovery and a safe attack simulator.
Technology ecosystem
Every project carries its real maturity. Only VNX-DNA and VNX-Secure (above) contain shipped code; the rest are research or concepts.
VNX-RAM
Research concept for a molecular-memory subsystem. No hardware exists; only a software security contract and its in-process reference implementation.
VNX-IO
Concept: data ingest and export infrastructure around VNX archives. No code exists.
VNX-Cache
Concept: caching tier for decoded archive content. No code exists.
VNX-LoadBalancer
Concept: distribution of encode and decode workloads across machines. No code exists.
VNX-Fallback
Concept: recovery infrastructure across storage tiers. No code exists. (Within VNX-DNA, fail-closed decoding and PARTIAL recovery are implemented.)
Crash & Error Handling
Concept: shared crash and error-handling infrastructure. No separate code exists; VNX-DNA has typed errors with stable exit codes.
Research
Pre-registered, reproducible computational studies — including negative results.
V9: consensus V2 and adaptive computational coverage
Five pre-registered hypotheses on decoding under a nanopore-like stress channel: a native consensus kernel, the oracle gap, a better consensus (candidate E), adaptive coverage, and a latent-class channel model. Four accepted, one rejected.
Simulated 2026-10-08V7: indel-aware consensus at low coverage
Full-template consensus confirmed on fresh pre-registered seeds; a low-coverage parity profile reaches 5-read coverage at +42 % strands; below 5 reads the architecture was not sufficient.
Simulated 2026-10-07V8: fitting a nanopore channel model to public data
A channel model fitted to the public D13 nanopore dataset reproduces per-base rates and indel run lengths but fails read-level structure tests. Reported as INADEQUATE; held-out data never opened.
Public data 2026-10-07
Collaboration
The next step for VNX-DNA is evidence we cannot produce alone.
Physical validation
Synthesise and sequence VNX-DNA strands, and test decoding on real reads.
wet labBenchmark replication
Re-run our published experiments on your hardware and report the differences.
computationalChannel-model research
Help build a sequencing error model that passes our pre-registered adequacy tests.
research
09 — For investors
Stage, roadmap and the commercial paths we consider, stated without projections we cannot support.