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.
The Enterprise Object Store offering is designed for mission critical environments where both a license and strict SLAs are required. Commercial version includes all of the Enterprise Object Store features, a four hour SLA, Indemnification, optional annual architecture and security reviews, unlimited panic buttons and other benefits that are detailed in the Enterprise License and Subscription Agreement.
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.
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.
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.
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.
MinIO logo and wordmark are representations of MinIO. Please follow the guidelines below for logo usage.
Version 1.0
MinIO is 100% open source under the AGPL v3.0 License. For more on license compliance please click here.
This document outlines the policy of the MinIO Project regarding the use of its trademarks. Any use of any MinIO trademark must be in accordance with this policy. For the purpose of this policy "Trademarks" means MinIO's word marks, service marks, logos, trade dress, names of products, services, business and the name of the corporation.
The MinIO trademarks include, among others, the names MINIO, the MinIO Stork, MinIO SUBNET, MinIO KES, MinIO Warp, MinIO DMT and MinIO Sidekick.
As a firm believer in Free Software ethos and a respected member of the community, we have a desire for widespread usage and improvement of our code by users, distributors and other community members, of our products distributed under Open Source Licenses. Although our code is Open Source, MinIO wishes to ensure that its trademarks remain reliable indicators of quality and source that our users have come to expect of us. It is also very important that we strictly enforce our trademark rights in order to be able to protect our users against people who use the marks to commit fraud. This means that, while you have considerable freedom to redistribute and modify our software, you must follow trademark law and this policy even for Open Source software. Balancing these two competing interests is not an easy task. We rely on our users, clients and community to help us achieve this balance.
Underlying MinIO's trademark policy is the general law of trademarks.
MinIO is designed to be used and extended, and MinIO recognizes that community members may need some way to identify the MinIO product in some way but you must ensure that consumers are not confused as to whether they are official (meaning approved by MinIO) or not.
Your use of MinIO's trademarks must always be non-confusing. People should always know who they are dealing with, and where the software they are downloading came from. Websites and software that are not produced or officially authorized by MinIO shouldn't imply, either directly or by omission, that they are.
In case of any confusion or clarifications, please write to us at legal@min.io
You may not change any MinIO Logo except to scale it. This means you may not add decorative elements, change the colors, change the proportions, distort it, add elements, or combine it with other logos. However, when the context requires the use of black-and-white graphics and the logo is color, you may reproduce the logo in a manner that produces a black-and-white image.
MinIO has tried to make its trademark policy as comprehensive as possible. If you are considering a use of a MinIO trademark that is not covered by the policy, and you are unsure whether that use would run afoul of MinIO's guidelines, please contact us at legal@min.io
If MinIO determines at any time, in its sole discretion, that your use of any of our trademarks violates this Policy, we may revoke permission for your usage, and you must immediately cease all use of the marks.
This policy may be updated from time to time. Please refer to this page for all updates.