The agency sends its client a sheet of unmatched conversions every Monday. Then the client asks for a screen where they can set up their own triggers, conditions, and destinations. That feature changes which n8n license the agency needs to discuss.
Before you quote the work, sketch where the workflow runs and list who can change it.
Here’s the scenario we’ll follow. A marketing agency checks two authorized conversion exports every week. It compares the tracker export with the affiliate network’s export by conversion ID and gives the client a sheet of discrepancies to review. It’s an illustration, not a real client. If you need the reporting setup itself, start with our n8n affiliate reporting guide.

What the n8n license lets you charge for
n8n’s guidance permits paid implementation on client-run infrastructure, and agency-run, self-hosted workflows where the agency alone controls the logic and customers receive the results. If customers can design their own n8n-powered logic, or they’re paying to use hosted n8n, talk to n8n about a commercial agreement. That’s n8n’s reading in its License FAQ, checked November 18, 2026.
The Sustainable Use License (SUL) is the source-available license behind self-hosted Community Edition. n8n Cloud is a separate subscription with its own terms.
Notice what the test isn’t. It isn’t “do you make money with n8n?” One independent guide, from SSD Nodes, frames it well: the license doesn’t punish you for earning money with n8n. It stops you from turning n8n itself into the product. n8n’s FAQ is blunt about the other variables too. It says the determining factor is client access, not client count or revenue volume.
So your quote depends on two questions. Who controls the workflow logic? And is n8n the thing being sold, or a tool inside something else?
Follow the same report through five setups
Same weekly reconciliation report, five ways to deploy or sell it. The licensing readings are n8n’s, not ours.
| Setup | Where it runs and who can edit | What the buyer gets | Licensing path to explain |
|---|---|---|---|
| Client hires an implementer | The client runs n8n in its own environment. The agency installs the workflow and is invited to maintain it. | An internal reporting workflow, plus implementation or maintenance. | n8n permits paid consulting on the client’s own infrastructure, as long as you aren’t also hosting it for them. The client chooses a plan or license for its own use. |
| Agency sells a managed report | Only agency staff create or edit workflows on the agency’s self-hosted instance. A client may authorize an account for a fixed workflow. | A spreadsheet or report and an agreed review cadence. | n8n’s current guidance allows this under the SUL on the stated conditions. Keep the client’s access limited to authorization and outputs. |
| SaaS includes a fixed report | The app receives a CSV, runs a fixed workflow in the background, and displays the result. Product staff own the rules and access to the workflow. | The application’s reporting interface and review history. | Check the SUL FAQ’s backend examples and the role of n8n in the value being sold. Community Edition can fit the documented pattern. |
| SaaS lets buyers build rules | Buyer-created triggers, conditions, and actions are translated into n8n workflow logic through the app. | The ability to design automations for their own account. | Discuss a commercial agreement. The help center points to Enterprise for customer-configured automations even through a custom interface. Confirm the rights in the applicable agreement. |
| SaaS embeds the n8n editor | Customers create and edit workflows in the n8n canvas inside the product. | A visible, n8n-branded editor. | Ask about n8n’s separate OEM offering. |

