n8n Sustainable Use License: What Consultants Can Sell

Updated October 2026. I checked this on 15 October 2026 against LICENSE.md and LICENSE_EE.md on the master branch of the n8n repository (commit 3c447b42a7), n8n's community license page, its License FAQ and its pricing page. This is a reading of published text by someone who builds on n8n, not legal advice. Where a case is not clear, n8n says to write to license@n8n.io, and so do I.

1. The decision

The question a consultant actually has is this: "I build n8n automations for clients and charge for them. Do I need a commercial agreement with n8n, or can I run all of it on the free self-hosted edition?" The owner of that decision is the consultant or the founder of a small automation practice, sometimes with a client's legal contact on the thread. Three things force it to be answered now rather than later: a client asks for a login "so we can tweak it ourselves", a second client arrives and you want to share one instance, or you start thinking about turning a repeated build into a product.

I publish n8n tutorials on this site and take n8n consulting work through the n8n automation page, so I read this license as a practitioner would. I did not find a single sentence that answers the question, so the rest of this guide assembles the answer from four primary sources and then tests the result on thirteen scenarios.

2. Why it matters

Fact. n8n is not open source by the Open Source Initiative's definition, and n8n says so. Its docs describe the Sustainable Use License (SUL) as a "fair-code" license: the source is available, you can run and modify it, and commercial use is restricted. GitHub's own license detector agrees that it is not a standard license. The repository API I queried on 15 October 2026 reports the license key as other with SPDX id NOASSERTION.

Fact. The consequences of getting it wrong are written into the license itself. Use that violates the terms "is not licensed", and the license ends automatically. If n8n sends you a notice and you stop all violations within 30 days, the license is reinstated retroactively. A second violation after reinstatement ends it "automatically and permanently". That is a harsher clause than most clients expect to find under a tool they were told was free.

Fact. The license has changed before. n8n's docs say it was Apache 2.0 with the Commons Clause until 17 March 2022, and that the switch to the SUL lifted the old restriction on charging for consulting and support. The docs also say every contributor signs a Contributor License Agreement that "gives n8n the ability to change its license without seeking additional permission". I would not build a business on a reading I had not dated. That is why this page carries a commit hash and a check date.

3. Options

There are six real options for a consultant. The list includes "do nothing", because for a one-client practice it is sometimes correct.

• A. One self-hosted instance that you operate, clients get outputs only. You build and run everything. Clients see emails sent, rows synced, messages answered. No client has a login.
• B. Install and configure n8n on the client's own server. The client owns the machine and the instance. You charge for installation, configuration, workflows and maintenance.
• C. Give clients editor access to your instance. This is the "let them tweak it" option. It is outside the community license.
• D. The client buys their own n8n subscription (Cloud, or a paid self-hosted plan) and you work in their account as a contractor.
• E. A commercial agreement with n8n: an Enterprise license, or the OEM route if clients will see the n8n editor inside your product.
• F. Defer. Stay on A for the clients you have, write down the boundary, and revisit when a client asks for something A cannot give.

4. What the sources say, and how they fit together

There are four layers, and they answer different questions.

The license text

Fact. LICENSE.md grants you the right to use, copy, distribute and modify the software "only for your own internal business purposes or for non-commercial or personal use". You may distribute it to others "only if you do so free of charge for non-commercial purposes". Read alone, that sounds like it blocks consulting. It does not, because "internal business purposes" is defined in the FAQ, not in the text.

Fact. The same file carves out source files with .ee. in the file name or a directory ending in .ee. Those fall under a separate Enterprise License (LICENSE_EE.md), which says the software "may only be used in production" if you hold a valid Enterprise license, with a development and testing exception. I counted how much of the repository that covers. The output is below.

The FAQ's definition of internal business purpose

Fact. The FAQ says "internal business purpose" means using n8n "within your organization or product where people outside of your business can receive or see what your workflows produce". Receiving and seeing outputs is fine. The test it keeps returning to is not who owns the credentials and not whether the n8n interface is visible. In its words, the SUL test "is not about UI visibility" and is instead "about who controls the workflow logic and whose commercial interests are being served."

