Softwr

Research · head to head

DNAnexus vs Florence eBinders

DNAnexus logo

DNAnexus

Research

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

From
On request
Rated
-
Full reviewWebsite
Florence eBinders logo

Florence eBinders

Research

Electronic investigator site file and eRegulatory binder for clinical research sites

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.; Florence eBinders pricing is set against how much your sponsors are expected to reimburse rather than a rate card, so two similar sites can pay materially different amounts and neither has a public benchmark to negotiate against.
  • They diverge on capability: DNAnexus covers Governed data storage, Florence eBinders covers Electronic investigator site file.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which DNAnexus and Florence eBinders actually diverge.

Attributes where DNAnexus and Florence eBinders differ
AttributeDNAnexusFlorence eBinders
PlatformsWeb, LinuxWeb

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 Florence eBinders

  • Electronic investigator site file
  • Part 11 electronic signature
  • SiteLink remote monitoring
  • eSource
  • Delegation and training logs
  • Document templates
  • Site-side ownership
  • 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 Florence eBinders
  • A pharma sponsor analysing genomic endpoints in a registrational programme where 21 CFR Part 11 records are requirednot Florence eBinders
  • A biobank or consortium giving hundreds of external researchers governed access to a dataset too large to distributenot Florence eBinders
  • A diagnostics vendor packaging its pipeline as a versioned app so partner laboratories can run it without receiving the source codenot Florence eBinders

Florence eBinders

  • An academic medical centre research office replacing physical regulatory binders across dozens of concurrent studiesnot DNAnexus
  • A site management organisation standardising delegation logs and training records across multiple locationsnot DNAnexus
  • A site under audit pressure that needs to show a complete, time-stamped document history rather than a folder of signed papernot DNAnexus
  • A research site whose sponsors keep requesting remote monitoring access and currently receive scanned documents by emailnot 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.

Florence eBinders

  • Pricing is set against how much your sponsors are expected to reimburse rather than a rate card, so two similar sites can pay materially different amounts and neither has a public benchmark to negotiate against.
  • It is site-side only: it does not do electronic data capture, study budgeting or full trial management, so a research office still runs a CTMS and an EDC alongside it and pays for the interfaces between them.
  • The benefit case depends on sponsors and monitors actually using remote access; if your sponsor mix insists on on-site source data verification, you have digitised the binder without removing the visits that made it expensive.
  • Migrating years of existing paper and scanned regulatory documents into structured, indexed binders is a substantial one-off project that sites routinely underestimate and that is scoped and charged separately.
  • Adoption is heavily United States centred, so a European or Asian site will find fewer sponsors familiar with the platform and less mature alignment with local regulatory expectations than a domestic site enjoys.

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

Florence eBinders

On request
  • Florence eBinders$undefined/year
    • Priced against study volume, site profile and expected sponsor reimbursement
    • Electronic investigator site file with Part 11 signature and audit trail
    • SiteLink sponsor and monitor remote access

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 Florence eBinders if

  • You need electronic investigator site file.
  • You also want part 11 electronic signature.
Florence eBinders review

Questions people ask

Is DNAnexus or Florence eBinders better?
Neither clearly leads. DNAnexus starts at On request and Florence eBinders at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, DNAnexus or Florence eBinders?
DNAnexus starts at On request and Florence eBinders at On request.
Does DNAnexus or Florence eBinders run on more platforms?
DNAnexus runs on Web, Linux. Florence eBinders runs on Web.
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 Florence eBinders is typically brought in for.
What can DNAnexus do that Florence eBinders cannot?
DNAnexus covers Governed data storage, Workflow execution, App building, Controlled collaboration. Florence eBinders covers Electronic investigator site file, Part 11 electronic signature, SiteLink remote monitoring, eSource.

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.

Florence eBinders: Is this an EDC system?

No. It manages the site regulatory binder and source documents. Trial data capture is a separate system such as Medidata, Castor or REDCap.

DNAnexus: Is validated use included?

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

Florence eBinders: Who normally pays for it?

The site buys it, but sites commonly recover the cost through per-study sponsor budgets, and Florence prices with that expected reimbursement in mind.

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.

Florence eBinders: Does it support 21 CFR Part 11?

Yes, with electronic signatures, audit trails and access controls. Validation for your intended use is still your responsibility.

DNAnexus: Does it host UK Biobank?

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

Florence eBinders: Can sponsors see our documents?

Only what you grant through SiteLink. Documents stay under site control rather than in a sponsor-owned repository.

Share

Related pages

More on DNAnexus

More on Florence eBinders

Keep looking

Other head to heads