MinIO is dual licensed under GNU AGPL v3 and commercial license.
The GNU AGPL v3 is designed for developers who are building open source applications in compliance with the GNU AGPL v3 license and are able to support themselves. It is fully featured. If you distribute, host or create derivative works of the MinIO software over the network, the GNU AGPL v3 license requires that you also distribute the complete, corresponding source code of the combined work under the same GNU AGPL v3 license. This requirement applies whether or not you modified MinIO. Please consult the license here ↗ or review the FAQs below.
A commercial license is available.
MinIO's commercial Object Store offering is designed for mission critical environments where both a license and strict SLAs are required. The commercial version includes all of the Object Store features, SLAs, Indemnification, optional annual architecture and security reviews, unlimited panic buttons, and other benefits that are detailed in the Customer License and Subscription Agreement.
What is the GNU AGPL v3?
The GNU AGPL v3 is short for the "GNU Affero General Public License v3." It is a FOSS ↗ license certified by the Free Software Foundation ↗ and the Open Source Initiative ↗. You can get a copy of the GNU AGPL v3 license with MinIO source code or at https://www.gnu.org/licenses/agpl-3.0.en.html ↗ .
What does it mean for me to comply with the GNU AGPL v3?
When you host or distribute MinIO over a network, the AGPL v3 applies to you. Any distribution or copying of MinIO software modified or not has to comply with the obligations specified in the AGPL v3 license. You must include the source code, full license text and the original copyright notice along with the object code.
We recommend the Free Software Foundation’s interpretation ↗ of the GNU AGPL v3 license.
Making combined or derivative works of MinIO
Creating combined or derivative works of MinIO requires all such works to be released under the same license.
If MinIO source code is included in the same executable file, they are definitely combined in one program. If modules are designed to run linked together in a shared address space, that almost surely means combining them into one program.
By contrast, pipes, sockets, RESTful APIs, and command-line arguments are communication mechanisms normally used between two separate programs. So when they are used for communication, the modules normally are separate programs. But if the semantics of the communication are intimate enough, exchanging complex internal data structures, that too could be a basis to consider the two parts as combined into a larger program.
Merely aggregating MinIO software into your distribution does not constitute derivative works. For more information, please refer to the GPL FAQ ↗.
Talking to your Legal Counsel
If you have questions, we recommend that you talk to your own attorney for legal advice. Purchasing a commercial license from MinIO removes the GNU AGPL v3 obligations from MinIO software.
