Is n8n Free and Open Source? The Licence and the Costs Explained

Last verified: October 2026

By Rick Kennerknecht, NoCode Guide

November 10, 2026

Is n8n open source: an open padlock beside a licence scroll, with a dividing line between a free and a paid section

Last verified: October 2026

n8n is not open source by the usual definition. It is "fair-code", distributed under the Sustainable Use License, which lets you read, modify and self-host the software free of charge for your own internal business or personal use, but not resell it as a service. The Community Edition is free with no execution caps; n8n Cloud and Enterprise are paid.

That answer satisfies almost nobody on the first read, because "open source" is doing two jobs in the question. One is "can I see the code and run it for free?" (yes). The other is "does it carry an OSI-approved licence like MIT or Apache?" (no). The rest of this post separates those, quotes the actual licence, and lays out exactly what is free.

Is n8n open source? Fair-code versus open source

The n8n GitHub README describes the project as "fair-code distributed under the Sustainable Use License and n8n Enterprise License", and as "Source Available" with "Always visible source code". It does not use the words "open source" in its licence section, and that is deliberate.

The Open Source Initiative's definition requires, among other things, that a licence not restrict anyone from using the software in a specific field of endeavour and not discriminate by purpose. The Sustainable Use License restricts commercial redistribution. So it fails the OSI test on purpose, in exchange for a business model that funds development: n8n GmbH sells Cloud hosting and Enterprise licences, and the licence stops a competitor from taking the code and selling it as their own hosted product.

"Fair-code" is the label n8n uses for this arrangement. In practice it means: the full source is on GitHub, you can clone it, read it, build it, patch it and run it, and you can do all of that for free as long as you are using it yourself rather than selling it to others.

Whether that distinction matters to you depends on what you want to do. For the large majority of people searching "n8n open source", who want to self-host it for their own company or side project, it does not matter at all. For a hosting company, an agency planning to resell managed n8n, or a product team that wants to embed it, it matters a great deal.

What the Sustainable Use License permits and forbids

The licence is short, and the key paragraph from the LICENSE.md in the n8n repository reads:

"You may use or modify the software only for your own internal business purposes or for non-commercial or personal use. You may distribute the software or provide it to others only if you do so free of charge for non-commercial purposes. You may not alter, remove, or obscure any licensing, copyright, or other notices of the licensor in the software."

The grant itself is broad: a non-exclusive, royalty-free, worldwide licence to use, copy, distribute, make available and prepare derivative works, subject to those limitations. Here is how that plays out for the situations people actually ask about.

What you want to doPermitted under the Sustainable Use License?
Self-host n8n and run your own company's automations on itYes: internal business purposes
Run n8n for a personal project or hobbyYes: personal use
Read, fork and modify the source codeYes, subject to the same use limits and keeping the notices intact
Build workflows for a client inside the client's own n8n instanceYes: the client is using it for their internal business
Charge clients for consulting and workflow-building workYes: you are selling your labour, not n8n
Give a modified copy of n8n to someone else for free, non-commerciallyYes, explicitly allowed
Sell managed n8n hosting to the publicNo: that is providing the software to others for a charge
Embed n8n inside your own paid product and sell accessNo without a commercial agreement with n8n
Strip the n8n branding and licence noticesNo
Use code in files or folders marked .eeNo without an Enterprise licence

The grey zone is a multi-tenant setup where you run one n8n instance and let paying customers log into it. That reads as providing the software to others for a charge, and the honest advice is to ask n8n GmbH before building a business on it. Building automations for clients, by contrast, is the normal agency model and sits comfortably inside "internal business purposes", because each client is using n8n for their own operations.

The licence also includes a patent grant, with the usual clause that your patent licence ends if you claim the software infringes a patent of yours. Standard stuff, but it is in there.

The Enterprise files: what .ee means

The repository is not uniformly licensed. The licence file states that source files with .ee. in the filename or .ee in the directory name are not covered by the Sustainable Use License, and that using them requires a valid n8n Enterprise License as defined in LICENSE_EE.md.