Paid hosted access. This is the frequent mistake. Selling a login to an agency-hosted n8n editor needs a commercial agreement, even when each customer has an isolated instance. Isolation doesn’t change what you’re selling. For work across several client-owned environments, n8n’s FAQ says to write to its licensing team, and it mentions a partner program for multi-instance management that was still in development when we checked.
Why you shouldn’t settle this on a forum. In August 2026 a small agency posting as AutomatIA, with three to five clients, asked the n8n community forum a question that matches row two. It would host one instance. Each client would have separate workflows and credentials. Clients would never touch the editor. Did that need a commercial license? A volunteer said yes, and the agency marked it “confirmed.” Later in the thread the same volunteer clarified: “we’re not n8n team, we’re just volunteers.”
Now compare n8n’s own FAQ. It describes an automation consultant on one self-hosted instance, where clients pay for outcomes and get outputs only, and calls that allowed. It also says clients can generate their own OAuth credentials for that setup. The thread predates n8n’s October 6, 2026 help-center update by about seven weeks, and that update spells out the agency case. A forum answer and the vendor’s current text can say opposite things.
It happened before. In late 2025 a developer asked whether a client reselling automation results to its own customers fit the SUL. A volunteer said it likely needed an Embed license, and the developer wrote that he’d pitch his client on that route. He’d emailed n8n’s sales team two days earlier and hadn’t heard back. Two lessons: a confident answer can quietly rewrite your proposal, and a reply from n8n takes time. Send your question before you quote.
Authorization and roles. In row two, the client authorizes an account through OAuth and the agency’s workflow reads the data. The client keeps the relationship with the network. The agency keeps the logic. n8n’s FAQ says it plainly: the question isn’t whose credentials are used, it’s who controls the workflow logic. Our client handover checklist walks through who hosts the instance and who holds credentials.

When a SaaS feature changes the license conversation
Picture two screens in the same product.
Screen one. The client uploads two CSVs and clicks “Run report.” The vendor owns the join rules and the workflow. The dates and files are inputs to one fixed workflow. The customer triggers it and doesn’t shape it. n8n’s FAQ says users can trigger pre-built automations and even connect their own accounts to them.
Screen two. The client creates a rule. They pick a trigger, add a condition, choose a destination, and save. Now the customer’s settings decide what the workflow does.

n8n’s FAQ has a pair of examples that mirror these screens. A project-management SaaS sends each support ticket to n8n through an internal API call and shows the user a priority score. n8n calls that allowed, because it’s a silent processing layer and the product’s value is the app. A freelancer-focused SaaS lets users build their own automations through a custom UI, with n8n running invisibly behind it. n8n says that isn’t allowed, because the custom layer doesn’t change who defines the logic. It adds that the test is medium-neutral, so an API, MCP, or an AI agent writing rules for the user counts the same.
Wrapping the editor in your own interface doesn’t make customer-designed logic vendor-designed.
Credentials don’t settle it. The October help-center article says the same: clients can connect their own accounts, but they can’t open the editor or change the logic. Keep three things apart:
- An authorized OAuth connection, where the client lets your workflow read its data.
- Editor access, where someone can build or change workflows.
- Notes about a plan-specific credential feature, which belong to a plan and not to the license question.
Describe the surfaces the client actually uses. If you’re on n8n Cloud, its own agreement applies instead.
Read the vendor wording closely. n8n’s FAQ gives backend examples permitted under Community Edition. Its OEM page presents Enterprise as the commercial backend offering and OEM for the branded editor. The October help article points to Enterprise for customer-controlled automations through a custom UI. Check the signed agreement and order form for your deployment. n8n’s published End User License Agreement (effective August 27, 2026) covers purchases through a reseller. Use the OEM name from the current page. Some community threads and third-party guides still say “Embed,” so expect the vocabulary to be inconsistent. When your product falls between descriptions, cite both references and ask n8n to confirm your deployment.
Two real deployments. Formula Bot is the fixed-backend shape. In n8n’s published case study, founder David Bressler runs the frontend and database in Bubble and uses n8n webhooks for heavy processing. Bubble gets an immediate response while n8n works in the background. Roughly 60 percent of Formula Bot’s workflows now run in n8n, and they can last up to 10 minutes. He describes himself as a data analyst, not a coder, and credits n8n for letting a solo founder with two developers handle enterprise-style workloads. Customers use Formula Bot. n8n doesn’t show up in their experience.
pxtra, a German B2B benefits platform, shows operator ownership. Every new customer arrived with a different HR and payroll setup, so the company moved those integrations into n8n workflows connected to its product through a REST API. It self-hosts n8n inside its own infrastructure for security and compliance. Its development lead reports a cleaner codebase and far fewer bugs after offloading custom scripts. Each integration can also be sold as an add-on service on top of the software license. The engineers adapt a base workflow per customer, so the logic is the operator’s.
n8n lists Business for Formula Bot and Enterprise for pxtra. The case studies show how each company uses n8n. The terms of their individual agreements are private, so use the architectures as examples and ask n8n to confirm the license for yours.
If you’re still deciding what to build into the product, our post on How to Find Micro-SaaS Ideas on Upwork covers what to validate first.

