3 ms·
Your license, as I can read it, intends to prohibit profiting from your software by either (1) including it in their product, or (2) hosting it and selling its
by propter_hoc 6y ago
Your license, as I can read it, intends to prohibit profiting from your software by either (1) including it in their product, or (2) hosting it and selling its functionality. So for example, if a user wants to have some kind of Spotify import feature built into his online music-management service, he is not permitted by this license to build n8n into his paid service. (Correct me if I am wrong on this interpretation.)
But I think you will get a lot of demand for including this product in various workflows in an integrated way. Are you planning on releasing an API license, or some such?
- janober 6y agoYes, that is correct. If you use n8n as a backend or part of your backend that is totally fine. What is not permitted is to use n8n code to offer some kind of automation service.
- toomuchtodo 6y agoVery reasonable and generous to allow someone to generate revenue with your tool as a backend component as long as they’re not offering a verbatim automation SaaS service with a clone of your code. Kudos and thank you.
- janober 6y agoWe actually want that people use n8n as a backend and want to improve that further in the future and write more about it. We do not have to make money with literally everybody that uses our code. But if a good way to describe the service (or module, ...) is "automate X" then a license would be required. That we think is fair and makes sure that n8n is long term sustainable. And after all, is that also in the interest of the people/companies building on top of us.