
n8n Community Edition is the free, self-hosted edition of n8n under the Sustainable Use License, and it carries what n8n's documentation calls "almost the complete feature set of n8n", queue mode included. n8n Enterprise is the paid plan n8n describes as "For organizations with strict compliance and governance needs". It runs on n8n Cloud or self-hosted and adds audit logging, log streaming, external secret stores, custom roles, sign-in through OIDC and dedicated support with an SLA, plus multi-main on a self-hosted instance. Between the two sits Business, a self-hosted plan with SSO through SAML or LDAP, shared projects, and environments and Git. n8n publishes no Enterprise price, and its pricing page lists Enterprise as "Contact Sales" with "Custom workflow executions".
The edition you need follows from what your security team requires before n8n touches production data. Community fits one team running internal workflows. Business fits when people must sign in through your company directory and changes must move through Git before they go live. Enterprise fits when audit events must reach your SIEM, credentials must stay in your vault, the editor must stay up when one main process fails, or a broken workflow needs support with a guaranteed response time.
Every self-hosted install runs the same product, and the license key sets which features it unlocks. The Community Edition "is what n8n runs without a license key", in the words of n8n's edition guide. Without a key you still get the workflow editor, every integration, the AI Agent node, the MCP Server Trigger and MCP Client, code steps, custom nodes, execution logging, error workflows, an encrypted credential store and queue mode, with unlimited users and unlimited concurrent executions, as the self-hosted columns of n8n's pricing page list them.
What the Community Edition leaves out is the set of controls for more than one team. It has no SSO, no projects, no environments or version control using Git, no external secrets and no log streaming, and it has no sharing, since "Only the instance owner and the user who creates them can access workflows and credentials." Registering the instance with an email address is free and adds folders, debug in editor and custom execution data, according to the same edition guide.
Business is self-hosted only, and n8n's pricing page describes it as "For companies with < 100 employees needing collaboration and scale". It adds SSO through SAML or LDAP, shared projects with admin, editor and viewer roles, credential sharing, environments and Git, global variables and external storage in S3. OIDC is the one sign-in option Business lacks: n8n's documentation marks SAML "Available on Business and Enterprise plans" and OIDC "Available on Enterprise plans."
Enterprise runs on n8n Cloud or self-hosted, and it is the only plan with audit logging and log streaming, which sends events to a syslog server, a generic webhook or a Sentry client. It is also the only plan with external secret stores, which read credentials from 1Password, AWS Secrets Manager, Azure Key Vault, GCP Secrets Manager, HashiCorp Vault or Infisical. Sign-in runs through SAML, LDAP or OIDC, with unlimited shared projects and custom roles, execution data redaction, two-factor authentication enforced across the instance and a view of running workers. Changes move through environments and Git with workflow diffs, and a self-hosted instance scales with queue mode and multi-main. n8n's guides to external secrets and log streaming mark both features Enterprise only.
Support follows the same line. Community and Business get the community forum, and Enterprise adds email support and dedicated support with an SLA, which n8n's pricing page defines as "direct access to our in-house team, with guaranteed response times available through SLAs." The same page says of Business: "The Business Plan is a self-serve option and dedicated support is supported only in our Enterprise plan."
| Community | Business | Enterprise | |
|---|---|---|---|
| Hosting | self-hosted | self-hosted only | on n8n Cloud or self-hosted |
| Sign-in | no SSO | SSO through SAML or LDAP | SAML, LDAP or OIDC |
| Sharing | the instance owner and the user who creates them | shared projects with admin, editor and viewer roles | unlimited shared projects and custom roles |
| Changes | no environments or version control using Git | environments and Git | environments and Git with workflow diffs |
| Logging | execution logging | execution logging | audit logging and log streaming |
| Secrets | an encrypted credential store | an encrypted credential store | external secret stores |
| Scaling | queue mode | queue mode | queue mode and multi-main |
| Support | the community forum | the community forum | dedicated support with an SLA |
| Price | free | a published price | Contact Sales |
n8n's source code carries two licenses. The Sustainable Use License, which n8n created in 2022, covers the main repository, and files with ".ee." in their name fall under the n8n Enterprise License. n8n calls the model fair-code, and its license page says "we do not call ourselves open source", because the Open Source Initiative does not accept limits on use.
The Sustainable Use License lets you use and modify n8n "only for your own internal business purposes or for non-commercial or personal use", and distribute it only "free of charge for non-commercial purposes". n8n's license FAQ states the test plainly: "If workflows are only created or modified by you or people in your organization, you can use n8n under the Community license for free." Under it you can run n8n for your business, build automations for clients on your own instance as long as they cannot create or edit them, run n8n behind the scenes in your own product, and charge for building, setting up and maintaining workflows.
The same FAQ rules out hosting n8n as a service where your clients build workflows, letting external users "build or configure their own workflows through your product, whether via a custom UI, our API, MCP, or an AI agent acting on the user's behalf", forking n8n to launch your own automation product, and white-labeling it. For a use the license does not permit, n8n's license page says "You must sign a separate commercial agreement with us", and for an embedded workflow builder the FAQ points to "an Enterprise license, which is designed for this architecture."
The paid features come with a license key. Subscribing to Business or Enterprise "gives you a license key that unlocks the features for that plan", in the words of n8n's edition guide. The n8n Enterprise License says its code "may only be used in production" if you "hold a valid n8n Enterprise license corresponding to your usage", while copying and modifying it "for development and testing purposes" needs no subscription. The license FAQ lists using "enterprise features that ask for a license key without an Enterprise license" among the things the Community license does not allow.
The license also leaves room for outside help. Since n8n moved off Apache 2.0 with Commons Clause in March 2022, its license page says, "you are now free to offer commercial consulting or support services (e.g. building n8n workflows) without the need for a separate license agreement with us."
n8n publishes no Enterprise price. Its pricing page lists Enterprise as "Contact Sales" with "Custom workflow executions", says "Enterprise overage fees are set in your order form", and offers pay by invoice and sales assisted procurement on Enterprise alone. Business has a published price, "667€ /mo, billed annually" for "40K workflow executions" on the page as read on 20 November 2026, and n8n aims it at companies with fewer than 100 employees.
The published plans show the unit n8n prices by: "All plans include unlimited users and workflows and every integration. Pricing is based on monthly workflow executions, regardless of complexity." Headcount does not set the price. Come to the sales call with the production executions you expect a month, whether n8n hosts the instance or you self-host it, and the Enterprise-only controls your security review requires, such as audit logging, log streaming, external secret stores or dedicated support with an SLA. On a self-hosted instance the license key "must ping our license server daily to stay active", and the ping "includes data like the number of production executions, which helps us track usage", in the words of the same pricing page.
A self-hosted Enterprise instance also runs on infrastructure you pay for and operate. n8n's hosting guide lists maintenance of a self-hosted instance as "Your responsibility", so the license fee and the cost of running the servers are two separate lines in the budget.
Start from the requirements your security team will not waive, and take the lowest edition that carries all of them, Community before Business before Enterprise. Company sign-in through SAML or LDAP, shared projects and Git point to Business. Audit logging, log streaming, external secret stores, custom roles, OIDC, multi-main or dedicated support with an SLA point to Enterprise. If your customers would build or edit their own workflows, the question is the license, and n8n points to an Enterprise license for that.
Ovidius deploys n8n Business or Enterprise in your cloud account and helps you choose the right plan before you talk to n8n sales. We first estimate how many workflow runs (executions) you expect and list your security requirements, so you buy Business or Enterprise only when you need it.
n8n says it is not. Its source code is available under the Sustainable Use License, which limits use to your own internal business purposes or non-commercial and personal use, and the Open Source Initiative does not accept limits on use, so n8n's license page says "we do not call ourselves open source". n8n calls the model fair-code: the source code is openly available and can be extended by anybody, and its authors restrict commercial use.
Yes, a company can run it free for its own internal use. n8n's license FAQ says: "If workflows are only created or modified by you or people in your organization, you can use n8n under the Community license for free." You can run several instances, build automations for clients on your own instance as long as they cannot create or edit them, and charge for building and maintaining workflows. Hosting n8n so that clients build their own workflows needs a separate agreement with n8n.
SSO is on the paid plans only. A self-hosted Business plan supports SSO through SAML or LDAP, and Enterprise adds OIDC, which n8n's documentation marks "Available on Enterprise plans." The free Community Edition has no SSO, so people sign in with n8n accounts, and only the instance owner and the user who creates a workflow or credential can access it.
Yes, the Community Edition runs queue mode. n8n's edition guide lists it as included in the Community Edition, and the self-hosted columns of n8n's pricing page show it on Community, Business and Enterprise alike. Multi-main, which keeps the editor up when one main process fails, is the Enterprise-only part of scaling, together with the view of running workers.
The Sustainable Use License does not allow it. Its FAQ rules out letting external users "build or configure their own workflows through your product, whether via a custom UI, our API, MCP, or an AI agent acting on the user's behalf." Customers may trigger automations you built and connect their own accounts to them. For an embedded workflow builder, n8n points to "an Enterprise license, which is designed for this architecture."
A Business or Enterprise license key "must ping our license server daily to stay active", according to n8n's pricing page, and the ping includes the number of production executions. You can apply a key to an unlimited number of instances, and their combined usage counts toward your quota. If you go over it, workflows keep running and overage charges may apply.
Choosing between Business and Enterprise? Book a discovery call. A senior partner leads your workflow from the first call, and on the call you talk to the people who would do the work.