What to send n8n before you quote
n8n’s help desk is upfront that it can’t confirm your specific use case, and sends you to license@n8n.io. Here’s an email you can adapt for our example:
We plan to self-host n8n on infrastructure our agency operates. Our team creates and edits the weekly reconciliation workflows. Clients authorize a reporting account through OAuth and receive a discrepancy report. We charge for the reporting service. We may later add a screen where clients build their own conditional routing rules. Could you confirm whether the initial setup fits the Sustainable Use License and what agreement would cover the second feature?

For a different deployment, cover these points:
- Product: name it and say who pays for what.
- Instance: who owns it, and which edition.
- Authorization: how clients connect accounts.
- Customer access: what they can trigger or change in the UI or API.
- Visibility: whether they see any n8n controls.
For a commercial quote, add estimated executions. Our illustrative four-week estimate is 20 clients × 4 scheduled runs, plus 10 reruns, so 90 executions (assuming one execution per run). Then ask n8n how it counts actual usage.
That number should calm you down. n8n’s published self-hosted Business tier is €667 a month billed annually and includes 40,000 executions. Ninety is nowhere near it. Volume isn’t what makes the second feature expensive. The agreement category is.
Run the numbers before you price the feature. If a commercial quote came back at $50,000 a year, for example, that would be about $4,167 a month. This is a budgeting scenario. Ask n8n for a quote for your own setup. Spread across 20 clients, that’s roughly $208 per client per month before your own margin. If the report was priced as a cheap add-on, you’d want to know that before the customer sees a rule builder.
Send license questions to license@n8n.io and commercial terms to sales@n8n.io. If your quote includes implementation or maintenance, our n8n agency pricing guide covers what to bill for.
FAQ
Can I use Community Edition in a paid SaaS? Yes, in a documented pattern. n8n’s FAQ describes a SaaS that sends support tickets to n8n through an internal API and returns a priority score. Only the backend talks to n8n, users never configure it, and the product’s value comes from the app. If outsiders can control the workflow, or n8n is the thing being sold, ask n8n.
Can clients connect their own accounts? Under n8n’s current self-hosted guidance, yes. In our example the client authorizes a reporting account and receives the output. The condition is that they can’t open the editor or change the logic.
What if I bundle n8n into software I ship to a client’s server? Get a specific review. n8n’s FAQ uses a document-processing tool with n8n installed at the customer’s premises and calls it permissible but possibly gray. Once a customer has local access, it’s hard to guarantee they can’t build workflows. That’s different from installing and maintaining a client’s own instance as a consultant, which n8n allows if you aren’t also hosting it for them.
Sources
Vendor licensing guidance and published plan prices were checked on November 18, 2026.
- n8n Sustainable Use License v1.0 (LICENSE file in the n8n repository).
- n8n License FAQ, checked November 18, 2026.
- n8n Help Center, “Which license do I need for my use case?”, updated October 6, 2026.
- n8n OEM product page, checked November 18, 2026.
- n8n End User License Agreement for purchases through resellers, effective August 27, 2026.
- n8n case study: Formula Bot, founder David Bressler.
- n8n case study: pxtra, Mark Bosold and Denny Kunkel.
- n8n Community forum, agency licensing thread, August 17, 2026.
- n8n Community forum, client-automation licensing thread, October 31, 2025.
- SSD Nodes, “What the n8n Sustainable Use License allows,” checked November 18, 2026.
- n8n Plans and Pricing, checked November 18, 2026.





Leave a Reply