4 ms·

I'm confused :- ) Who are you writing to? Me or @janober? Did you mean that n8n could switch to AGPL? All versions of AGPL allow both non-commercial and commer

I'm confused :- ) Who are you writing to? Me or @janober? Did you mean that n8n could switch to AGPL? All versions of AGPL allow both non-commercial and commercial usage. (And one needs to share-alike one's modifications.) In any case I like the idea to be free for charities and public research :- ) You work with something like that? Is AGPL ok with you, or you're worried it might require you to open-source parts of your platform?

Dayshine 7y ago
You! :) AGPL requires all users to open-source their projects using your work, even if they don't modify your work. It is an extension of GPL not LGPL. If my web application uses an AGPL library, it's a derivative work. I, like many in my field, work in a small team with almost no budget. My current project involves collecting sensitive (medical) data over the internet. The cost and risk involved in open-sourcing our application is prohibitive. However, it's slightly less relevant for your project, as I can't see much value in directly integrating it into another application :) This is more a problem we run into with AGPL libraries, not AGPL applications.
- satvikpendem 7y ago
  Correct, you can buy the commercial license if you don't want to open source. This is a benefit of AGPL to the creators, and should you choose to open source your product, to the community as well. If you don't have the money, you can negotiate with the creator for the price. Note that this is a pricing/business problem and not a license problem. The creator, knowing your plight, may offer a commercial license for free, or a cheap, negotiated price.