Those files implement the paid features. The Community Edition features page lists what the free edition does not include: SSO, environments, external secrets, log streaming, projects, sharing of workflows and credentials, Git-based version control, custom variables, external binary storage and multi-main mode. Everything else, which the page describes as almost the complete feature set, is free. Registering a free community account also switches on folders, debug in editor and custom execution data.

The paid code ships in the same Docker image as everything else, which is why the Community Edition can show you a feature in the UI that is greyed out until a licence key is entered. You are not supposed to patch around that, and the licence says so.

Is n8n free? Community Edition, Cloud and Enterprise

Three products, one codebase.

Community Edition is the self-hosted software under the Sustainable Use License. It is free. There is no execution cap, no workflow cap, no user cap, and no time limit. What it costs is a server and your time, which the self-hosting guide puts numbers on. This is the edition most people mean when they say "n8n is free", and for that edition the statement is accurate.

n8n Cloud is the hosted service. Paid, priced in euros, with a 14-day trial and no free tier. Starter is €20 a month on annual billing for 2,500 executions; Pro is €50 for 10,000. The n8n Cloud explainer covers plans and limits; the n8n pricing page keeps the figures current.

Enterprise is a paid licence that turns on the .ee features, on Cloud or self-hosted. Contact sales, custom pricing.

Running the free edition takes about this much configuration. Pin the version tag; n8n 2.0 renamed latest to stable and recommends pinning anyway.

services:
  n8n:
    image: n8nio/n8n:2.43.7
    restart: unless-stopped
    ports:
      - "127.0.0.1:5678:5678"
    environment:
      - N8N_HOST=n8n.example.com
      - N8N_WEBHOOK_URL=https://n8n.example.com/
      - GENERIC_TIMEZONE=America/Denver
      - TZ=America/Denver
    volumes:
      - n8n_data:/home/node/.n8n
volumes:
  n8n_data:

That is the whole free product. The Docker install guide adds the reverse proxy, task runners and Postgres for a production setup, but nothing in that longer version costs a licence fee.

Why "is n8n open source" is usually the wrong question

The question people are actually asking is one of these four, and each has a cleaner answer.

"Will it cost me money to run?" Only the server. For most small teams that is a VPS in the ten-to-thirty-dollar range per month, with no per-execution charge.

"Can I get locked in?" Less than with most tools. Workflows export as JSON, the database is SQLite or Postgres on your own disk, and the source is public. If n8n GmbH vanished tomorrow, your instance would keep running and the code would still be on GitHub under a licence that permits you to keep using it.

"Can I trust the code?" You can read all of it, which is more than most automation vendors offer. Whether you do is another matter.

"Can I build a business on it?" Yes, if the business is automation work for clients. No, if the business is selling n8n itself. The what is n8n page covers what the tool does if you are still at that stage.

If an OSI-approved licence is a hard requirement, for example because your company policy says so, then n8n is out and the question becomes which alternative. Activepieces is MIT-licensed for its Community Edition (with its own commercial folder, packages/ee, mirroring n8n's approach), Node-RED and Kestra are Apache-2.0, Windmill's core is AGPLv3 and Temporal is MIT. The n8n alternatives page compares them by what they are good at, and the licence column is there for the people who need it. Which raises the point that matters for everyone else: an OSI licence is not the same as a free product. Several of those tools also sell cloud tiers and enterprise features, exactly as n8n does, just under a different licence text.

The practical summary

Self-host the Community Edition for your own use and you pay nothing to n8n, ever, with no caps. Do that for clients, inside their instances, and you are still within the licence. Sell n8n itself, as hosting or as part of a product, and you need a commercial agreement. Need the greyed-out features, and you need Enterprise. Want no server at all, and you pay for Cloud.

Whether to run it yourself or pay for hosting is a separate decision from the licence, and the n8n Cloud vs self-hosted page works through it with the execution math. The licence will not stop you either way. It only stops you from becoming n8n's competitor using n8n's code, which, as licence restrictions go, is a reasonable one to live with.

Frequently asked questions

Related guides

We use cookies for analytics to understand how our guides are used. You can decline non-essential cookies.