DRAGEN Pricing and Licensing

Overview

DRAGEN uses a usage-based licensing model across most pipelines and features. Usage is typically measured in gigabases (Gbases) of input from FASTQ or BAM files and is calculated per execution of DRAGEN.

If you are interested in learning more about DRAGEN pricing or are experiencing any issues - please contact usarrow-up-right.

circle-exclamation

Pipelines not metered

The following DRAGEN pipelines do not consume usage quota:

  • Germline / Somatic - CNV Only or SV Only

  • Germline - Joint Genotyping

  • BCL Convert

Platform specific Pricing and Licensing

The licensing experience differs depending on where DRAGEN is being used. Use the sections below to find the model that applies to your environment.

DRAGEN On-Premises Server

DRAGEN servers use prepaid annual licenses that are assigned to a specific DRAGEN server. As DRAGEN runs, usage is metered against the server's licensed quota.

For more information on DRAGEN Server On-Premises Licensing, refer to the DRAGEN OnPrem Server License Reference Section.

DRAGEN Cloud FPGA (BYOL) on AWS or Azure

Running DRAGEN in your own cloud environment (AWS or Azure) requires a prepaid annual license which are assigned to credentials provided to you. As DRAGEN runs, usage is metered against your credentials licensed quota.

For more information on DRAGEN Cloud Licensing, refer to the DRAGEN Cloud FPGA (BYOL) Reference Section.

Illumina Connected Analytics (ICA) and BaseSpace Sequene Hub (BSSH)

When running DRAGEN within ICA or BSSH, billing is handled automatically in those platforms. As DRAGEN runs, usage is metered as described on the ICA Pricing pagearrow-up-right.

DRAGEN onboard NovaSeqX series, MiSeq i100 Series, and NextSeq 1000/2000

DRAGEN usage on supported sequencing instruments is included with the instrument and is not metered.

Learn more at:

Frequently Asked Questions

Q: How do I see how many Gbases a run consumed?

A: Gigabase consumption per run can be found in any of the following three places;

  • .metadata.licenseInfo section of the *.metrics.json file in that runs output directory

  • *_usage.txt file in that runs output directory

  • License report in that runs stdout.

Last updated

Was this helpful?