Research · head to head
DNAnexus vs Replicate
DNAnexus
Research
Regulated cloud platform for genomic and multiomic data, with GxP and FedRAMP coverage
- From
- On request
- Rated
- -
The short version
- Only Replicate has a free tier, so it costs nothing to try first.
- 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.; Replicate private model deployments are billed for all the time instances are online, including setup and idle time, not only for processing
- They diverge on capability: DNAnexus covers Governed data storage, Replicate covers Model hosting.
- Prices and features above were last checked on 31 August 2026.
Where they differ
Only the attributes on which DNAnexus and Replicate actually diverge.
Identical on both: user rating (Not yet rated).
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 Replicate
- Model hosting
- Simple API
- Auto-scaling
- Custom models
- REST API
- Python client
- JavaScript client
- Api support
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 Replicate
- A pharma sponsor analysing genomic endpoints in a registrational programme where 21 CFR Part 11 records are requirednot Replicate
- A biobank or consortium giving hundreds of external researchers governed access to a dataset too large to distributenot Replicate
- A diagnostics vendor packaging its pipeline as a versioned app so partner laboratories can run it without receiving the source codenot Replicate
Replicate
- Running open source machine learning models through a hosted API without managing GPUsnot DNAnexus
- Deploying and serving a custom or fine tuned model on rented GPU hardwarenot DNAnexus
- Per second billed batch image, video and language model inferencenot 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.
Replicate
- Private model deployments are billed for all the time instances are online, including setup and idle time, not only for processing
- Multi-GPU A100, H100, H200 and L40S capacity beyond the listed configurations is only available with a committed spend contract
- The pricing page publishes no free tier allowance
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
Replicate
Free- Pay-as-you-go$null/usage
- Billed by execution time for public models
- CPU Small: $0.000025/second ($0.09/hour)
- 8x Nvidia A100 GPUs: $0.0112/second ($40.32/hour)
- Enterprise$null/custom
- Dedicated account manager
- Priority support
- Higher GPU limits
Which should you pick?
Choose DNAnexus if
- You need governed data storage.
- You work on Web, Linux.
- You also want workflow execution.
Choose Replicate if
- You need model hosting.
- You want to start without paying.
- You work on Api, Cloud.
- You also want simple api.
Questions people ask
- Is DNAnexus or Replicate better?
- Neither clearly leads. DNAnexus starts at On request and Replicate at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, DNAnexus or Replicate?
- Replicate has a free tier; the other does not. Paid plans start at On request for DNAnexus and Free for Replicate.
- Does DNAnexus or Replicate run on more platforms?
- DNAnexus runs on Web, Linux. Replicate runs on Api, Cloud.
- Can I use Replicate for free?
- Yes. Replicate has a free tier, so you can try it without paying. DNAnexus starts at On request.
- 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 Replicate is typically brought in for.
- What can DNAnexus do that Replicate cannot?
- DNAnexus covers Governed data storage, Workflow execution, App building, Controlled collaboration. Replicate covers Model hosting, Simple API, Auto-scaling, Custom models.
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.
Replicate: How much does Replicate cost?
Replicate uses pay-as-you-go pricing based on model execution time and compute type. Costs range from $0.09/hour for CPU (Small) to $40.32/hour for 8x Nvidia A100 GPUs. Some models charge per input/output tokens instead of time.
SourceDNAnexus: Is validated use included?
No. Regulated and validated configurations sit in a separate commercial tier from ordinary research use.
Replicate: Does Replicate offer a free tier?
Yes, Replicate is free to start with pay-as-you-go pricing. There are no subscription tiers or minimum commitments; you pay only for what you use.
SourceDNAnexus: 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.
Replicate: What is the difference between public and private models?
Public models are billed by execution time. Private models are billed for all instance uptime including setup, idle, and active processing time, except for fast-booting fine-tunes which are billed only during active processing.
SourceDNAnexus: Does it host UK Biobank?
Yes, DNAnexus hosts the UK Biobank research analysis platform, which has its own access approval and cost terms.
Related pages
Other head to heads
- DNAnexus vs Benchling
- DNAnexus vs Terra
- DNAnexus vs Seven Bridges
- DNAnexus vs Form Bio
- DNAnexus vs Labguru
- DNAnexus vs Dotmatics
- DNAnexus vs TetraScience
- DNAnexus vs Schrodinger
- DNAnexus vs LabWare
- DNAnexus vs STARLIMS
- DNAnexus vs Castor EDC
- DNAnexus vs Condens
- DNAnexus vs SurveySparrow
- DNAnexus vs Contentsquare
- DNAnexus vs LabArchives
- DNAnexus vs NVivo
- DNAnexus vs GWI
- DNAnexus vs Aurelius
- DNAnexus vs Anthropic API
- DNAnexus vs Pika
- DNAnexus vs Fathom
- DNAnexus vs D-ID
- DNAnexus vs Together AI
- DNAnexus vs RunPod
- DNAnexus vs AI21 Labs
- DNAnexus vs Lambda Labs
- DNAnexus vs Banana
- DNAnexus vs CoreWeave
- DNAnexus vs Modal
- DNAnexus vs Stable Diffusion
- DNAnexus vs Rytr
- DNAnexus vs Sourcegraph Cody
- DNAnexus vs Tabnine
- DNAnexus vs Verbit
- DNAnexus vs Adobe Firefly
- DNAnexus vs Wordtune
- Replicate vs Benchling
- Replicate vs Terra
- Replicate vs Seven Bridges
- Replicate vs Form Bio
- Replicate vs Labguru
- Replicate vs Dotmatics
- Replicate vs TetraScience
- Replicate vs Schrodinger
- Replicate vs LabWare
- Replicate vs STARLIMS
- Replicate vs Castor EDC
- Replicate vs Condens
- Replicate vs SurveySparrow
- Replicate vs Contentsquare
- Replicate vs LabArchives
- Replicate vs NVivo
- Replicate vs GWI
- Replicate vs Aurelius
- Replicate vs Anthropic API
- Replicate vs Pika
- Replicate vs Fathom
- Replicate vs D-ID
- Replicate vs Together AI
- Replicate vs RunPod
- Replicate vs AI21 Labs
- Replicate vs Lambda Labs
- Replicate vs Banana
- Replicate vs CoreWeave
- Replicate vs Modal
- Replicate vs Stable Diffusion
- Replicate vs Rytr
- Replicate vs Sourcegraph Cody
- Replicate vs Tabnine
- Replicate vs Verbit
- Replicate vs Adobe Firefly
- Replicate vs Wordtune