Skip to content

Stop prepping each omics layer on a different instrument.

One 96-well platform for chromatin, DNA, RNA, and protein. Same prep for every layer — so your integration model learns biology, not batch effects.

Built for the study you're actually integrating.

Four matched-sample study patterns where one prep platform replaces three — and your integration model sees biology instead of instrument noise.

Matched-sample multi-omics

Chromatin, RNA, and protein from one biological sample

The same specimen goes to ChIP-seq, RNA-seq, and proteomics — three instruments, three protocols, three operators. Your integration model can't tell biology from the batch effect that introduces.

Column-level programming runs chromatin shearing, RNA fragmentation, and protein extraction on a single 96-well plate, one run. The matched sample stays matched — harmonized at the source, before any chemistry.

Archival multi-omics

Matched FFPE and frozen tissue, every omics layer

Archival blocks and frozen specimens run on separate prep tracks — and block-age variability stacks on top of cross-platform noise before integration even starts.

One platform processes matched FFPE and frozen tissue across chromatin, DNA, RNA, and protein. MultiomicsTracks96 (2024) is the published reference workflow — 8-dimensional omics from matched archival and frozen samples.

Consortium standardization

Cross-site matched-sample studies

A multi-site consortium study integrates only as well as its least-harmonized site. Every member lab running a different prep platform builds cross-site batch effects into the shared dataset.

One sample-prep platform, one parameter framework, every site. Run logs and processing parameters export for FAIR-compliant data sharing — the documentation trail NIH Data Management & Sharing submissions expect.

Longitudinal cohorts

Multi-year cohorts, one constant prep layer

Over a five-year cohort, your downstream mass spec and sequencer will be upgraded. Every instrument change introduces a batch effect that threatens the longitudinal interpretability of the whole study.

PIXUL stays constant as the upstream sample-prep layer while downstream platforms evolve. Parameter-locked runs documented in run logs — a longitudinal anchor that holds the cohort together across instrument generations.

Your integration model finds the strongest signal in the data. Prep each omics layer on a different instrument — and the strongest signal becomes the instruments, not the biology.

One instrument. Every omics. Harmonized at the source.

One instrument, every omics
1 plate
chromatin, DNA, RNA, protein — one run

Column-level programming runs different applications in different columns of the same plate — chromatin in one, RNA in the next, protein in the next. Different programs, same run. The architecture is built for three-on-one-plate multi-omics.

Harmonized at the source
Zero
cross-platform prep batch effects

Every omics layer prepped on the same instrument, the same parameter framework. The cross-platform batch effect that integration models can't recover from never enters the data — because the matched sample is harmonized before any chemistry happens.

Consortium-ready
FAIR-ready
run logs + open-format plates

Run logs and processing parameters export for FAIR-compliant data sharing and NIH Data Management & Sharing submissions. Standard polystyrene plates — non-proprietary labware, no cost that climbs as cohorts scale.

Where PIXUL stands alone.

Fragment-size consistency across 96 wells

307 ± 35 bp
Two transducers per column at 2 MHz — no plate-edge effects

Bomsztyk et al., Nucleic Acids Research, 2019. The architecture paper — uniform acoustic energy, the same parameter framework for every application.

Read paper

Validated across every omics layer

2019–2026 peer-reviewed
Proteomics · genomics · epigenomics · multi-omics

Every omics layer PIXUL prepares — chromatin, DNA, RNA, and protein — validated in peer-reviewed publications across application areas. The breadth is the multi-omics proof.

Browse publications

Questions multi-omics labs ask before they evaluate.

Application-specific instruments are best-in-class for each omics layer. Why one platform?
Application-specific instruments optimize for one job, and they are genuinely strong at it. But matched-sample multi-omics integration is one big job, not three small jobs. When chromatin, RNA, and protein from the same specimen run on three instruments, the integration model cannot separate biology from the cross-instrument batch effect — especially in the case where an experimental group and its control end up on different instruments. Per-application precision is the right frame when each application stands alone; it is the wrong frame when harmonization across applications is the goal. Most multi-omics labs keep an application-specific tool for the rare maximum-precision job and route matched-sample studies through PIXUL.
Doesn't a trapping-cartridge cleanup already solve harmonization?
A trapping-cartridge cleanup is excellent extraction chemistry, and it is complementary to PIXUL, not competing with it. It operates downstream of physical disruption: cells still have to be lysed, chromatin sheared, and DNA fragmented before any extraction chemistry happens. PIXUL is that upstream physical-disruption step, harmonized across all four omics layers. Many labs run PIXUL upstream of the cartridge — PIXUL handles the matched-sample disruption, the cartridge handles the proteomics extraction. The harmonization the cartridge delivers at the chemistry layer, PIXUL delivers at the disruption layer; together they cover the whole prep.
Does column-level programming actually work for different applications at once?
Column-level programming means each column of the 96-well plate can run a different application program — chromatin shearing in one set of columns, RNA fragmentation in the next, protein extraction in the next — in the same run. It is not a gimmick; it is the core architecture. PIXUL's inventor lab ran three omics applications on a single plate as a routine experiment. MultiomicsTracks96 (2024) is the published reference workflow demonstrating the pattern across matched samples.
What about cross-day variability, not just within-plate CV?
A fair question, and the honest answer has two parts. Within a plate, PIXUL's two-transducers-per-column architecture delivers uniform acoustic energy with sub-10% CV — no plate-edge effects. Across days, no sample-prep instrument eliminates temporal drift on its own. What PIXUL eliminates is the cross-platform axis — the batch effect from running different omics layers on different instruments. The cross-day axis is managed by cohort design: randomize experimental groups across plates and runs so that no group is confounded with a single day or plate. We provide a cohort-planning template for exactly this.
Switching from our per-application instruments means re-validating every pipeline. Is it worth it?
Re-validation is a real cost, and it is why PIXUL is the strongest fit for labs where matched-sample multi-omics is a clean-slate problem — a new U-series grant, a consortium new-site lab, or a biopharma multi-omics team without legacy published methodology. For a lab with a deeply published per-application pipeline, the honest answer is to adopt PIXUL on the next study, not the current one. The published pipeline stays valid; the next matched-sample cohort starts harmonized.
We'd be the only consortium site running PIXUL. Why adopt a non-default platform?
Consortium platform choices are path-dependent — the first instrument in tends to propagate. PIXUL's run logs and processing parameters export for FAIR-compliant data sharing, which is what cross-site integration actually requires: not that every site runs the field-default instrument, but that every site's prep is documented and harmonized. A consortium standardizing on PIXUL gets cross-site reproducibility plus the NIH Data Management & Sharing documentation trail. The question is not whether PIXUL is the default — it is whether the platform makes multi-site data integrable.

Skip the brochure tour.
Talk to a PIXUL specialist.

A 30-minute working call with the multi-omics applications team. Bring a matched-sample set — FFPE, frozen, cells — and see column-level programming run every omics layer on one plate, plus a walk-through of run-log export for FAIR-data submission.

Speak to a specialist