Softwr

Research · head to head

DNAnexus vs STARLIMS

DNAnexus logo

DNAnexus

Research

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

From
On request
Rated
-
Full reviewWebsite
STARLIMS logo

STARLIMS

Research

Laboratory information management from Abbott for regulated and public health 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.; STARLIMS implementation is lengthy and outcome quality depends heavily on the partner doing the configuration
  • They diverge on capability: DNAnexus covers Governed data storage, STARLIMS covers Sample and specimen management.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which DNAnexus and STARLIMS actually diverge.

Attributes where DNAnexus and STARLIMS differ
AttributeDNAnexusSTARLIMS
PlatformsWeb, LinuxWeb, Windows, 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 STARLIMS

  • Sample and specimen management
  • Quality management
  • Instrument integration
  • Public health reporting
  • Regulatory compliance
  • Web and mobile access

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 STARLIMS
  • A pharma sponsor analysing genomic endpoints in a registrational programme where 21 CFR Part 11 records are requirednot STARLIMS
  • A biobank or consortium giving hundreds of external researchers governed access to a dataset too large to distributenot STARLIMS
  • A diagnostics vendor packaging its pipeline as a versioned app so partner laboratories can run it without receiving the source codenot STARLIMS

STARLIMS

  • Public health laboratories handling surveillance and outbreak investigationnot DNAnexus
  • Clinical laboratories needing regulated specimen tracking and reportingnot DNAnexus
  • Food safety and environmental testing laboratoriesnot DNAnexus
  • Multi-site laboratory networks standardising methods and specificationsnot 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.

STARLIMS

  • Implementation is lengthy and outcome quality depends heavily on the partner doing the configuration
  • Pricing is quote-based with no public reference, making early budget setting difficult
  • The breadth across laboratory types means some verticals get less development attention than others
  • Interface modernisation has lagged behind newer cloud-native laboratory platforms
  • Over-specified for small laboratories, where a lighter LIMS delivers most of the value for a fraction of the effort

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

STARLIMS

On request
  • STARLIMS$undefined/year
    • Sample management
    • Quality management
    • Instrument integration

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 STARLIMS if

  • You need sample and specimen management.
  • You work on Web, Windows, Cloud, On-premise.
  • You also want quality management.
STARLIMS review

Questions people ask

Is DNAnexus or STARLIMS better?
Neither clearly leads. DNAnexus starts at On request and STARLIMS at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, DNAnexus or STARLIMS?
DNAnexus starts at On request and STARLIMS at On request.
Does DNAnexus or STARLIMS run on more platforms?
DNAnexus runs on Web, Linux. STARLIMS runs on Web, Windows, 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 STARLIMS is typically brought in for.
What can DNAnexus do that STARLIMS cannot?
DNAnexus covers Governed data storage, Workflow execution, App building, Controlled collaboration. STARLIMS covers Sample and specimen management, Quality management, Instrument integration, Public health reporting.

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.

STARLIMS: Who owns STARLIMS?

Abbott. That gives it institutional weight in laboratory procurement and a natural relationship with Abbott diagnostic instruments.

DNAnexus: Is validated use included?

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

STARLIMS: Where is it strongest?

Public health and clinical laboratories. Surveillance reporting, outbreak investigation and unpredictable specimen surges are different problems from pharmaceutical QC, and it handles them well.

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.

STARLIMS: What does it cost?

Not published. Enterprise licensing plus implementation, quoted on laboratory count, users and modules.

DNAnexus: Does it host UK Biobank?

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

STARLIMS: How does it compare to LabWare?

Both are enterprise LIMS with regulatory depth. LabWare is more dominant in pharmaceutical QC; STARLIMS has more presence in public health and clinical. Implementation partner quality matters more than the platform difference.

STARLIMS: What decides a successful implementation?

Configuration and validation quality, not platform features. Evaluations that compare feature lists rather than implementation approach are asking the wrong question.

Share

Related pages

More on DNAnexus

More on STARLIMS

Keep looking

Other head to heads