AbhijeetBuilts

n8n

n8n License Explained: What Businesses and Agencies Can Do

The n8n license explained in plain English: what businesses and agencies can do for free, and when hosting, embedding or white-labelling needs a paid deal.

10 Nov 2026 · 7 min read · Abhijeet Singh

Connect on LinkedIn

LOG 73Field journalFiled 10 Nov 2026
Technical ink illustration of a modular automation engine whose outputs flow out freely while access to its internal workflow logic stays locked, representing n8n license boundaries.
On this page 9 sections

If you run a business on n8n, or you build n8n workflows for clients, the n8n license question comes up sooner or later. Is it free for commercial use? Can an agency charge clients for workflows? Can you host n8n for a client, or put your own logo on it? The short answer: internal use and building workflows for clients are fine on the free edition, while hosting n8n as a service, letting outsiders build workflows, or white-labelling it needs a commercial agreement with n8n.

This post walks through what the license actually says, as of November 2026, using n8n's own license text, documentation and help center. It is a plain-English summary, not legal advice. If your setup is unusual, n8n asks you to email its licensing team, and that is the right move before you build a business model on an assumption.

If you are still deciding whether n8n fits your company at all, start with our guide to n8n for business and whether it suits you, then come back here for the licensing detail.

What is the n8n license?

n8n is not open source in the strict sense. Its source code is public on GitHub, but the core is published under the Sustainable Use License (version 1.0), a license n8n wrote itself. n8n calls its model "fair-code": you can see, run and modify the code, but commercial reselling of the product is reserved for n8n. The Sustainable Use License replaced the earlier Apache 2.0 with Commons Clause arrangement.

The license text is short. The key points:

  • You get a free, worldwide, non-exclusive right to use, copy, modify and distribute the software.
  • You may use or modify it only "for your own internal business purposes or for non-commercial or personal use".
  • You may distribute it to others only free of charge and for non-commercial purposes.
  • You may not remove or hide n8n's license, copyright or other notices.

There is a second layer. Any source file with ".ee" in its name or folder is not covered by the Sustainable Use License at all. Those files hold the enterprise features and sit under the separate n8n Enterprise License, which requires a paid license key to use in production.

What "internal business purposes" means in practice

The phrase sounds narrow, but n8n reads it generously. Running your own company's automations is the obvious case: syncing your CRM with your database, routing leads, sending invoices, enriching records with AI. That is all internal use, and it is free on the self-hosted Community edition no matter how big your company is or how much revenue those workflows touch.

The test n8n's help center applies is about who builds and controls the workflows, not whose money is involved. If only you and people in your organization create or edit workflows, you are inside the license.

What agencies and consultants can do

This is where most confusion sits, and n8n's help center is clear on it as of November 2026. According to n8n's support article on license use cases, a consultant or agency can:

  1. Build workflows for clients and charge for that work. Selling your time and expertise is not selling n8n.
  2. Run client workflows on your own n8n instance, as long as clients only receive the outputs and cannot open the workflow editor or change the workflow logic. Clients can connect their own accounts and credentials.
  3. Install and manage n8n on a client's own server, as long as you do not also host it for them. The client then picks its own plan or license.

In a December 2025 thread on n8n's community forum, a consultant who runs many clients' workflows on one instance shared n8n's support reply: delivering outcomes where clients never touch n8n counts as internal business purposes, and there is no set limit on the number of clients. That reply is second-hand, so treat it as a useful signal rather than a contract, but it matches the help center wording.

When we build n8n automations for clients, we usually recommend the third option: the client owns the instance (n8n Cloud or their own server), we build inside it, and they keep full control of their data and credentials. It keeps the licensing simple and avoids the client depending on a vendor's server for core operations.

What needs a commercial license

The line is crossed when n8n itself, rather than your work, becomes the product you sell. Based on the license text and n8n's help center, you need a commercial agreement with n8n if you want to:

  • Host n8n as a service and let clients log in and build their own workflows.
  • Let anyone outside your organization build or configure workflows, whether through the n8n editor, your own interface, the API, MCP or an AI agent. n8n's help center says this applies even if customers never see the n8n interface.
  • White-label n8n, meaning remove n8n's branding and offer it as your own tool.
  • Use features that need a license key, such as the enterprise features in the ".ee" files.

For years, the commercial route for embedding or white-labelling was sold as n8n Embed. As of November 2026, n8n's documentation describes embedding the editor in your own product as an OEM integration, which needs a separate commercial agreement negotiated with n8n through its licensing team. That OEM page also notes n8n branding stays in place, so do not assume a fully unbranded product is on offer without asking. The OEM page does not list pricing, so expect a quote from n8n.

Using n8n behind your own product

A common middle case: you run a SaaS app and want n8n to power a feature. n8n's OEM documentation draws a useful line. If your product only triggers workflows you built, through webhooks or the API, and your users never build or edit workflows, you do not need the OEM agreement. That "behind the scenes" model works under the standard plans.

The moment your users can design their own automations inside your product, even through your own interface or an AI chat that writes workflows for them, you are in Enterprise or OEM territory.

Enterprise features are a separate question

Even inside an allowed use case, some features are paid. n8n's documentation lists features that only unlock with a Business or Enterprise license key, including:

  • Projects and workflow and credential sharing
  • SSO through SAML or LDAP
  • Environments and version control with Git
  • External secrets and log streaming
  • Multi-main mode for high availability

There is also a free middle step. Registering your Community edition with an email unlocks folders, debug in editor and custom execution data at no cost. If you need team permissions, our post on n8n projects, roles and access control covers what each plan gives you.

A quick decision checklist

Ask these questions in order:

  1. Who builds and edits the workflows? Only your team: you are almost certainly fine on the free edition. Anyone outside your organization: you need a commercial license.
  2. Whose instance is it? Your own instance running client workflows that clients cannot edit is allowed. A client-owned instance that you manage is also allowed. Hosting n8n for clients as a paid platform is not.
  3. Is n8n branded as yours? If you remove or hide n8n's branding, you need a commercial agreement.
  4. Do you need enterprise features? SSO, Git environments, projects or log streaming require a paid plan whatever your use case.
  5. Still unsure? Email n8n's licensing team before you sign client contracts, and keep their written answer on file.

Self-hosted vs n8n Cloud

The license question applies mainly to self-hosting, because that is where you run n8n's code yourself. On n8n Cloud you are a customer on a paid plan and n8n's terms of service govern use. Licensing and cost often decide this choice together, so it helps to read our breakdown of self-hosting n8n and when it makes sense alongside a worked example of what n8n costs per year.

The practical takeaway

For most small and mid-size businesses, the n8n license is not a blocker. Automating your own operations is free on the Community edition. For agencies and freelancers, building and running workflows for clients is allowed, and the cleanest setup is usually a client-owned instance. Only when you want to turn n8n into a platform your clients log into, build on, or see under your brand do you need to talk to n8n's sales or licensing team.

If you want help choosing the right n8n setup, or want production-grade workflows built on an instance your business owns, take a look at our n8n workflow development services and book a call through the website. We will map your use case, flag any licensing questions early, and build something your team can run with confidence.

Related resources

Keep building the automation map

Move from the guide into the services and proof pages connected to this topic.