Softwr

Research · head to head

DNAnexus vs LabWare

DNAnexus logo

DNAnexus

Research

Regulated cloud platform for genomic and multiomic data, with GxP and FedRAMP coverage

From
On request
Rated
-
Full reviewWebsite
LabWare logo

LabWare

Research

Enterprise laboratory information management system for regulated labs

From
On request
Rated
-
Full reviewWebsite

The short version

  • Each has a real cost: DNAnexus no pricing is published, so an organisation cannot compare the total cost against running the same pipelines on its own cloud account until it is deep in a sales process.; LabWare implementation and validation take a year or more, and the services cost frequently exceeds the licence
  • They diverge on capability: DNAnexus covers Governed data storage, LabWare covers Sample management.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which DNAnexus and LabWare actually diverge.

Attributes where DNAnexus and LabWare differ
AttributeDNAnexusLabWare
PlatformsWeb, LinuxWindows, Web, Cloud, On-premise

Identical on both: starting price (On request), pricing model (quote), free tier (No), user rating (Not yet rated), category (Research).

What each one covers

Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in DNAnexus

  • Governed data storage
  • Workflow execution
  • App building
  • Controlled collaboration
  • Compliance posture
  • Cohort browsing

Only in LabWare

  • Sample management
  • Instrument integration
  • Regulatory compliance
  • Stability studies
  • ELN
  • Configuration framework

What people use each for

The jobs each tool is most often brought in to do.

DNAnexus

  • A clinical diagnostics laboratory that needs a CLIA and CAP aligned environment for production sequencing pipelines without building the compliance evidence itselfnot LabWare
  • A pharma sponsor analysing genomic endpoints in a registrational programme where 21 CFR Part 11 records are requirednot LabWare
  • A biobank or consortium giving hundreds of external researchers governed access to a dataset too large to distributenot LabWare
  • A diagnostics vendor packaging its pipeline as a versioned app so partner laboratories can run it without receiving the source codenot LabWare

LabWare

  • Pharmaceutical quality control laboratories subject to regulatory inspectionnot DNAnexus
  • Multi-site laboratory networks needing one method and specification librarynot DNAnexus
  • Contract laboratories managing chain of custody across many clientsnot DNAnexus
  • Laboratories replacing a validated legacy LIMS they can no longer maintainnot DNAnexus

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

DNAnexus

  • No pricing is published, so an organisation cannot compare the total cost against running the same pipelines on its own cloud account until it is deep in a sales process.
  • Compute and storage are billed through the platform rather than at underlying cloud list price, so the compliance envelope carries a persistent margin on every terabyte and core hour, which grows with the science rather than staying fixed.
  • Data egress at genomic scale is slow and chargeable, so leaving the platform later is a real project rather than a contract decision, and that gravity weakens negotiating position at renewal.
  • The regulated and validated configurations sit in a higher commercial tier than the research configuration, so an organisation that starts in research mode and later needs GxP faces a repricing rather than a setting change.
  • Bioinformaticians used to running Nextflow on their own infrastructure find the platform abstractions constraining, and porting an existing pipeline into the app model is engineering work that does not carry over to any other platform.

LabWare

  • Implementation and validation take a year or more, and the services cost frequently exceeds the licence
  • Pricing is entirely quote-based with no public reference point, even by enterprise standards
  • Extensive configuration means the finished system depends heavily on implementation quality, and outcomes vary widely between customers
  • The interface is functional rather than modern, which is a common objection from scientists used to consumer software
  • Substantially over-specified for research laboratories without regulatory obligations

Pricing, plan by plan

DNAnexus

On request
  • DNAnexus Platform$undefined/year
    • Quoted per organisation through a sales process
    • Storage and compute billed through the platform rather than at cloud list price
    • Regulated and validated configurations are a separate commercial tier

LabWare

On request
  • LabWare LIMS$undefined/year
    • Sample management
    • Instrument integration
    • Regulatory compliance

Which should you pick?

Choose DNAnexus if

  • You need governed data storage.
  • You work on Web, Linux.
  • You also want workflow execution.
DNAnexus review

Choose LabWare if

  • You need sample management.
  • You work on Windows, Web, Cloud, On-premise.
  • You also want instrument integration.
LabWare review

Questions people ask

Is DNAnexus or LabWare better?
Neither clearly leads. DNAnexus starts at On request and LabWare at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, DNAnexus or LabWare?
DNAnexus starts at On request and LabWare at On request.
Does DNAnexus or LabWare run on more platforms?
DNAnexus runs on Web, Linux. LabWare runs on Windows, Web, Cloud, On-premise.
What is DNAnexus best used for?
DNAnexus is most often used for a clinical diagnostics laboratory that needs a clia and cap aligned environment for production sequencing pipelines without building the compliance evidence itself, a pharma sponsor analysing genomic endpoints in a registrational programme where 21 cfr part 11 records are required, a biobank or consortium giving hundreds of external researchers governed access to a dataset too large to distribute, a diagnostics vendor packaging its pipeline as a versioned app so partner laboratories can run it without receiving the source code. Of those, a clinical diagnostics laboratory that needs a clia and cap aligned environment for production sequencing pipelines without building the compliance evidence itself and a pharma sponsor analysing genomic endpoints in a registrational programme where 21 cfr part 11 records are required are not what LabWare is typically brought in for.
What can DNAnexus do that LabWare cannot?
DNAnexus covers Governed data storage, Workflow execution, App building, Controlled collaboration. LabWare covers Sample management, Instrument integration, Regulatory compliance, Stability studies.

Answered from the vendors’ own pages

DNAnexus: Why pay for DNAnexus instead of raw AWS?

For the compliance evidence. GxP, FedRAMP, CLIA, CAP and Part 11 coverage removes a validation programme most organisations would otherwise have to build and maintain themselves.

LabWare: Why is LabWare so dominant in pharma?

Validation experience. In a regulated laboratory the software forms part of what an inspector examines, and decades of accumulated validation practice is not something a newer vendor can substitute for.

DNAnexus: Is validated use included?

No. Regulated and validated configurations sit in a separate commercial tier from ordinary research use.

LabWare: What does it cost?

Not published. Enterprise licensing plus implementation and validation services, and the services frequently exceed the licence.

DNAnexus: Can I get my data out?

Yes, but egress at genomic scale is chargeable and slow, so plan exit costs at the point of signing.

LabWare: How long is implementation?

A year or more for a regulated laboratory, including validation. Anyone quoting substantially less is either scoping narrowly or omitting validation.

DNAnexus: Does it host UK Biobank?

Yes, DNAnexus hosts the UK Biobank research analysis platform, which has its own access approval and cost terms.

LabWare: Does it include an electronic laboratory notebook?

Yes, LabWare offers ELN alongside LIMS on the same platform, which avoids the integration problem of running two vendors.

LabWare: Is it suitable for a research lab?

Usually not. Research laboratories without regulatory obligations pay for compliance machinery they do not need, and Benchling or a lighter LIMS fits better.

Share

Related pages

More on DNAnexus

More on LabWare

Keep looking

Other head to heads