If you never got the point of GATK Lite and you hated the 2.0 license... Oh, do we have good news for you!
First, a little bit of context. When we released GATK 2.0, the GATK had emerged as the leading research software package in its domain. Public demand for tech support was rising rapidly; not only from the academic research community as it had in the past, but also from researchers using the software in a for-profit context. These latter users have specific needs (quality assurance, process certifications, etc.) that we are ill-equipped to address.
This drove us to seek a partnership with a company called Appistry which could release and license the GATK as a commercial software product appropriate for use in a for-profit and regulatory-compliant setting. We knew this solution would better meet customer needs, while alleviating our support burden and allowing us to focus on our core constituency, the academic and non-profit research community. This plan also had the prospective benefit of leveraging the intellectual property of the GATK (much of which results more or less directly from public investments) to fund the continuation of our research and development activities.
However we knew it would take us and our partners at Appistry some time to develop a mature commercial product. So as an interim solution, we enacted a more restrictive license, closed part of the source code on the “Full GATK” release, and provided a “Lite” version to enable for-profit users to keep working with an up-to-date version of the GATK (albeit without the cutting-edge tools that were introduced in version 2.0). Of course, the GATK programming framework (the GATK engine, libraries, and basic data management tools) continued to remain open source under the MIT license.
Well, we got a lot of feedback from the user community over these changes. We listened carefully, took the criticism to heart, and realized our interim solution left much to be desired. First, closing part of the source code was a deeply unpopular move. Many of you pointed out that this might restrict academic knowledge and obstruct progress in the field of algorithmic research. Second, we did a poor job of communicating the purpose of Lite and how it differed from the Full version. Even though Lite was always intended as an interim solution, some organizations opted to adopt it instead of the Full version and seem to view it as a viable long-term solution for genetic analysis. Related to this, we found that maintaining the two different distributions gave us our share of headaches in terms of supporting and updating the toolkit.
In light of these considerations, we’re going to change things up again, hopefully for the better!
In a nutshell: no more Lite and a new license (attached) that restores free access to the source code for those in the community performing academic non-commercial research. That’s right, free as in beer! You’ll still have the option of downloading the packaged binary (i.e., the “ready-to-run” program) from our website as you did before, but you’ll also be able to get the full source code (programming framework AND all tools including the latest and greatest) straight from the Github repository if you want. You can set it up on a server and provide it as a service to other non-profit users within your organization. You can dig into our deepest secrets to find out what makes ReduceReads and the HaplotypeCaller tick. And feel free to send us patches if you find a way to improve the code!
Licensed users through Appistry, in addition to having access to the full GATK and the added benefits of a fully-fledged commercial solution (less buggy, more help-y), may optionally purchase access to the source code. Appistry has been fine-tuning its process for providing the commercial product (including enterprise-grade QA, which we don’t do) as well as training a professional support team. If your use of GATK requires a commercial license, we encourage you to reach out to them. Appistry will be able to handle any questions you may have about the commercial release schedule, available support, and of course, licensing and pricing terms (whether for individual or site-wide licenses, companies big and small).
The following figure summarizes the different packages and their corresponding licenses.
Note that if you are using a version of GATK-Lite, you may continue using it, but we will be making no more updates to Lite after 2.3. Thus, if you choose to stay with Lite, you will be using an outdated version of the toolkit and you won’t benefit from any further improvements made to the GATK with the 2.4 release and in the future.
We welcome any and all comments on these new changes, which are due to take effect with the upcoming release of version 2.4 (tentatively scheduled for early February). There’s still time to tweak the language of the license if you spot any issues we’ve overlooked.
If you are using the GATK in an academic or non-profit research setting and have any questions or concerns about the details of the new license (attached), please join the discussion in the comments below. If you are using the GATK in a for-profit context, please contact our partners at Appistry as they will be in a better position to address your questions. If you’re not sure in which category you belong, please contact either Appistry or Issi Rozen at the Broad Institute.
As announced a few months ago, commercial users of the GATK will now be required to purchase a license in order to use the full-version GATK 2 for commercial / for-profit use (while GATK-Lite can still be used for any purpose without a license).
We are now able to give you more details about how this will work: we have selected a company called Appistry to be the exclusive partner who will handle for-profit GATK licensing and support. If you have any questions, please visit their FAQs page, and contact them directly to inquire about pricing or any "special case" scenario you feel may apply to your use of the GATK.
Appistry will launch a discussion forum within the next few days in which you will be able to network with your peers and Appistry staff about the for-profit release of the GATK.
If you would like to discuss why we have made these changes to the licensing model, please see our own discussion thread on licensing and source code models in GATK 2.
The license still refers to GATK2 in several places. For example:
"1.1 PROGRAM shall mean copyright in the object code and source code known as GATK2 and related documentation, if any, as they exist on the EFFECTIVE DATE and can be downloaded from http://www.broadinstitute.org/gatk on the EFFECTIVE DATE."
Not sure if this is intentional, but might want to update it for clarity, or better still eliminate all reference to version in the license.
I have been asked to reach out to you to clarify the GATK license. We are hoping to package our CNV/SNP calling and annotation pipeline that includes GATK and make it available on an Amazon Machine Image (AMI) for use on the Amazon EC2 cloud for anyone who wants to replicate our protocol using their own data. Of all the tools that we use, only GATK contains license restrictions. It is our intent that our AMI be used by academic/non-commercial users, and it is not intended to be sold. We can list the AMI in the AWS Marketplace as a Bring Your Own License (BYOL) instance. However, there are no checks provided by Amazon that users do in fact have a license. Is this permissible?
I have used GATK in my PhD project, and was wondering if I could get the permission to use the Best Practices workflow graphics  in my doctoral dissertation? How should I attribute your copyright?
I have two licence questions. First of:
There are two licence notes in BaseTest.java. I'm assuming that the top one is the one that should be viewed as currently in use. Is this correct?
Secondly, under which licence are the test resources made available. Am I'm free to use and redistribute these? I'm asking since I'm in the process of refactoring my pipeline project to use GATK as a external dependency, but some of the tests I've written use the files provided with the GATK as a resource, and I'd like to keep them and distribute them with the project as I've done before in my GATK fork.
We are keen to know more regarding the licensing arrangements for GATK 2.0, specifically availability and cost. I understand not all arrangements are yet in place, however we are eager to receive any updated information you may have. Please may I request contact information so that we may continue this discussion via telephone.
Thank you for your assistance. Kind regards,
PopulationGenetics Cambridge UK www.populationgenetics.com