n8n White Label: Cost and What You Can Rebrand (2026)
Oct 26, 202615 min read
How to rebrand n8n as your own
The short answer
"n8n white label" means putting your own name, logo and colours on n8n so your customers never see n8n's.
It comes through n8n Embed, a separate commercial agreement you negotiate with n8n, not a setting you switch on in a plan, which is a different arrangement from tools such as Activepieces that people also look at when they want embedded automation.
If you only run workflows for your own team, none of this applies to you.
What white labelling means here
Show someone else's software as if it were yours, and that is white labelling. For n8n, that means a customer opens an editor wearing your brand, builds or edits workflows inside your product, and has no idea what engine sits underneath.
That's a different job from self-hosting n8n to automate your own business. Internal use needs no rebranding at all.
The moment the editor, or the automations it produces, becomes something you sell or hand to clients under your name, you have crossed from using n8n to reselling it.
What the n8n Sustainable Use License restricts
Start with the licence, because the whole question begins there. n8n's Sustainable Use License allows internal business use but restricts reselling the software and removing or replacing its branding. That restriction is why rebranding is a licensing matter first and a technical matter second.
Confirm the terms with n8n before you commit to a build, because they and the Embed arrangement can change. The n8n vendor pages cited here were current on 26 October 2026.
Other tools, such as Activepieces, handle embedding under different terms, and the next sections compare how the options differ.
Everything below works on Activepieces' free plan. Start without code or a credit card.
What you can rebrand in n8n Embed
Only two things are confirmed. n8n's Embed page covers branding of the editor interface, logo and colours; domain, emails, credentials, sharing and isolation are not spelled out. The table separates what the page states from what I couldn't tie to it.
| Item | Customisable under Embed | Stays n8n's | Source page | Status |
|---|---|---|---|---|
| Editor UI | Branding of the interface | The editor software itself | n8n Embed page | Confirmed |
| Logo/colours | Your logo and colours scheme | Not stated | n8n Embed page | Confirmed |
| Domain | Not stated | Not stated | None found | Unconfirmed |
| Emails | Not stated | Not stated | None found | Unconfirmed |
| Credentials/OAuth apps | Not stated | Not stated | None found | Unconfirmed |
| Workflow sharing | Not stated | Not stated | None found | Unconfirmed |
| Tenant isolation | Not stated | Not stated | None found | Unconfirmed |
Two rows are confirmed and five are open, so quote only the first two to a customer.
What the Embed page speaks to is the visible layer: the editor wearing your name, logo and colours. That's the part the licence otherwise forbids you to change, which is why it needs the paid agreement.
If you want the editor on your own domain, that is a deployment matter, and sending invitation or password-reset mail under your sender name is a configuration matter. Neither appears as an Embed entitlement, so ask for it in writing before you promise it.
Where an embedded product lives or dies is in giving each customer separate workflows and credentials. n8n's published pages don't state how Embed handles tenant separation, shared workflows or your own OAuth app registrations, so treat all three as open questions.
Silence isn't permission. Every "Not stated" cell above is a question for n8n's sales team, and the answer belongs in the contract, not in a support chat.
How n8n licensing decides whether you need Embed
You need an Embed agreement only when n8n becomes part of what you sell. Running workflows for your own business needs nothing, and that's where the Sustainable Use License draws its line. Get that line wrong and the "Not stated" cells become your legal exposure.
Selling n8n as a service, or hosting it for customers for a fee, is not permitted without a commercial agreement; internal business use is. Everything below sorts into three situations.
Read the last two columns together, because they're not the same question: an agreement is about permission, white labelling is about the interface your customer sees. The table shows which of the three needs a paid agreement and which needs white labelling.
| Situation | What you do | Sustainable Use License allows it? | Agreement needed | White label needed |
|---|---|---|---|---|
| Internal use | Run workflows for your own company's operations | Yes | None | No |
| Agency client work | Build and maintain workflows on infrastructure the client owns or controls | Yes, as consulting | None | No |
| SaaS embedding | Put n8n inside your product so your customers use it | No | Yes, commercial Embed | Usually, if customers see the editor |
Internal use and agency work sit on the permitted side, so what follows concerns the two cases where the answer changes.
If you run n8n for your own operations, or build workflows for a client on an instance that is theirs, the license covers you. You're selling your labour, not n8n. You need no agreement and no rebranding.
The point where the license stops covering you is charging a client to host an instance you run for them. You're now selling access to n8n itself, so you need a commercial agreement, even if no customer ever sees a logo.
When your customers build or run automations through your own product, you're reselling n8n's functionality. This needs the paid Embed agreement, and white labelling comes up here as a term of that contract, not as a setting you switch on.
What n8n Embed costs and requires
That figure is reported by a third party rather than listed on n8n's own pricing page, so treat it as a starting point for the sales conversation, not a quote.
On n8n's pricing page, Cloud Starter is €20 a month, or €240 a year, and Cloud Pro is €50 a month, or €600 a year. Enterprise self-hosted starts at €8,000 a year.
The Embed number comes from WorkflowBuilder's comparison. It's roughly six times the Enterprise entry price and over 200 times Cloud Starter, so n8n prices it as a product-embedding licence, not a bigger plan.
Because the Embed figure is reported, not published, budget around it and expect the real number to depend on your use.
Most internal-automation buyers should stop at the jump from €8,000 to $50,000 and confirm they don't need Embed at all.
n8n Embed vs Cloud vs Enterprise self-hosted costs
Compare how each one is billed and hosted. n8n bills Cloud monthly and hosts it. Enterprise self-hosted bills annually and you host it.
Embed also bills annually, under a negotiated agreement, and the product runs on your side. Cloud and Enterprise cover your own team's workflows. Only Embed covers putting n8n inside something you sell to customers.
Check the feature list for SSO and projects against each tier before you sign, because those features depend on the plan.
Hidden requirements: hosting and support
Running anything is not in the $50,000, so organizations implementing Embed must budget separately for infrastructure, hosting, and operational costs. You bring the servers, the upgrades, the backups and the monitoring, and you carry the on-call burden when a customer's workflow fails.
Add engineering time for that work, plus legal review of the contract itself. Ask n8n in writing what support you get under Embed, since the pricing page doesn't say.
Easier to see it running than to read about it: set it up free, no card.
Where n8n white label is actually used
Embed fits when automation is a feature your customers touch inside your own product. It's overkill when the only people who see n8n are your own staff, because the license problem only exists once someone outside your company is using it under your name.
That's a narrow test, and most teams asking about white labelling fail it.
SaaS products with in-app automation
This is the clearest fit. If your product lets customers build workflows, connect their own accounts, or trigger automations from your interface, you're redistributing n8n's engine as part of what you sell.
That's the arrangement the license restricts without a paid agreement, so Embed is the route.
Before quoting any build, check the specifics: which triggers your customers need, whether their credentials must stay isolated per tenant, and whether the editor itself is exposed or only the results. Those details decide how much of n8n you are actually reselling.
Does n8n white label apply to agencies?
Who logs in decides the agency case, which sits in a grey zone. If you build workflows on your own n8n instance and hand clients the outputs, you're running automation internally and delivering a service. No rebrand is needed.
If clients get a branded portal where they open, edit, or manage workflows themselves, you're presenting n8n as your product, and that points back to Embed.
A branded dashboard that only reads from your own front end, with n8n hidden behind a webhook, is often a custom build and not a rebrand at all.
When no rebrand is needed
Internal platform teams are the plainest case. Employees using n8n to move data between company systems are not customers, so there's nothing to resell.
The same goes for consultants who run workflows on a client's own instance under that client's license. Paying for white labelling here buys a logo swap nobody outside the company will see.
| Use case | Fits Embed? | Why | Better alternative | Vendor-published example |
|---|---|---|---|---|
| SaaS product with customer-facing automation | Yes | Customers use n8n inside your product, which is redistribution | None; this is what Embed is for | n8n's Embed page describes this scenario |
| Agency with branded client portals | Only if clients edit workflows | Client-managed workflows present n8n as your product | Run workflows on your own instance and expose results through your own front end | None that I can confirm |
| Internal platform team | No | Only employees use it, so nothing is resold | Standard self-hosted or cloud plan | None needed |
Only one row is a clean yes, and the agency row depends on a single question: do clients touch the workflow editor? Answer that first, then take it to n8n in writing.
How to avoid n8n white label mistakes
Behind every one of these is the habit of treating white labelling as a setting instead of a contract, and each can be checked against n8n's own licence or docs pages.
The list below runs in the order teams tend to hit them, and the three that cost the most get a fuller explanation after it.
- Assuming the free, self-hosted edition can be rebranded.
- Stripping n8n's branding in a fork and shipping it.
- Hosting workflows for clients with no commercial agreement.
- Budgeting the licence fee and nothing for running it.
- Ignoring tenant isolation, so one client's credentials sit beside another's.
- Trusting a blog post over n8n's licence and Embed pages.
Free to self-host isn't free to rebrand. The licence restricts reselling and rebranding, so a logo swap on the community edition is a breach, not a customisation. A fork that removes branding (mistake two) breaks the same restriction, only with more engineering behind it.
Running workflows for your own business is one thing. Running them as a service your clients pay for, or inside a product you sell, is what the Embed agreement exists to cover.
If a client logs in to something you host, read that as your signal to get terms in writing before the first invoice.
The Embed fee buys permission, not uptime. Hosting, backups, upgrades, monitoring and support hours are yours, and they grow with each client you add. Price those first, then add the licence, or your margin disappears into maintenance.
Isolation and sourcing (mistakes five and six) come down to the same habit: ask n8n directly, and keep the answer on file.
Alternatives when you need embedded automation, including Activepieces
If n8n's answer on Embed terms doesn't suit you, there are two other routes: building on a workflow engine yourself, or running Activepieces, whose MIT-licensed core carries 772 integrations. The licence decides between them. Whichever you pick, record the date you read each vendor's terms.
Treat "open" and "rebrandable" as separate questions; the table below compares the three routes on what they permit. Each row comes from the vendor's own licence or docs page, checked on 26 Oct 2026.
| Route | Licence | Rebrandable parts | Hosting model | Published pricing | Checked |
|---|---|---|---|---|---|
| n8n Embed | Sustainable Use, commercial agreement for embedding | Whatever the agreement grants | Your infrastructure or n8n's, per agreement | Quoted by n8n on request | 26 Oct 2026 |
| Build on a workflow engine | Depends on engine; MIT engines allow reuse | Everything you build yourself | Yours | No vendor fee on MIT engines; engineering time is the cost | 26 Oct 2026 |
| Activepieces embed SDK | MIT community edition per its docs | Embedded builder inside your app, per the SDK docs | Self-hosted or vendor cloud | Check Activepieces' pricing page for the embed tier | 26 Oct 2026 |
What follows is how to read each row.
If you build on a workflow engine, you own the interface, the tenancy model and the support burden. With an MIT-licensed engine, rebranding raises no licence question, but you build per-customer isolation, credential storage and upgrade handling yourself.
That cost never shows up on a price list.
Activepieces answers the licence question differently: its core is MIT-licensed, and its LICENSE file in the activepieces/activepieces repository puts only the enterprise directories under a separate commercial licence.
Whatever ships under MIT you can run, fork, resell or embed without a negotiated agreement, which a source-available licence like n8n's does not give you, and its embed SDK puts the flow builder inside your own application.
It suits teams who need customer-facing, embedded automation, not someone who only wants n8n's own branding removed.
Read the docs to see which edition carries the embedding features, because that line decides whether you owe the vendor a commercial agreement anyway. Count the connectors your customers actually need, not the catalogue total.
Start with the licence, then test the one integration your customers will use first. A route that rebrands cleanly but lacks that trigger or action is worse than a harder route that has it.
Frequently asked questions
Licensing and branding
Can I remove the n8n logo on the free self-hosted version?
Treat it as not permitted without checking the license first. The community edition ships under n8n's Sustainable Use License, which is written around internal business use, so stripping branding to show the product to customers moves you toward the redistribution the license restricts.
Running it privately for your own team is a different case, and nobody outside sees the logo anyway.
Is n8n white label legal for agencies?
Building and maintaining workflows for clients is one thing; reselling or rebranding n8n itself is another, and only the second needs an agreement. If a client's automations run on n8n and the client never sees it as your product, you're probably fine.
If you host n8n for them under your name and charge for access, ask n8n for Embed terms in writing.
Does n8n offer a white label option on Cloud plans?
Don't assume a Cloud plan includes one. Branding control is handled through the commercial Embed arrangement, not as a setting you switch on with a subscription tier. If a plan page doesn't list custom branding, ask n8n's sales team directly instead of inferring it.
Setting up and verifying terms
How long does an n8n Embed agreement take to set up?
I can't give a reliable timeline. It's a negotiated contract, so duration depends on how clearly you can state your use case, your customer model, and how many instances you expect to run. Bring those answers to the first conversation and the process moves faster.
Where should I verify n8n's terms before buying?
Start with the license text in n8n's own repository and the current Embed information on n8n's site, then get the specifics confirmed by n8n in writing.
Marketing pages and forum answers go stale, and a reseller's summary isn't a contract. If your plan depends on one clause, ask n8n to confirm that clause by name.
