Yeah, min.io really soured AGPL license, for me at least. Because of their stance I've switched away from min.io in our company and avoid everything AGPL like a plague. Having read the license many times and also all discussions around it, I understand that it should be fine to use an AGPL project in a commercial enterprise (without modifications, internally in backend network). However, if authors themselves of such a project believe and say otherwise, I'm really not going to risk anything and definitely not asking lawyers if "my specific use of min.io violates the license or not". I'm just using it as-is over network, internally in my backend deployment. Not modified and not exposed to external world.
> I understand that it should be fine to use an AGPL project in a commercial enterprise (without modifications, internally in backend network).
Making changes is fine too, so long as those changes are also distributed. "The source come with the binaries" is the general rule. You don't even have to open your whole stack (that is FUD), only the parts under the AGPL that you changed and only when you distribute it. Companies can and always have used these projects internally without risk.
