Licenses

How to interpret our licenses and to use our source code and models.

Why we are open source

Free and open-source software (FOSS) is software that anyone is free to use, copy, study, change and share, and whose source code is openly available. Because everyone can see how the software works, anyone can help improve it, and those improvements can be shared back so the software gets better for everyone.

The free in FOSS is about freedom. The Free Software Foundation describes it as four essential freedoms:

  • The freedom to run the software as you wish, for any purpose.
  • The freedom to study how the software works and change it. Access to the source code is a precondition for this.
  • The freedom to share copies with others.
  • The freedom to share your modified versions with others, so the whole community can benefit from your changes.

The Open Source Initiative sets out similar criteria in the Open Source Definition.

Our choice

FlyByWire Simulations is an open-source community. We develop our projects following the FOSS spirit, and we have deliberately chosen licenses that keep them that way. Our source code uses the copyleft GNU GPLv3, so anyone who distributes a project based on our code must share their source code under the same license.

Our original 3D models are licensed under CC BY-NC 4.0, which allows anyone to share and adapt them, but not for commercial purposes.

This is part of the beauty of open-source licenses: they allow others to use our work and innovate on top of it. As long as our licenses are followed, others are free to use our source code and models for their own projects.

Using our source code or models in your own project

You are free to use our source code and models as long as you follow the rules and specifications of our licenses. Below is an explanation of the licenses and how they relate to our aircraft source code and models.

Source code: GNU GPLv3

Most of the systems and other source code in our aircraft repositories is licensed under the GNU General Public License v3.0. Some files, such as third-party libraries, use other licenses. Therefore, you must check the license header of each file you use as well as any license files in its parent directories. If you distribute anything based on our GPLv3 code:

  • Your project as a whole must be licensed under the GPLv3 as well.
  • You must make the complete source code available to everyone who receives your project, from the same place they download it and at no extra charge. Publishing it on a platform such as GitHub is the easiest way to do this. Anyone who receives the source code is allowed to share it further.
  • You must clearly state that you modified our code, and when. Keeping your project in public version control, such as git, makes your changes easy to track.
  • You must keep our copyright and license notices, and include a copy of the GPLv3 with your project.

The GPLv3 itself does not prohibit selling software, but a project that includes our 3D models cannot be sold. See below for more information. Note that anyone is free to use and redistribute the source code under the GPLv3, including for software sold which is GPLv3 licensed.

3D models: CC BY-NC 4.0

Our original 3D models are licensed under the Creative Commons Attribution-NonCommercial 4.0 International license. If you share anything that contains our models, or models based on them:

  • It must be non-commercial. You cannot sell it or put it behind a paywall; it must be available for free.
  • You must credit our work. For example, mention in your product description that your model is based on, and derived from, the FlyByWire models, with a link to our website.
  • You must keep our copyright notice, state that the model is licensed under CC BY-NC 4.0 with a link to the license, and link to our original model.
  • You must indicate that you modified our model, and keep any earlier notices of modifications.
  • You cannot suggest that your project is official, or endorsed by FlyByWire Simulations.

Microsoft Flight Simulator content

The FlyByWire A32NX was created under Microsoft's Game Content Usage Rules using assets from Microsoft Flight Simulator, and both our aircraft rely on the Microsoft Flight Simulator SDK, which comes with its own license agreement which you must review and follow. We can not provide guidance on licenses or End-User License Agreements of different projects or companies.

This page does not provide legal advice and is an overview of our projects and licenses. The actual license content is the source of truth and must be complied with.

Licenses by repository

These are the main licenses of our active public repositories, and are meant as general guidance. Some repositories include code or assets under other licenses, such as third-party libraries. For the specifics, always check the license header of each source file and any license files in its parent directories.

GNU General Public License v3.0

You may use, modify and distribute the code, including commercially, as long as anything you distribute based on it is also licensed under the GPLv3 and comes with its source code.

Plain-English summary on TLDRLegal

Applies to:

Creative Commons Attribution-NonCommercial 4.0 International

You may share and adapt the material for non-commercial purposes, as long as you give credit and indicate the changes you made.

Plain-English summary on TLDRLegal

Applies to:

GNU Affero General Public License v3.0

Similar to the GPLv3, but if you let others use a modified version over a network, such as a web service, you must also offer them its source code.

Plain-English summary on TLDRLegal

Applies to:

MIT License

You may do almost anything with the code, as long as you include the original copyright and license notice.

Plain-English summary on TLDRLegal

Applies to:

Questions?

If you have questions about our licenses, contact one of our developers, moderators, or admins on our Discord server.