Hi Team,
As we have explored the n8n workflow using n8n docker setup. Here we are using beautiful workflow for our use cases.
My question is, can we use the same setup directly at the client side for handling client issues and task/automation ? or it need some kind of enterprise licensee ?
as people are saying as this is community version and we can simply use it.
Hi @Rupesh_Verma !
As far i understood until now about licenses is :
If you are deploying n8n directly on your client’s infrastructure (their server, their cloud account), and you are only providing consulting, workflow building, or maintenance services (i.e., you do not host n8n yourself, and your client is the only one using it for their own internal business purposes), this is allowed.
Providing consulting, setup, and support for a client’s self-hosted n8n instance is explicitly permitted by the license.
However, if you host n8n yourself and use it to automate tasks for multiple clients, or if your clients access n8n directly (for example, to connect their own accounts and build workflows), this is not allowed under the Community Edition license.
In such cases, you would need a commercial (Enterprise or Embed) license, as this is considered offering n8n as a service…
Summary , yes, you can “clone” your project and share/sell with others to use it with their own credentials/space etc..
so if we are giving consultation to our client and client has it self hosted docker instance. In that case client has to take any licensee for fully functional mode.?
I don’t understand that.
But anyways, if your client is using your “cloned” project for internal purpose applies same rules as to you.