No. The total annual revenue or funding limit is that of the whole organisation or individual that owns the Tracktion Engine licence. If your team or project is a small part of a large organisation then you will likely require a Pro licence. The revenue or funding limit is not based upon revenue generated by software containing Tracktion Engine nor the budget of a particular team or individual within an organisation.

Tracktion Engine is dual licensed under both the Tracktion Engine licence and the GPLv3.

This means that you can choose to use Tracktion Engine under the terms of the GPLv3 licence. If you are not "propagating" or "conveying" closed-source software containing Tracktion Engine outside of your organisation then you may not be violating the terms of the GPLv3. The creation and use of "in-house" tools and the internal development of "pre-release" software (before it goes out to external testers) is usually permitted under the GPLv3. Please refer to the GPLv3 terms for the full details.

If you are not using Tracktion Engine under the GPLv3 then you will require a Tracktion Engine licence. You will need to maintain a licence for at least the duration over which you are distributing closed-source binaries containing Tracktion Engine.

No. Tracktion Engine Educational licences are offered to bona fide educational institutions and come with the number of seats requested by the educational institution. Institutions requesting Educational licences must agree to submit any requested documentation to show proof of a bona fide educational institute.

By default all developers contributing any source code to software containing Tracktion Engine will require a Tracktion Engine licence.

However, there are certain situations where this doesn't make much sense. If the software development team using Tracktion Engine is a small fraction of the overall software development team, and the use of Tracktion Engine is not central to the overall product, then it is more appropriate that only the developers in the team using Tracktion Engine will require Tracktion Engine licences. If your use of Tracktion Engine meets these conditions please contact sales@Tracktion Engine.com and we can work out a fair licensing compromise.

While Tracktion Engine licences can be infrequently reassigned between developers, our licensing is not designed to be flexible with regards to team size. If a product containing Tracktion Engine ever had a large development team then it is the maximum concurrent size of the development team that fixes the number of licence seats required. If the team size is subsequently reduced to just a few people providing product maintenance post-release the product still requires the larger number of licence seats for the entire duration over which the product is distributed.

No. The software needs to be licensed by all the contributors to the source code. If you have not contributed to any of the source code then you do not require a licence.

However, you must ensure that the software is appropriately licensed for the whole duration over which you are distributing it. If any of the contributors are third parties then the distributor/seller is legally obliged to ensure that the corresponding licences are perpetal, rather than subscription, Tracktion Engine licences.

You can use either option.

If the hiring organisation purchases a licence then that licence can be used by the contractor for the duration of their work. When the contractor has finished the work the licence can then be re-assigned to a different contractor. If the hiring organisation will have a fixed maximum number of contractors working simultaneously then this licensing model may be the most appropriate.

It is also possible for contractors to have their own individual Tracktion Engine licences. In this situation the relevant revenue or funding limit will be that of the contractor, so it may be possible for contractors to use Indie licences where the revenue of the hiring organisation would exceed the Indie funding or revenue limit. However, the hiring organisation is responsible for ensuring that the software is appropriately licensed for the whole duration over which it is distributed (see the answer to the previous question above).

All license subscriptions are paid via PayPal. Your license will automatically renew each month.

You can review the license agreement here.

You can find our GitHub repository here including the README.

Make sure to review the license terms before purchase. Most licenses require a 12 month commitment. After that time, then you can cancel your license via your account page.