Fact. The FAQ lists what you can do: use n8n to run your business, "build automations for your clients on your instance, as long as your clients do not have the possibility to create or edit them", and "charge your customers for workflow creation, setup, and maintenance services" and for "training and consultancy services". It lists what you cannot do: host n8n as a service and let clients build workflows, let external end users build or configure their own workflows through your product "whether via a custom UI, our API, MCP, or an AI agent acting on the user's behalf", fork the code to launch your own automation product, white-label it, or use license-key features without an Enterprise license.

The consulting section

Fact. The FAQ answers the consultant's question directly. Building, running and maintaining workflows on your own instance for clients is permitted, including charging fees, and "there is no limit on the number of clients you can serve from a single instance". The deciding factor, in n8n's words, is "client access, not client count or revenue volume". It adds that "clients pay for outcomes, not for n8n access".

Fact. It also covers option B: you can charge a client to install, configure, build on and maintain n8n on the client's own infrastructure, "as long as you don't offer hosting as well, which would compete with n8n's own Cloud offering". And it covers credentials: a freelance consultant whose clients authorize their own OAuth connections on a shared instance is allowed, because "what makes this permissible is not that the consultant enters the credentials, it is that clients cannot build or modify workflows."

The product-value test

Fact. A separate FAQ section restricts use where "the commercial value of a product derives entirely or substantially from n8n functionality". Its question is "is n8n the thing being sold, or is it a tool that supports something else being sold?" The worked example is a subscription product where customers connect apps, build automations in a visual builder and run them on a hosted backend. That is not allowed, whether or not the customer ever sees the n8n UI. A paid training workshop that uses n8n for live demos, with no ongoing learner access, is allowed.

Fact. One more row matters for anyone building a product. Using n8n "as a backend processing engine" is fine under the community license when only your backend talks to n8n and end users never configure workflows. The OEM page in n8n's docs repeats the line: triggering workflows by webhook or API, with users never seeing the editor, needs "no separate agreement". Surfacing the editor inside your product requires an OEM agreement, and n8n branding is required.

5. What I ran

The sources above are prose, and prose invites loose reading. So I did two things. First, I counted how much of the repository the Enterprise carve-out covers, using the GitHub tree API on the same master commit.

repo n8n-io/n8n, branch master, tree sha 3c447b42a7 (fetched 2026-10-15)
tree truncated: False
files (blobs): 31630
files matching the .ee. rule: 1299 (4.1%)

Observed. 1,299 of 31,630 files, about 4.1%, sit under the .ee. rule on that commit. The share is small, but it is not trivial: the paths I inspected include packages for the AI workflow builder, the CLI and the frontend. The FAQ is explicit that using enterprise features that ask for a license key, without an Enterprise license, is outside the community license. I did not map individual files to individual features, so I cannot tell you which options a given plan unlocks beyond what the pricing page lists.

Second, I turned the FAQ's rules into a checklist script and ran thirteen scenarios through it. The script is below in full. It encodes n8n's published rules and nothing else, so it is only as good as my reading, and the scenario list is mine.

#!/usr/bin/env python3
"""Encodes the rules in n8n's License FAQ (fetched 2026-10-15) as a checklist.
Not legal advice. When a scenario lands on GRAY or NO, ask license@n8n.io."""
from dataclasses import dataclass, field

FAQ = "docs.n8n.io/n8n-community-license/community-license/license-faq"

@dataclass
class S:
    name: str
    who_runs_n8n: str = "you"            # "you" | "client"
    you_host_for_client: bool = False     # you also host a client's own instance
    third_party_can_build: bool = False   # client/end user can create or edit workflows (UI, API, MCP, agent)
    n8n_is_the_product: bool = False      # commercial value derives (substantially) from n8n itself
    white_label_or_fork: bool = False
    uses_license_key_features: bool = False
    has_enterprise_license: bool = False
    ships_to_customer_premises: bool = False
    notes: list = field(default_factory=list)

