Short answer: Yes — you can build automations with n8n and sell the outcomes to clients. No — you cannot white-label n8n, host it for them, or charge clients to access it without a commercial licence. Most agencies get this backwards, and the mistake is expensive.
Every "start an AI automation agency" video on YouTube tells you to sell n8n workflows. Almost none of them mention the licence clause that decides whether your business model is legal. This guide fixes that, in plain English, with the most up-to-date information at this time, September 2026.
Running an agency? If you'd rather not carry this risk yourself, Fismbot's done-for-you automation services run the engine for you — you buy outcomes, we handle the licence and the infrastructure.
Why this matters more than your tech stack
n8n is not open source in the way WordPress is. It's fair-code, released under the Sustainable Use License (SUL). That distinction is not academic — it's the difference between a compliant agency and one fielding a legal letter.
The licence grants you generous rights: use, modify, create derivative works, and redistribute. But it attaches three limitations:
- You may use or modify the software only for your own internal business purposes or for non-commercial/personal use.
- You may distribute it or provide it to others only if you do so free of charge and non-commercially.
- You may not remove or obscure any licence, copyright, or attribution notices.
Read rule 1 and rule 2 together and the boundary becomes clear: n8n can be the engine inside your service. It cannot be the product you sell.
This is the same principle behind how Fismbot's Post Pilot and Email Pilot are packaged — you subscribe to a marketing outcome, not to the automation platform underneath it.
The engine vs. the product — n8n licensing turns on exactly this distinction.
Watch (4 min): What Is n8n? Workflow Automation & AI Agents Explained — a quick primer on what n8n actually is before the licensing detail below makes sense.
The two things n8n explicitly names as not allowed
n8n's own documentation is unusually direct here. It lists the following as examples that wouldn't be allowed under the SUL:
- White-labelling n8n and offering it to your customers for money.
- Hosting n8n and charging people money to access it.
That's the line. If n8n itself — the interface, the workflow builder, the execution engine — is what your client is paying for, you're outside the free licence.
The common denominator across every prohibited case: n8n becomes the product being sold. A standalone hosting offering, a relabelled automation platform, a SaaS product whose value derives entirely or substantially from n8n functionality.
What is allowed (this list is longer than people think)
According to both the official licence docs and n8n's own support team, the following are compliant:
- Using n8n internally to deliver automation outcomes to clients.
- Consulting around n8n and running workflows on the client's behalf.
- Selling the results of a workflow — a report, a database entry, a message sent, a booked call.
- Installing a workflow on the client's own infrastructure (their VPS, their account).
- Building automations where clients never touch n8n.
One agency owner confirmed this directly with n8n support, who confirmed: "Using n8n internally to deliver automation outcomes is allowed. Consulting + running workflows for clients is allowed. What's not allowed: giving clients access to n8n, reselling it, or white-labelling it."
You're selling the output of the machine, not the machine.
The decision table: does your model survive the licence?
| Your business model | Compliant? | Why |
|---|---|---|
| Build workflows in your n8n instance, client never logs in | ✅ Yes | Internal use, selling outcomes |
| Deploy n8n on the client's own server, they own it | ✅ Yes | It's their instance, their licence |
| Consult, support, and maintain client automations | ✅ Yes | Services around the tool |
| Sell a workflow JSON template pack (free distribution) | ✅ Yes | Non-commercial redistribution |
| Give clients logins to your shared n8n instance | ❌ No | Providing access for money |
| Host n8n and charge a monthly "access" fee | ❌ No | n8n-as-a-service |
| Rebrand n8n as "YourAgency Automate" and sell it | ❌ No | White-labelling |
| Build a SaaS whose value derives from n8n | ❌ No | Embedding commercially |
Print that table. It answers 90% of the "is this legal?" questions agencies ask.
Related: Marketing Automation that Sticks to Mind — ideas most agencies pay to learn about.
The $50,000 reality check
Here's the part the YouTube tutorials skip. If your model does fall on the "no" side, your options are a commercial agreement with n8n — and community reports put the Embed / commercial licence at around $50,000 per year. Enterprise licensing has been quoted starting around €10,000, but for genuine white-label embed rights, expect the higher tier.
For a solo agency doing $5K/month, that maths doesn't work. It's not a fee you absorb; it's a fee that kills the model.
The forum thread that surfaced this is worth reading in full — one commenter's summary is blunt: "It's all nice and shiny, until you realize that selling n8n workflows to businesses while hosting it needs the embed licence, which starts at $50k per year. No one ever mentions this in their videos."
A $50K/yr licence is not a rounding error for a small agency.
Watch (5 min): n8n Pricing Explained — Plans and Cost Guide — covers the execution-based cloud tiers so you can model your own hosting maths.
Three business models that are compliant and profitable
If white-labelling is off the table, what actually works? These three cover almost every successful n8n agency I've seen.
1. The "invisible engine" model
You run n8n on your own infrastructure. Clients never see it. They buy a result — "we'll book you 20 qualified calls a month" or "we'll keep your social feeds full automatically."
- You charge for: the outcome, not the tool.
- Client sees: dashboards, reports, booked meetings.
- Licence position: fully compliant (internal use).
- Best for: agencies selling to non-technical SMBs who don't care what's under the hood.
This is the model behind Fismbot's done-for-you services — the automation is invisible; the outcome is the product.
2. The client-owned-instance model
You build the workflow, install it on the client's own server (their VPS, their n8n Cloud account), and hand it over. They own the instance and the licence. You charge a build fee plus an optional maintenance retainer.
- You charge for: setup, then ongoing management.
- Client sees: their own instance, their own data.
- Licence position: compliant — it's their instance.
- Best for: clients who want ownership, or who have compliance requirements.
3. The outcome-service model (retainer)
You never sell "an automation." You sell a monthly service: lead generation, content publishing, inbox triage, reporting. n8n is one tool among several.
- You charge for: a recurring service line.
- Client sees: the business function running smoothly.
- Licence position: compliant.
- Best for: building predictable MRR.
Sell the outcome. The tool is your business, not your product.
Watch (7 min): How I'd Learn n8n if I Had to Start Over in 2026 — covers tracking outcomes so you can prove value and charge retainers.
What about n8n Cloud's own tiers?
If you're on n8n Cloud, the same licence logic applies — cloud plans don't grant you reseller rights. The tiers (verified 2026) are:
- Starter: ~$20/month, 2,500 executions/month
- Pro: ~$50/month, 10,000 executions/month
- Business (self-hosted): ~$800/month, 40,000 executions/month
- Enterprise: custom pricing
Note the important detail many miss: the Business self-hosted plan introduces per-execution fees, a different economic shape from the free Community Edition. Teams that start free and scale into a paid self-hosted tier are the ones who get surprised. Model your execution volume before you upgrade, not after.
Also note: there are no specific restrictions on how many clients you serve from a single instance, as long as your use stays internal and clients never access it.
The compliance checklist (run this before your next pitch)
Before you sell your next "automation package," confirm:
- Clients never log into n8n — no shared instance, no guest seats.
- Nothing in your marketing says "we'll give you n8n" or implies tool access.
- Your branding never obscures or replaces n8n's notices on any distributed artefact.
- Your proposal language sells outcomes ("we'll book 20 calls/month"), not software ("we'll host n8n for you").
- If you deploy on client infrastructure, the client's name is on the account.
- Free workflow templates you distribute carry n8n's attribution.
Six checkboxes. Any "no" is a legal exposure you can fix this week by changing your wording and account structure — not your tech.
If you're evaluating whether to build this in-house or buy it as a service, Why Fismbot lays out the cost comparison side by side.
FAQ
Can I use n8n for client work at all?
Yes. Using n8n internally to deliver automation outcomes to clients is explicitly allowed by n8n support.
Can I charge clients a monthly fee for automations running on my n8n instance?
Yes, as long as you're charging for the service/outcome and clients never access n8n itself.
Can I sell n8n workflow templates?
Distributing templates free of charge is allowed. Selling access to n8n as a platform is not. If the value the customer buys is the template logic rather than n8n access, you're generally on safe ground — but keep the licence notices intact.
How much is the n8n embed/commercial licence?
Community reports point to around $50,000/year for embed rights. Enterprise licensing has been quoted from ~€10,000. Confirm directly with n8n sales for your specific use case.
Do I need a licence if I install n8n on the client's own server?
No — the client holds the licence for their own instance. You're providing a build service.
What happens if I white-label anyway?
You're outside the licence terms. n8n can require you to stop or to purchase a commercial licence. At minimum you'd be exposed to forced migration and legal costs — not a risk worth taking for a small agency.
The bottom line
n8n's licence isn't a trap — it's a shape. It tells you your business should sell outcomes, not access. Agencies that internalise that build durable, compliant, high-margin services. Agencies that ignore it build a business on a licence they don't have.
Sell the result. Keep the engine invisible. That's both the legal path and, as it happens, the easier one to sell.
Want the compliant version built for you? Fismbot's automation services are built on that exact model — you buy outcomes, we run the engine. Book a consultation and we'll map what's automatable in your business.
Not ready to talk yet? Join the Fismbot newsletter for one practical automation breakdown a week — including the compliance gotchas most agencies learn the hard way.
Sources
- n8n Sustainable Use License (official)
- Can I use n8n Cloud to manage workflows for multiple consulting clients? — n8n Community
- Does My Business Model Violate the n8n FairCode License? — n8n Community
- Selling n8n workflow for calls — n8n Community
- n8n Pricing
- n8n Review 2026: Pricing, Licence and Real Limitations — Sondero
Last updated: September 2026. Licence terms and pricing can change — always confirm current terms with n8n directly before relying on them commercially. This article is informational and not legal advice.