I’m trying to confirm whether a potential client automation setup would fall under the Sustainable Use License (SUL) or require a Commercial License. My initial intuition is that this use case would fall under the Sustainable Use License (SUL) as I believe it qualifies as internal business use, but I’d like to verify that before presenting it as an option.
I reached out to the sales team on Oct 29 but haven’t heard back yet, so I’m posting here for clarification in the meantime.
Context
I’m a software developer evaluating n8n for a business automation solution. The scenario involves a client who provides B2B services and wants to automate internal operations — for example, processing CSV data, sending emails or SMS messages, and updating records based on engagement results.
Only my client and I would access or manage n8n; their end clients would not. The client would charge their customers for the results of the automation (e.g., recovered leads, processed records), but not for direct access or use of n8n itself.
Simplified Workflow Summary
Triggered when a CSV or spreadsheet is uploaded.
Workflow loops through entries, sends communications (email/SMS).
A response form triggers a secondary workflow for processing replies.
Data is then sent back to my client’s internal system.
Future potential for AI message personalization.
Main Questions
Would this setup qualify as internal business use under the SUL, given that only my client and I access n8n?
Would hosting on a third-party provider (e.g., Hostinger or similar) affect the licensing requirements? I would assume it wouldn’t, since the instance would still be privately hosted and accessed only by my client and myself, but I’d like to confirm to be certain.
If the client later expands to similar automations for other clients (managed internally the same way), would those remain within SUL coverage?
Your described setup is compliant with the SUL as long as it is for your client’s internal use and only you and your client access n8n.
Hosting on a third-party provider does not affect SUL compliance if the instance is private.
Expanding to offer automations to your client’s clients would require a different license or agreement, as this is not considered internal business use.
Just to make sure I fully understand the distinction:
You mentioned that my described setup is compliant with the SUL as long as it’s for my client’s internal use and only my client and I access n8n: even though the automation itself provides a workflow outcome to one of my client’s clients. However, expanding to offer automations to different clients’ clients would require a different license or agreement, as that’s not considered internal business use. This is where I get a bit confused.
In Scenario 1, my client (let’s call them Client A) builds an automation/workflow that helps recover lost leads for their own client (Client B). Client A charges Client B for the outcome of the workflow. This use case, as I understand it, would fall under the SUL.
Now, in Scenario 2, Client A has multiple clients (Clients B – F). After the workflow proves successful for Client B, Client A asks me to build a different workflow for Client C that produces a different type of outcome; but still with the same access structure (only Client A and I use or manage n8n).
Could you clarify why Scenario 2 would fall outside the SUL even though the access and operational structure remain the same?
In other words, is the key distinction who benefits from the automation (my client’s clients) rather than who operates and accesses n8n?
I just want to ensure I fully understand the licensing boundary so I can explain it accurately to my client.
Thanks again for your time and help in clarifying this, I really appreciate it.
The key distinction in the n8n Sustainable Use License (SUL) is not just who operates or accesses n8n, but **who ultimately benefits from the automation and whose data is being processed**.
- **Scenario 1** (Client A builds a workflow for their own client, Client B, and charges for the outcome): This is generally allowed under the SUL, as long as n8n is used for Client A’s internal business purposes. Providing consulting or workflow-building services for a client is explicitly permitted, as long as the client (Client A) is using n8n for their own business and not reselling n8n functionality as a service to others. You can charge for consulting, support, or workflow development without a separate license agreement with n8n, as long as the use is internal to the client’s business and not offered as a product or service powered by n8n to third parties [What is and isn’t allowed under the license]( Sustainable Use License | n8n Docs ).
- **Scenario 2** (Client A uses n8n to build and operate workflows for multiple clients, Clients B–F, each with different outcomes, but only Client A and you operate n8n): This scenario is more problematic under the SUL. The license restricts use to “internal business purposes,” which means you cannot use n8n to provide automation as a service to multiple external clients, even if only you and Client A operate n8n. If the value delivered to Clients B–F derives substantially from n8n functionality, and they are the ultimate beneficiaries, this is considered “offering n8n as a service,” which is not permitted under the SUL without a separate embedding/commercial agreement [What is and isn’t allowed under the license]( Sustainable Use License | n8n Docs ) [Forum clarification]( Question about n8n license and client automations ).
**In summary:**
The SUL boundary is defined by the *end beneficiary* of the automation. If n8n is used to automate processes for your own company (or your direct client’s internal business), it’s allowed. If n8n is used to deliver automation as a service to multiple external clients (where those clients are the primary beneficiaries and their data is processed), it falls outside the SUL—even if only you and your client operate n8n. In such cases, you would need a separate commercial agreement with n8n (n8n Embed) [What if I want to use n8n for something that’s not permitted by the license?]( Sustainable Use License | n8n Docs ).
If you need further clarification for your specific use case, n8n recommends reaching out to them directly…
I know, it may be tricky to understand, but I think is about revenues more …
Gotcha, that makes perfect sense: the key factor is who ultimately benefits from the automation. Thanks for breaking it down so clearly. I’ll present it to my client as a case where a commercial (Embed) license would be the appropriate route if he wants to use an n8n workflow for his clients.
I really appreciate you taking the time to explain it so thoroughly. That clears it up for me.