def verdict(s: S):
    if s.uses_license_key_features and s.has_enterprise_license:
        return "YES", "covered by the separate Enterprise license (LICENSE_EE.md), not the SUL"
    no = []
    if s.uses_license_key_features:
        no.append("enterprise features need a license key (What you cannot do)")
    if s.white_label_or_fork:
        no.append("no forking into your own product or white-labelling (What you cannot do)")
    if s.third_party_can_build:
        no.append("someone outside your org can build workflows (Workflow building, credentials and control)")
    if s.n8n_is_the_product:
        no.append("product value derives from n8n itself (When product value derives from n8n)")
    if s.who_runs_n8n == "client" and s.you_host_for_client:
        no.append("installing is fine, hosting it as well is not (FAQ, consulting section)")
    if no:
        return "NO", "; ".join(no)
    if s.ships_to_customer_premises:
        return "GRAY", "customer has local access; confirm architecture with license@n8n.io (Workflow building, credentials and control)"
    if s.who_runs_n8n == "client":
        return "YES", "client owns the server, you charge for install and build (FAQ, consulting section)"
    return "YES", "n8n stays your internal tool; outputs go out, access does not (FAQ, consulting section)"

SCENARIOS = [
    S("Consultant: one instance, clients get outputs only"),
    S("Consultant: clients link their own OAuth, no editor access"),
    S("Consultant installs n8n on the client's own server", who_runs_n8n="client"),
    S("Same, but you also host it for them", who_runs_n8n="client", you_host_for_client=True),
    S("Give the client an editor login on your instance", third_party_can_build=True),
    S("SaaS with a custom UI where users build automations", third_party_can_build=True, n8n_is_the_product=True),
    S("Product calls n8n by webhook; users only trigger flows"),
    S("'AutoOps' subscription: customers connect apps and build", third_party_can_build=True, n8n_is_the_product=True),
    S("End-user AI agent edits workflows through the n8n API/MCP", third_party_can_build=True),
    S("Use a license-key feature on Community, no license", uses_license_key_features=True),
    S("Same feature, valid Enterprise license held", uses_license_key_features=True, has_enterprise_license=True),
    S("Fork n8n and rebrand it", white_label_or_fork=True),
    S("Ship customer-premises n8n inside a paid product", ships_to_customer_premises=True),
]

if __name__ == "__main__":
    print(f"rules source: {FAQ}")
    print(f"{'#':>2}  {'verdict':<7} scenario")
    for i, s in enumerate(SCENARIOS, 1):
        v, why = verdict(s)
        print(f"{i:>2}  {v:<7} {s.name}")
        print(f"{'':>11}-> {why}")
    counts = {}
    for s in SCENARIOS:
        v = verdict(s)[0]
        counts[v] = counts.get(v, 0) + 1
    print("totals:", counts)

This is what it printed on 15 October 2026:

rules source: docs.n8n.io/n8n-community-license/community-license/license-faq
 #  verdict scenario
 1  YES     Consultant: one instance, clients get outputs only
           -> n8n stays your internal tool; outputs go out, access does not (FAQ, consulting section)
 2  YES     Consultant: clients link their own OAuth, no editor access
           -> n8n stays your internal tool; outputs go out, access does not (FAQ, consulting section)
 3  YES     Consultant installs n8n on the client's own server
           -> client owns the server, you charge for install and build (FAQ, consulting section)
 4  NO      Same, but you also host it for them
           -> installing is fine, hosting it as well is not (FAQ, consulting section)
 5  NO      Give the client an editor login on your instance
           -> someone outside your org can build workflows (Workflow building, credentials and control)
 6  NO      SaaS with a custom UI where users build automations
           -> someone outside your org can build workflows (Workflow building, credentials and control); product value derives from n8n itself (When product value derives from n8n)
 7  YES     Product calls n8n by webhook; users only trigger flows
           -> n8n stays your internal tool; outputs go out, access does not (FAQ, consulting section)
 8  NO      'AutoOps' subscription: customers connect apps and build
           -> someone outside your org can build workflows (Workflow building, credentials and control); product value derives from n8n itself (When product value derives from n8n)
 9  NO      End-user AI agent edits workflows through the n8n API/MCP
           -> someone outside your org can build workflows (Workflow building, credentials and control)
10  NO      Use a license-key feature on Community, no license
           -> enterprise features need a license key (What you cannot do)
11  YES     Same feature, valid Enterprise license held
           -> covered by the separate Enterprise license (LICENSE_EE.md), not the SUL
