Skip to content

info@23rdpairlab.com +44 7920 423953

23rd Pair Lab Limited

Bioinformatics · Pipelines · Software · Sequencing kits

WE READ ALL 23 PAIRS

Bioinformatics data analysis, end-to-end pipeline development, proprietary analysis software and targeted sequencing solutions.

Illustrative XY human karyotype — 22 autosomal pairs plus the sex chromosomes

What we do

Four ways we work with sequencing data

Analysis run for you, pipelines built for your team to own, software you can license, and targeted kits we developed ourselves.

We run the analysis

Bioinformatics data analysis

Whole genome, exome, RNA-seq, targeted panels, metagenomics, multi-omics and long-read data, analysed with the QC and methods written down.

Explore analysis

You own the workflow

Pipeline development

Reproducible, automated, documented workflows designed around your data and handed over with the code and configuration.

Discuss a pipeline

You run the tools

Bioinformatics software

23rdExon, CAN and MetaXplore — three independent analysis tools we build and use, licensed for your own team.

Explore software

Targeted long-read

NanoAmp™ kits

Proprietary targeted amplification kits for high-resolution genomic analysis on Oxford Nanopore sequencing. For research use only.

Explore NanoAmp™

Who we work with

Teams with sequencing data and a question to answer

  • Research groups Academic and institutional teams with sequencing data to analyse.
  • Biotechnology companies R&D teams needing analysis capacity or a pipeline of their own.
  • Laboratories Labs adding long-read or targeted sequencing analysis to existing work.
  • Life-science teams Groups who need the analysis explained, not just delivered.
  • Company UK-registered, no. 15728861
  • Software Three proprietary analysis tools
  • Technology Proprietary NanoAmp™ assays
  • Handover Files and configuration included

How we think about it

A result you cannot check is not a result.

Every analysis we deliver comes with the pipeline version, the reference build, the quality metrics and the filtering logic that produced it. If a reviewer or a sceptical colleague asks how a variant call was made, the answer is in the report rather than in someone's memory.

  • Pipeline version and reference build recorded on every run
  • Quality metrics reported before conclusions, not after
  • Raw and intermediate files handed over, not withheld
  • A named analyst you can email with a question

How a project runs

Five stages, in this order

The numbering here is real: each stage depends on the one before it, and we will tell you if a sample or a dataset fails at any of them.

  1. Scope the question

    What are you trying to find out, what will you do with the answer, and is sequencing the right way to get it? Sometimes it is not, and we say so.

  2. Sample or data intake

    Samples or existing FASTQ/BAM files arrive, get logged against your project, and are checked for the things that quietly ruin an analysis later.

  3. Quality control

    Coverage, duplication, contamination, sex checks, batch effects. You see the QC before we go further, so a weak dataset never becomes a confident claim.

  4. Analysis and interpretation

    Alignment, calling and annotation against the pipeline agreed at scoping, then human interpretation against the current literature and databases.

  5. Report and handover

    A written report, the underlying files, and a call to walk through both. Follow-up questions after delivery are part of the job, not an extra.

Tell us what you are trying to find out.

Send the question rather than the specification. If we are not the right lab for it, we would rather say that early and point you somewhere better.