Is n8n free? Community vs enterprise limits
Self hosted n8n is free under a fair code licence with real limits. What you may do, which features need a paid key, and where cloud plans fit.
Is n8n free to self-host?
Yes, n8n is free to self-host. You run the community edition on a server you own, and the licence sets no limit on how many workflows you build or how often they run. Two things decide whether that free edition is enough for you: n8n is not open source in the sense the Open Source Initiative (OSI) uses that term, and a specific set of features stays switched off until you pay for a licence key.
The licence is the Sustainable Use License, version 1.0. The source code is public, and you may read it, run it and change it. What the licence restricts is how you may use it. You may run n8n for yourself or for your own company, and you may run it behind the scenes of a product you sell. You may not host it as a service where your customers build or configure their own workflows.
What fair-code means, and why n8n is not open source
Fair-code is the label n8n uses for its own model. It describes software whose source is public and freely runnable, but whose commercial use the author restricts. n8n's documentation gives the reason for the wording directly: an OSI-approved open source licence cannot include limits on how you use the software, and the Sustainable Use License contains exactly that kind of limit, so n8n does not call itself open source.
That distinction is not an argument about words. It reaches your procurement team. A policy that reads "we deploy open source tools, or tools we have bought" leaves n8n in a third category, so somebody has to make a real decision about it. Read the licence file in the n8n repository before that conversation rather than after it.
What the Sustainable Use License lets you do
The permission grant itself is broad. The licence gives you a non-exclusive, royalty-free, worldwide licence to use, copy, distribute, make available and prepare derivative works of the software, for internal business purposes or for personal non-commercial use.
In practice that covers:
- Running n8n on your own server for your own company, for example syncing data from a CRM (customer relationship management system) into an internal database.
- Running it at home for personal projects.
- Changing the code, and running your modified version.
- Selling consulting work, such as building workflows for a client.
- Building and running automations for clients on your own instance, as long as the clients cannot create or edit them.
- Selling support, such as setting up and maintaining n8n on servers a client owns.
- Using n8n behind the scenes in your own product, where users run and trigger the automations you built and may connect their own accounts to them, as long as they cannot open the workflow builder or configure the workflow logic.
Nothing in the licence meters your usage. There is no execution quota and no seat count on the community edition, so its capacity depends on your infrastructure. The AI nodes are not gated either, so building an AI agent workflow in n8n works on the free edition.
What the Sustainable Use License does not let you do
The restrictions are short, and n8n lists them with examples in its licence FAQ:
- Hosting n8n as a service and letting your clients build workflows on it.
- Letting external end users build or configure their own workflows through your product, whether through a custom interface, the n8n API, MCP or an AI agent acting for them.
- Forking n8n's code to launch your own automation product.
- White labelling n8n by removing its branding and offering it as is.
- Using enterprise features that ask for a licence key without an Enterprise license.
The licence text adds two more. You may not alter, remove or obscure any licensing, copyright or other notice, and you may distribute the software only free of charge and for non-commercial purposes.
The second restriction is the one that surprises people, so read it twice. A billing job that moves your company's own data using your company's own API keys is internal use, and it is allowed. A product where each of your customers connects their own Google account to automations you built is allowed too, as long as those customers cannot open the workflow builder or change the workflow logic. Let the same customers design their own automations, even through your own interface or the n8n API, and it is not allowed, because the licence draws its line at who controls the workflow logic, not at whose credentials n8n is holding. The software and the server can be identical in the last two cases. The answer is not.
There is also a second licence inside the same repository. Any source file with .ee. in its filename, or .ee in its directory path, sits outside the Sustainable Use License and is covered by the separate n8n Enterprise License. That code ships inside the same Docker image you pull, so the paid features are present in the build and stay switched off until a valid key activates them. Switching them on any other way is a licence violation, not a configuration trick.
How fair-code differs from MIT and AGPL
An MIT licence permits almost everything, including taking the code and selling a hosted version of it. Its one real condition is that the copyright notice and the permission notice stay in all copies or substantial portions of the software.
The AGPL (GNU Affero General Public License) also permits selling a hosted version, and it places no limit on who you may serve. Its condition is disclosure: if you modify the software and let users reach it over a network, you must offer those users your modified source.
The Sustainable Use License works on a different axis. It asks nothing about publishing your changes. It restricts how you may use the software, and who may control the workflows you run with it. The short summary is that the AGPL controls what you must publish, and the Sustainable Use License controls what you may sell.
That difference decides what happens to forks. Anyone may fork an AGPL project and run it as a competing hosted service, provided they publish their changes. Nobody may do that with n8n, because the use restriction travels with the code into every copy of it. This is why n8n can publish its entire source and still sell a cloud product without competing against a clone of itself.
Which features need a paid licence key
The community edition contains almost the whole product. n8n documents the exclusions rather than the inclusions, which is the more useful way round. As of October 2026 the compare editions page lists these as paid:
- SSO (single sign-on) through SAML (security assertion markup language) or LDAP (lightweight directory access protocol)
- Sharing of workflows and credentials
- Projects
- Custom variables
- Environments
- Version control using Git
- External secrets
- External storage for binary data
- Log streaming
- Multi-main mode
Sharing is the limit most teams meet first, and it is easy to miss while one person evaluates the tool alone. On the community edition, only the instance owner and the user who created a workflow or credential can open it. Two colleagues on the same instance cannot pass a workflow to each other inside the interface. Teams work around this with one shared login, which removes any record of who changed what.
SSO is the second. If your company requires single sign-on for every internal tool, the community edition fails that requirement on day one, whatever else it can do. The pattern of a free self-hosted app whose authentication feature is the paid one repeats across this whole category, and the SSO tax in self-hosted apps explains why vendors keep drawing the line in the same place.
Environments and Git version control are one feature in practice. Together they let you keep workflows in a repository and promote them from a development instance to a production one. Without them, you can move workflows between instances by exporting and importing JSON through the interface, CLI or API. That works, and plenty of people do it. This does not provide Git history; the community edition still keeps workflow versions from the last 24 hours.
Multi-main mode is the one that limits scale. Queue mode with several worker processes runs fine on the community edition. Running more than one main process does not, and the main process owns schedules and webhooks, so it stays a single point of failure that you cannot make redundant without a key.
Log streaming and external secrets are compliance features. Log streaming pushes n8n's event log into a system you already watch. External secrets reads credentials from a vault instead of n8n's own encrypted store. Both are the kind of thing a security review asks for months after the tool reached production, which is an awkward moment to discover the price.
If the gated feature is the one you actually need and the plan is out of budget, compare tools instead of fighting the licence. The self-hosted n8n alternatives are worth reading side by side, because each project draws its own free line in a different place.
Register your community instance for the free licence key
Some free features still need a licence key, which sounds contradictory until you see the flow. Registering an email address gets you a free key. It unlocks three more capabilities at no cost:
- Folders, for organising workflows
- Debug in editor, which copies and pins execution data while you work on a workflow
- Custom execution data, for saving and annotating execution metadata
To get the key:
- Open the three dots menu in the lower left corner of the editor.
- Go to Settings, then Plan & usage.
- Select Unlock, enter your email, then select Send me a free license key.
- Activate the key with the button in the email, or select Enter activation key on the same Plan & usage page, paste it in and select Activate.
On a server you configure from files, skip the interface and set the key as an environment variable before the first start.
docker volume create n8n_data
docker run -it --rm --name n8n -p 5678:5678 \
-e N8N_LICENSE_ACTIVATION_KEY="paste-your-key-here" \
-v n8n_data:/home/node/.n8n docker.n8n.io/n8nio/n8nOpen the editor on port 5678, then check Settings, then Plan & usage. That page should name your plan instead of showing the unlock prompt. If the prompt is still there, the usual cause is that the instance was activated before: N8N_LICENSE_ACTIVATION_KEY has no effect on an instance that already holds a licence, so adding it to an existing container's environment can look like it did nothing at all.
Two more licence variables matter on a production box. N8N_LICENSE_AUTO_RENEW_ENABLED defaults to true. Set it to false and you have to renew by hand from the settings menu every ten days, or the licensed features stop working. N8N_LICENSE_DETACH_FLOATING_ON_SHUTDOWN also defaults to true, which releases the entitlement when the instance shuts down so another instance can claim it. On a production instance that restarts during deployments, set it to false so the licensed features come back with it. n8n ignores this second variable in multi-main mode. Both are documented, with their defaults, on the licence environment variables page.
Where the cloud plans sit
n8n Cloud runs the same software on n8n's own infrastructure. The plans are metered by workflow executions rather than by the number of active workflows, so a workflow that sits idle waiting for a webhook costs nothing until it fires.
The detail that matters to a self-hoster is that the enterprise licence key comes attached to a plan rather than sold on its own. You buy a Business or Enterprise plan, you receive a key, and you paste that key into the instance running on your own hardware. Self-hosting and paying are not opposites.
As of October 2026, the Starter, Pro and Business plans carry published prices on the n8n pricing page, quoted per month on annual billing. Business is self-serve and currently sold for self-hosted n8n only, which makes it the direct way to buy a key for your own server. Enterprise goes through the sales team and its pricing is not published at all. Any figure printed here would go stale, so read the page itself, and for Enterprise ask for a quote and ask specifically whether that quote includes the self-hosted key.
If you are still deciding between running it yourself and paying for a hosted automation product, the comparison of n8n against Zapier and Make works through the cost shape rather than the feature list.
Selling n8n inside your own product
If your customers will see and use the n8n editor itself, you need n8n's OEM integration, a separate commercial agreement that lets you embed n8n's interface inside your own product's UI. As of October 2026 the OEM integration docs list no price, so terms come from talking to n8n, and they state that n8n branding is required as part of an OEM integration. It is a route to embedding the editor, not to white labelling it.
Using n8n as a hidden backend is a different case. If you build the workflows and your users only run them, trigger them or connect their own accounts to them, the standard licence covers it and no agreement is needed. If your users can build or configure automations, n8n's help centre says the product needs an Enterprise license even if your customers never see the n8n interface, and the licence FAQ names a custom interface, the n8n API, MCP and AI agents acting for the user as routes that count. The dividing line is who controls the workflow logic, not the credentials and not the revenue.
So which edition do you need?
For one company running its own automations without workflow or credential sharing between colleagues, the community edition is enough. Register for the free key and go and build something. The next step is a server, and self-hosting n8n on a VPS with Docker and HTTPS covers the deployment, the reverse proxy and the certificate.
For a company that requires single sign-on, or separate environments for development and production, the community edition will not get there, and no amount of configuration changes that. Price a Business plan, or pick a tool whose licence matches your budget.
For anyone selling access to n8n itself, or a product where customers build their own workflows, the answer is a commercial agreement with n8n. The sooner that conversation happens, the cheaper it is.
FAQ
Is n8n open source?
No. n8n is fair-code, distributed under the Sustainable Use License. The source is public and you may read, run and modify it, but the licence restricts what you may use it for, and an OSI-approved open source licence cannot contain restrictions on use. n8n says this in its own documentation and describes itself as source available instead. Files with .ee. in the name or .ee in the path are excluded even from that licence and fall under a separate n8n Enterprise License.
Can I charge clients money for work involving n8n?
Yes, for services. Building workflows for a client needs no separate agreement, and neither does installing or maintaining n8n on servers the client owns. You may also build and run automations for clients on your own instance and charge for that work, as long as the clients cannot open the workflow editor or change the workflow logic. What you cannot do is host n8n as a service where clients build their own workflows, or sell a white-labelled version of it. The test is client access to the workflows, not the number of clients or the revenue.
Why can my team not share workflows on the self-hosted community edition?
Sharing of workflows and credentials is a licensed feature, so it is switched off without a paid key. On the community edition, only the instance owner and the user who created an item can open it, which means there is no way to hand a workflow to a colleague inside the interface. Exporting the workflow as JSON and importing it under the other account works, but credentials do not travel inside that export, and the imported copy becomes a separate workflow with its own execution history.
What happens if my n8n instance cannot reach the licence server?
An activated instance renews its licence against https://license.n8n.io/v1 by default, and N8N_LICENSE_AUTO_RENEW_ENABLED is true out of the box. If you turn automatic renewal off, you have to renew by hand from the settings menu every ten days, or the licensed features stop working. If an outbound firewall blocks the licence server, send the request through a proxy with the lowercase https_proxy_license_server variable rather than disabling renewal.
Do I have to pay to remove the n8n branding?
At minimum yes, if customers will see the result, and paying may not be enough. The Sustainable Use License forbids altering, removing or obscuring licensing and copyright notices, and n8n's licence FAQ lists white labelling n8n by removing its branding as a use it does not permit. The help centre says white labelling needs a commercial licence, while the OEM integration docs say n8n branding is required as part of an OEM integration, so get n8n's answer in writing before you plan a rebrand. Adjusting the look of an instance only your own staff use is a smaller question, but the clause about licensing and copyright notices applies whatever the audience.