12  NO      Fork n8n and rebrand it
           -> no forking into your own product or white-labelling (What you cannot do)
13  GRAY    Ship customer-premises n8n inside a paid product
           -> customer has local access; confirm architecture with license@n8n.io (Workflow building, credentials and control)
totals: {'YES': 5, 'NO': 7, 'GRAY': 1}

Observed. Five scenarios pass, seven fail and one lands in gray territory. Every pass is a case where n8n stays your tool and the client receives results. Every failure has at least one person outside your organization who can build or change workflow logic, or an Enterprise feature used without a license, or a fork. Scenarios 6 and 8 fail on two separate rules at once, which is why I made the script report every rule that applies instead of stopping at the first. The gray case, scenario 13, is the one n8n itself marks as needing confirmation, because once a customer has local access it is hard to guarantee they cannot build workflows.

The pattern matters more than the count. The rules do not ask how big you are, how much you earn, who owns the credentials, or whether the client can see an n8n screen. They ask who controls the workflow logic. Client access is the variable to manage.

6. Security and compliance

Fact. The SUL is a contract, not a regulation. No regulator audits it. What can happen is a licensing dispute with the vendor, and the termination clause above sets how fast that clock runs. The practical exposure for a consultant is that a client-facing arrangement drifts over time. A client gets an editor login "for a week" and keeps it, or an automation is later extended so that a client's AI agent can call the n8n API to create workflows. The FAQ treats that last case as the client building workflows through an agent.

Fact. The license also requires that "anyone who gets a copy of any part of the software from you also gets a copy of these terms", and that you keep licensing notices intact. If you install n8n on a client's server (option B), the client receives a copy of the software from you, so hand over the license text with it. The patent clause ends your patent license if you or your company claim in writing that the software infringes a patent. That clause rarely matters for consultants, but it is in the file.

Recommendation. Treat the client boundary as a security control and review it the way you would review access. List every account, API key and webhook that touches each instance, and ask for each one whether a client or a client's tool can change workflow logic through it. For credential handling on a shared instance, see my notes on n8n credentials and secrets.

7. Cost

Community-edition costs are your hosting and your time, and I did not measure those, so there is no figure for them here. The paid plans are the comparison point if a client needs something the community license cannot give. These are list prices read from n8n's pricing page on 15 October 2026. The page text I extracted did not state tax treatment, so treat them as pre-tax list prices.

Estimate (arithmetic on list prices). Billed annually, Starter comes to 240 EUR a year, Pro to 600 EUR and Business to 8,004 EUR. The pricing page also lists a Start-up plan at 50% off Business for companies under 20 employees. I did not check eligibility terms, so I would not plan around it.

The comparison I would make is not Community versus Business. It is what the client's requirement costs under each route. If a client wants to build in n8n themselves, the license-compliant routes are their own subscription (option D) or a commercial agreement (option E). A client on Pro at 600 EUR a year has bought a tool they are allowed to edit. A client on your instance has not. n8n's own guidance for workshop attendees who want to keep using n8n points the same way: they should "create their own n8n Cloud trial or self-host their own instance". I am applying that sentence by analogy to clients, which is my inference, not n8n's statement. For a wider cost comparison across automation platforms, see switching from Zapier to n8n and the ROI calculator.

8. Operational complexity

Option A is the cheapest to run and the easiest to get wrong over time. It needs one discipline: nobody outside your organization gets an account on the instance. That is a policy, not a technical limit, so it fails silently when a deadline pushes someone to share a login.

One shared instance also concentrates risk. A credential mistake or a bad deployment affects every client. The FAQ allows several instances ("Run several instances of n8n community version"), so one instance per client is permitted and is the cleaner choice when clients have different data-handling needs. The cost is more servers to patch. My Docker self-hosting guide covers the baseline setup.

Option B moves the ops burden to the client's infrastructure, which is the right trade if the client has its own IT team, and it keeps hosting out of your hands. The FAQ adds that managing n8n across many client environments is a case for contacting n8n, since "a partner program covering multi-instance management is in development". n8n also lists an experts directory at experts.n8n.io; I have not checked its terms.

