> For the complete documentation index, see [llms.txt](https://help.dragen.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.dragen.illumina.com/dragen-v4.6/reference/licensing/moving-to-dragen-pricing.md).

# Moving to DRAGEN Pricing

## Overview

DRAGEN Pricing applies to DRAGEN v4.6 and later runs licensed through Illumina BioInsight Platform. Every other run uses Legacy Gigabase Pricing. This page describes when DRAGEN Pricing starts for your organization and what to do for deployments that stay on Legacy Gigabase Pricing.

* For rates, tiers, sample classification, and standalone tools, see [BioInsight Platform pricing](https://www.illumina.com/products/by-type/informatics-products/bioinsight-platform/pricing/pricing-details.html).
* For the pricing model that applies to each deployment and DRAGEN version, see [Licensing by deployment](/dragen-v4.6/reference/licensing.md#licensing-by-deployment).

{% hint style="info" %}
Nothing changes for current customers automatically, and accounts are not converted.
{% endhint %}

## When DRAGEN Pricing starts

DRAGEN Pricing starts with your first run that meets both conditions: the run uses DRAGEN v4.6 or later, and it is licensed through BioInsight Platform. Pricing is determined per run, not per account. Runs under both models can coexist in the same organization, so you can move one workflow at a time.

Existing agreements, including multi-year per-gigabase contracts, negotiated rates, and custom commercial terms, continue unchanged to the end of their term. If you have questions, contact your Informatics Sales Specialist or account manager.

## Deployments on Legacy Gigabase Pricing

### Public-cloud BYOL with legacy license credentials

{% hint style="warning" %}
Legacy prepaid gigabase licenses for public-cloud BYOL (levels 1 to 5) can be purchased and renewed until March 31, 2027. No new prepaid public-cloud BYOL licenses are sold after that date.
{% endhint %}

Licenses purchased on or before March 31, 2027 keep their remaining quota and rate for the negotiated license period. Unused quota expires when that period ends.

To continue running DRAGEN on public cloud, choose one of the following:

* **Pre-purchase prepaid licenses** under Legacy Gigabase Pricing until March 31, 2027. Your licensing setup does not change. See [Legacy DRAGEN Cloud Licensing](/dragen-v4.6/reference/licensing/cloud_licensing.md).
* **License with a Platform API key** and run DRAGEN v4.6 or later under DRAGEN Pricing, in DRAGEN FPGA Mode on AWS or in DRAGEN Software Mode on standard cloud instances. Usage draws on your BIC balance, with no prepayment and no platform access fee. See [Set up API key licensing](/dragen-v4.6/reference/licensing/api_key_licensing.md#set-up-api-key-licensing).

### DRAGEN Server

DRAGEN Server licenses stay on Legacy Gigabase Pricing, including on DRAGEN v4.6. See [DRAGEN Server Licensing](/dragen-v4.6/reference/licensing/onprem_licensing.md). BioInsight Platform licensing for DRAGEN Server will become available in 2027.

## Before you move a workflow to DRAGEN v4.6

1. Find your deployment in [Licensing by deployment](/dragen-v4.6/reference/licensing.md#licensing-by-deployment) to confirm which pricing model applies.
2. If you will license DRAGEN on your own infrastructure, confirm that your domain and API key meet the [Illumina BioInsight Platform requirements](/dragen-v4.6/reference/licensing/api_key_licensing.md#illumina-bioinsight-platform-requirements), and that every node can reach the DRAGEN license server.
3. If you hold a legacy prepaid gigabase license for public-cloud BYOL (levels 1 to 5), confirm your negotiated license period, and decide by March 31, 2027 whether to pre-purchase quota or license with a Platform API key.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.dragen.illumina.com/dragen-v4.6/reference/licensing/moving-to-dragen-pricing.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.