Softwr

Research · head to head

DNAnexus vs Scispot

DNAnexus logo

DNAnexus

Research

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

From
On request
Rated
-
Scispot logo

Scispot

Research

No-code lab operating system combining LIMS, ELN and inventory for biotech teams

From
On request
Rated
-

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.; Scispot pricing is presented as four dollar sign bands with no figures, so a vendor whose marketing attacks competitor pricing opacity requires a discovery call before telling you its own numbers.
  • They diverge on capability: DNAnexus covers Governed data storage, Scispot covers No-code configuration.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which DNAnexus and Scispot actually diverge.

Attributes where DNAnexus and Scispot differ
AttributeDNAnexusScispot
PlatformsWeb, LinuxWeb, API

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 Scispot

  • No-code configuration
  • LIMS and ELN together
  • Inventory management
  • Instrument integration
  • Audit trails and e-signatures
  • API and data layer
  • Validation support
  • Integrations

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

Scispot

  • A Series A biotech replacing a folder of spreadsheets before a partner or investor audit exposes the gapnot DNAnexus
  • A diagnostics company that needs sample chain of custody and electronic signatures without a year-long LIMS implementationnot DNAnexus
  • A contract research organisation configuring different workflows per client without buying a separate instance each timenot DNAnexus
  • A computational team that wants laboratory data queryable through an API rather than exported by handnot 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.

Scispot

  • Pricing is presented as four dollar sign bands with no figures, so a vendor whose marketing attacks competitor pricing opacity requires a discovery call before telling you its own numbers.
  • Compliance capability is bundled into tier scope rather than itemised, which makes it hard to tell at purchase whether the tier you are quoted actually covers the Part 11 controls your auditor will ask for.
  • Validation remains your responsibility: the vendor supplies support and correctly states that no platform makes a lab compliant, but the documentation effort and its cost sit with your quality function.
  • It is a young and small vendor holding your primary scientific record, so business continuity, data escrow and full export guarantees need to be settled contractually rather than assumed.
  • Instrument integration breadth is narrower than the established LIMS vendors, so labs with older or unusual analysers may need custom connector work that undercuts the no-code promise.

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

Scispot

On request
  • Scispot$undefined/year
    • Custom annual pricing released after a discovery call
    • Four relative investment tiers shown only as dollar sign bands
    • Mid tier adds roles, e-signatures, approvals, audit trails and validation support

Which should you pick?

Choose DNAnexus if

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

Choose Scispot if

  • You need no-code configuration.
  • You work on Web, API.
  • You also want lims and eln together.

Questions people ask

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

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.

Scispot: How much does Scispot cost?

It does not publish figures. The pricing page shows four relative investment tiers as dollar sign bands, with real numbers given after a discovery call.

DNAnexus: Is validated use included?

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

Scispot: Does it support 21 CFR Part 11?

It can be configured for Part 11 controlled workflows with roles, e-signatures, approvals and audit trails from the mid tier, and it supports ALCOA+ principles. Validation of your configuration is still your responsibility.

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.

Scispot: Is it a LIMS or an ELN?

Both, plus inventory, in one subscription rather than separately licensed products.

DNAnexus: Does it host UK Biobank?

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

Scispot: Who is it not for?

Large regulated manufacturers with existing validated LIMS estates, and any lab that needs deep integration with an unusual analyser fleet.

Share

Related pages

Other head to heads