There is one handover cost worth planning for. If a client later wants to own and edit the workflows, you move them to an instance the client controls. Keep your workflows exportable, document credentials separately from logic, and agree in the contract who owns the workflow definitions. The license does not decide that. Your contract does.

9. Scale

The recommended option changes at specific triggers, not at a client count:

• A client asks for editor access. Move that client to their own subscription or instance (D or B), or sign an agreement (E). Do not make an exception on your shared instance.
• You repeat the same build for many clients. Repetition alone is fine. The moment you package it so that customers configure it themselves, you are close to the "AutoOps" example in the FAQ, and the product-value test applies.
• You want to put your own interface in front of n8n. A thin UI over fixed workflows, where users trigger runs, is the backend model. A UI where users define their own automation logic is the embedded workflow builder the FAQ calls not allowed. The FAQ's answer to that case is to talk to sales about an Enterprise license.
• An AI agent acts for the end user. The FAQ says the test is "medium-neutral". A user whose agent calls the n8n API to create workflows counts as the user building them.

10. Decision matrix

I score each option on five dimensions. The reasoning is in the sections above: license exposure follows from who can build workflows (section 4); cost follows from the price table (section 7); client control and operations follow from sections 8 and 9. Low, Medium and High are my judgment, not measurements.

11. Recommendation by scenario

Recommendation. I do not think one answer fits everyone. These are the five cases I would expect a consultant to be in, and what would flip each.

• Solo consultant, a handful of clients, no one wants to edit. Option A with a written rule: no client accounts. Flip to D or B the day a client asks to edit.
• Consultant whose clients have their own IT and security teams. Option B. The client owns the server and the data path, and you stay on the right side of the "no hosting as well" line. It flips to E if the client asks you to run it for them on your infrastructure with their staff building.
• Client who wants to build and maintain flows in-house after you hand over. Option D, or B with the client's own admin. Agree on the handover in the contract.
• Founder turning repeated builds into a product. Decide first whether n8n is invisible and users only trigger flows (the backend model, community license) or whether users configure automation (Enterprise or OEM). If the second, start the conversation with n8n before you write the front end.
• Any case you cannot place in the table above. Option F, then an email to license@n8n.io describing the architecture. Keep the reply. For its customer-premises document-processing example, the FAQ says to "confirm your architecture with license@n8n.io before launch", and I would do the same for anything similar.

12. Migration path

If you are already running client workflows on a shared instance, this is the order I would work in. It takes an afternoon per instance, and none of it needs n8n's permission.

1. Inventory access. List every user account on each instance and every API key. Mark anyone who is not your organization.
2. Inventory indirect access. Check which client systems or agents can call the n8n API or an MCP endpoint. A webhook that triggers a fixed workflow is fine. A tool that can create or edit workflows is not.
3. Decide per client. For each client with access, choose D, B or E. If none of them fits, remove the access.
4. Check for license-key features. If any instance uses a feature that asks for a license key, confirm which plan or license covers it.
5. Write the boundary into your contract. State that clients receive outputs, not access, who owns workflow definitions, and what happens at handover.
6. Date your reading. Save the commit hash, the FAQ text and a screenshot or copy of the pricing page the day you decide. The license can change, and the CLA says n8n can change it.

If you are scoping an n8n project and want to check where the client boundary sits before you quote it, see the consulting page or the AI readiness assessment.

What I could not verify

I did not test any of this against n8n's own licensing system, and I did not ask n8n. I could not find a published price for an Enterprise license or an OEM agreement, and I did not verify the terms of the experts directory or of the Start-up plan. The FAQ page showed "last updated 22 days ago" when I fetched it, and n8n has moved its license page: the older docs path /sustainable-use-license/ returned 404 when I tried it, and the current page is /n8n-community-license. A summary written against older paths may be out of date, so compare any third-party explainer to the FAQ text before you rely on it.

Ready to Get Started?

If you are scoping an n8n project and want a second pair of eyes on where the client boundary sits before you quote it, book a free 30-minute call. See also the n8n automation page.

Book a Free Discovery Call

Suyash Raj Founder, Voxdonna AI and AiSewak. Writes here about n8n, AI agents, and voice automation.