License Overview
Kitsu is free and open source software licensed under the GNU Affero General Public License version 3.0 (AGPL-3.0).What does this mean for you?You are free to use, modify, and distribute Kitsu, even for commercial purposes, as long as you comply with the license terms.
Quick Summary
You Are Free To:
Use
Use Kitsu for any purpose, including commercial projects
Study
Study how the software works and adapt it to your needs
Share
Distribute copies to help others
Modify
Modify the software and distribute your modifications
Your Responsibilities:
Share Source Code
If you distribute Kitsu or modified versions, you must make the source code available under the same AGPL-3.0 license.
The AGPL-3.0 License
Key Provisions
Freedom to Use
Freedom to Use
You may run the program for any purpose, without restrictions on who can use it or what they can use it for.
Freedom to Study and Modify
Freedom to Study and Modify
You have access to the source code and can modify it to suit your needs. The source code is a prerequisite for this freedom.
Freedom to Redistribute
Freedom to Redistribute
You can distribute copies of the original software to help others, with or without charge.
Freedom to Distribute Modifications
Freedom to Distribute Modifications
You can distribute your modified versions, so the whole community can benefit from your improvements.
Network Server Requirement (The 'Affero' Clause)
Network Server Requirement (The 'Affero' Clause)
If you run a modified version of Kitsu on a server and let others interact with it there, you must make the modified source code available to those users.This is the key difference between AGPL and GPL - it closes the “SaaS loophole” by requiring source code disclosure even when the software is only accessed over a network.
Copyright Notice
Common Questions
Can I use Kitsu in my studio without sharing my modifications?
Can I use Kitsu in my studio without sharing my modifications?
Yes, if you only use it internally and don’t distribute it to others or provide access over a network to users outside your organization.However, if you run a modified version as a service accessible to external users (e.g., clients, contractors), you must make your modifications available under AGPL-3.0.
Can I sell Kitsu or modified versions?
Can I sell Kitsu or modified versions?
Yes, you can charge for distributing Kitsu or modified versions. However, recipients must receive the source code and the same freedoms you received under AGPL-3.0.
Can I keep my custom plugins/extensions private?
Can I keep my custom plugins/extensions private?
This depends on how they’re implemented:
- If they’re separate programs that communicate with Kitsu through its API, they may not need to be AGPL.
- If they’re integrated into Kitsu’s codebase or form a combined work, they must be AGPL.
What if I only make small modifications?
What if I only make small modifications?
The size of modifications doesn’t matter. If you distribute modified versions or run them on a network server, you must make the source code available under AGPL-3.0.
Can I integrate Kitsu with proprietary software?
Can I integrate Kitsu with proprietary software?
Yes, you can integrate Kitsu with proprietary software through its API. API integration typically doesn’t create a derived work, so your proprietary software doesn’t need to be AGPL.
Compliance Guidelines
If You Distribute Kitsu
Provide Source Code
Make the complete source code available, including any modifications you’ve made.
If You Run Kitsu as a Network Service
Original Version
If you run the unmodified version, no additional action needed beyond what the license requires.
Full License Text
The complete GNU Affero General Public License v3.0 is available in:- The
LICENSEfile in the Kitsu repository - GNU AGPL-3.0 official text
- Kitsu GitHub repository
View Full License
Read the complete AGPL-3.0 license text on GitHub
Why AGPL?
CGWire chose the AGPL-3.0 license to ensure that:- Community Benefits: Improvements made by anyone benefit the entire community
- Transparency: Users can see exactly what the software does
- Network Protection: The “Affero” clause prevents the SaaS loophole
- Freedom: Studios maintain freedom to use and modify the software
- Collaboration: Encourages open collaboration and shared improvements
Contribution License
By contributing to Kitsu, you agree to license your contributions under the AGPL-3.0 license. All contributions must follow the C4 contract. See the Contributing Guide for more information.Third-Party Licenses
Kitsu uses various third-party open source libraries, each with their own licenses:Vue.js and Ecosystem
Vue.js and Ecosystem
- Vue.js: MIT License
- Vuex: MIT License
- Vue Router: MIT License
Build Tools
Build Tools
- Vite: MIT License
- ESLint: MIT License
- Prettier: MIT License
UI Libraries
UI Libraries
- Chart.js: MIT License
- FullCalendar: MIT License
- Fabric.js: MIT License (custom fork)
Other Dependencies
Other Dependencies
See
package.json for a complete list of dependencies and their respective licenses.Commercial Support
While Kitsu is free software, CGWire offers commercial support and services:- Professional support contracts
- Custom development
- Training and consulting
- Hosted solutions
CGWire Services
Learn about professional support options
Disclaimer
Not Legal AdviceThis page provides a general overview of the AGPL-3.0 license as it applies to Kitsu. It is not legal advice. For legal questions about license compliance, consult with a qualified legal professional.
Questions About Licensing?
If you have questions about licensing or compliance:- Review the full license text
- Check the GNU AGPL FAQ
- Ask on Discord
- Contact CGWire directly for commercial licensing questions
Related Resources
Contributing
How to contribute to Kitsu
C4 Contract
Contribution guidelines
GitHub Repository
View the source code
GNU AGPL-3.0
Official license text
