Skip to main content

​
Dual Licensing Model

The Birdflop website project uses a dual licensing model to support both open-source collaboration and allow for commercial use cases.

​
Open Source License

​
AGPL-3.0

For open-source usage, this project is available under the GNU Affero General Public License v3.0 or later (AGPL-3.0-or-later).
The full text of the AGPL-3.0 license can be found in the OSS_LICENSE.md file in the repository.

​
What This Means

Under the AGPL-3.0 license, you are free to:
  • Use the software for any purpose
  • Study how the software works and modify it
  • Share the software with others
  • Distribute your modifications

​
Requirements

If you use, modify, or distribute this software under the AGPL-3.0 license, you must:
  • Make source code available: If you run a modified version on a server and let others interact with it, you must make the complete source code available to those users
  • Use the same license: Any modifications or derivative works must also be licensed under AGPL-3.0
  • Preserve notices: Keep all copyright and license notices intact
  • Document changes: Clearly indicate any modifications you’ve made
  • Provide installation information: Include information needed to install and run modified versions

​
Network Use Provision

The AGPL-3.0 is specifically designed for network server software. Unlike the GPL, the AGPL requires you to release the source code even if you only provide the software as a service over a network (such as hosting a modified version of the website).

​
Closed Source License

​
Commercial & Non-Commercial Use

For closed-source use and modification (both commercial and non-commercial), a separate license is available by purchase.

Obtaining a Closed Source LicenseVisit the Birdflop Discord to inquire about obtaining a closed-source license.All other closed-source usage is disallowed.

​
What Requires a License

You need a closed-source license if you want to:
  • Use the code in a proprietary/closed-source project
  • Distribute the software without sharing the source code
  • Use the software in a commercial product without open-sourcing it
  • Modify the software for private use without releasing the changes

​
RGBirdflop Component

Special licensing is required to re-use the RGBirdflop / RGB Birdflop gradient creator code, regardless of whether you’re using the open-source or closed-source license.
The RGBirdflop component has additional licensing requirements beyond the base project license.

​
Attribution Requirements

​
For Open Source Projects

If you are hosting this site or a single page from this site for your server or own project under the AGPL-3.0 license:
  • Credit the original: Please credit Birdflop in some way
  • Link to GitHub: A link to the original GitHub repository is sufficient
  • Preserve license notices: Keep all license and copyright notices in the code

​
Example Attribution

Based on the Birdflop website
<a href="https://github.com/birdflop/web">GitHub Repository</a>

​
Contributing License Agreement

​
Your Contributions

By contributing to this project, you agree that:
  • Your contributions will be licensed under the same AGPL-3.0 license as the project
  • You have the right to submit the contribution
  • You understand and agree that your contributions are public
  • You grant the project maintainers permission to use your contributions under both the open-source and closed-source licenses

​
Contributor Rights

  • You retain copyright on your contributions
  • You grant a license to the project, not transfer copyright
  • You can use your own contributions in other projects

​
FAQ

Yes! Under the AGPL-3.0 license, you can use it for your server website. Just remember to:
  • Credit the original project
  • Make your modified source code available if you make changes
  • License your version under AGPL-3.0 as well
Yes, under two conditions:
  1. Open source: Release your entire project under AGPL-3.0 and make source code available
  2. Closed source: Purchase a closed-source license from Birdflop
That’s allowed under AGPL-3.0! However, if you let others access your modified version over a network (like hosting a website), you must make the source code available to those users.
You can remove branding, but you must:
  • Still credit the original project (a link to GitHub is sufficient)
  • Follow all other AGPL-3.0 requirements
  • Not claim the work as entirely your own
No special permission is needed to contribute! Just:
  • Follow the contribution guidelines
  • Ensure you have the right to submit your contributions
  • Agree that your contributions will be under the project’s dual license

​
Questions About Licensing?

If you have questions about licensing:
  • General questions: Ask in the Discord server
  • License purchases: Contact via Discord for commercial licensing
  • Legal concerns: Consult with a legal professional

​
License Files

The complete license texts are available in the repository:
  • OSS_LICENSE.md: Full AGPL-3.0 license text
  • CSS_LICENSE.md: Closed-source license information
This documentation provides a summary of the licensing terms. For complete legal terms, refer to the actual license files in the repository.

Build docs developers (and LLMs) love

Get started for freeTalk to us