ARE YOU USING n8n OPEN SOURCE? DID YOU KNOW THIS?
Key Provisions of the Sustainable Use License Relevant to This Message
According to the Sustainable Use License, the following restrictions apply:
✅ Allowed Uses:
  • Internal business use within a company (e.g., automating internal processes with n8n).
  • Personal or non-commercial use.
  • Providing consulting or support services related to n8n.
❌ Prohibited Uses:
  • Selling a product, service, or module whose value substantially depends on n8n.
  • Hosting n8n and charging users for access.
  • Embedding n8n into a paid service where users log in with their own credentials.
✅ License Restriction on Selling Access to n8n as a Service
If the intended use involves charging users for a service that heavily relies on n8n’s functionality, this would violate the license unless a separate commercial agreement (n8n Embed License) is obtained.
⚠️ Important: It is advisable to proceed cautiously and contact n8n for official confirmation before moving forward.
n8n’s Sustainable Use License and Enterprise License Follow the Fair-Code Model
License FAQs
What license does n8n use?
n8n uses the Sustainable Use License and the n8n Enterprise License. These licenses follow the fair-code model.
What part of the source code is covered by the Sustainable Use License?
The Sustainable Use License applies to all source code in n8n’s main GitHub repository, except:
  • Branches other than the master branch.
  • Source code files containing ".ee." in their name. These are licensed under the n8n Enterprise License.
What is the Sustainable Use License?
The Sustainable Use License is a fair-code software license created by n8n in 2022. You can read more about the reasoning behind it here.
This license allows you to use, modify, create derivative works, and redistribute the software for free, with three key limitations:
  1. You can only use or modify the software for your own internal business purposes, personal use, or non-commercial use.
  2. You may only distribute the software for free and for non-commercial purposes.
  3. You cannot alter, remove, or obscure any licensing, copyright, or other notices in the software. Any use of the licensor’s trademarks is subject to applicable law.
We encourage anyone interested in using the Sustainable Use License to do so. If you are developing something publicly, it is wise to consider licensing early to avoid future issues. Contact us at license@n8n.io if you have any questions.
What is and isn’t allowed under the license in the context of n8n’s product?
The license restricts use to "internal business purposes." In practice, this means all use is allowed unless you are selling a product, service, or module where the value derives entirely or substantially from n8n’s functionality.
🚫 Examples of NOT ALLOWED use cases:
  • White-labeling n8n and selling it to customers.
  • Hosting n8n and charging users for access.
✅ Examples of ALLOWED use cases:
  • Using n8n to sync internal company data, such as from a CRM to a company database.
  • Creating an n8n node for your product or an integration with n8n.
  • Providing consulting services related to n8n, such as workflow development, custom feature implementation, or code execution within n8n.
  • Setting up and maintaining n8n on an internal company server.
Can I use n8n as a backend to power a feature in my app?
Generally, yes, as long as the backend process does not use users' credentials to access their data.
🔹 Example 1: Syncing the ACME app with HubSpot
  • Bob sets up n8n to collect users’ HubSpot credentials to sync data between the ACME app and HubSpot.
  • ❌ NOT ALLOWED under the Sustainable Use License because it collects user credentials to integrate with ACME.
🔹 Example 2: Embedding an AI chatbot in the ACME app
  • Bob sets up n8n to embed an AI chatbot into the ACME app. The chatbot uses Bob’s company credentials, and users only enter their questions.
  • ✅ ALLOWED under the Sustainable Use License because no user credentials are collected.
What if I want to use n8n for something not permitted by the license?
You must sign a separate commercial agreement with n8n. We encourage software creators to embed n8n within their products, but they must sign an agreement specifying usage terms and applicable fees. This model is called n8n Embed. You can learn more and contact us here.
If you are unsure whether your use case qualifies as "internal business purposes," review the examples above or email us at license@n8n.io.
Why Doesn’t n8n Use an Open-Source License?
n8n’s mission is to provide technical superpowers to everyone. We believe that making n8n widely available while maintaining a sustainable business model is the best way to achieve this.
  • By making n8n free to use, easy to distribute, and source-available, we ensure accessibility.
  • By operating as a business, we can continue to develop features, fix bugs, and provide reliable software at scale.
Why Did n8n Create a New License?
Creating a proprietary license was not our first choice. We took this path only after reviewing existing licenses and determining that none fit our specific needs.
We designed our Sustainable Use License to:
  1. Be as permissive as possible.
  2. Ensure the sustainability of our business.
  3. Clearly define what is and isn’t allowed.
My company has a policy against using code that restricts commercial use. Can we still use n8n?
Yes, as long as you use n8n for internal business purposes and do not offer it to customers to connect their accounts and build workflows.
If you are unsure whether your use case qualifies, review the examples above or email license@n8n.io.
What Happens to Code I Contribute to n8n Under the Sustainable Use License?
Any code contributed to GitHub is subject to GitHub’s terms of use. This means:
  • You own and are responsible for your contributions.
  • You grant certain rights to other GitHub users to use your code.
n8n requires all contributors to sign a Contributor License Agreement (CLA), which:
  • Allows n8n to change its license without requiring additional permission.
  • Ensures contributors are not liable if their code causes harm.
Conclusion
The original message is valid because it correctly interprets the license’s restriction on selling access to n8n as a service.
If the planned use involves charging users for a service that relies significantly on n8n, this would violate the license unless a commercial agreement (n8n Embed) is obtained.
✅ It is prudent to contact n8n for official confirmation before proceeding.
3
0 comments
J London
3
ARE YOU USING n8n OPEN SOURCE? DID YOU KNOW THIS?
Content Academy
skool.com/content-academy
Build a profitable content strategy, efficient team & automated process
Leaderboard (30-day)
Powered by