n8n Community, Cloud, Business, Enterprise: which plan for whom?

n8n comes in four variants: the free Community edition for self-hosting with no execution limit, the Cloud plans Starter and Pro from 20 or 50 euros per month respectively, the Business plan for self-hosting with support from 667 euros per month, and Enterprise with individual pricing. The honest answer for most SMEs upfront: the Community edition fully covers everyday automation, with n8n you mainly pay for team and governance features, not for more automation power. As of: July 2026, prices according to the n8n pricing page.

What specifically differentiates the plans?

• Community (self-hosted, free): all nodes, all integrations, unlimited workflows and executions. With a free registration key, folders, debug functions and execution history are added.
• Cloud Starter (20 EUR/month): 2,500 executions per month, 5 concurrent executions, 1 day of history. n8n takes care of operations and updates, hosted in Frankfurt.
• Cloud Pro (50 EUR/month): 10,000 executions, 20 concurrent, longer history. For growing teams without the desire to run their own servers.
• Business (from 667 EUR/month, self-hosted): 40,000 executions, plus SSO/SAML and LDAP, Git-based environments, external secrets and support.
• Enterprise (individual pricing): everything from Business plus log streaming, advanced roles and projects, 365+ days of history and Enterprise support.

Which features are really reserved for the paid plans?

The line is not drawn at automation, but at team governance: single sign-on via SAML or LDAP, Git versioning with separate environments for development and production, external secret stores such as Vault, log streaming into a SIEM, and fine-grained projects and roles are only available from Business or Enterprise. Anyone who has never needed these terms in operations most likely does not need them in n8n either. The Community edition has a pragmatic substitute for this: export workflows as JSON and back them up in your own Git repository, manage credentials via environment variables.

When does an SME really need Enterprise?

The paid plan makes sense in three situations. First, when compliance requirements demand SSO and centralized rights management, typically from around 50 automation users or in regulated industries. Second, when multiple teams work on workflows in parallel and need separate development and production environments with a clean deployment process. Third, when a support contract with response times is required. Below these thresholds, an SME paying for Business from around 8,000 euros a year is mainly paying for functions it does not use. The more economical route then is usually: Community edition on your own German server, professionally set up and maintained, with a service provider as a safety net instead of a license agreement.

Cloud or self-hosting: the cost calculation

A calculation example over three years: Cloud Pro costs 1,800 euros, a suitable German server for the Community edition costs 200 to 700 euros depending on size, plus a one-time cost for clean setup with HTTPS, backups and updates. From medium usage onward, self-hosting is significantly cheaper and has no execution limits, but you bear the operations yourself. We handle exactly this setup as an n8n service at a fixed price, including the question of whether Cloud or your own server fits your data protection requirements. How n8n performs overall against the competition is covered in the big tool comparison.

Frequently asked questions about n8n plans and licenses

Is the n8n Community edition really free, even for companies?

Yes, the Community edition is also free for commercial use within your own company, governed by the Sustainable Use License. What is essentially not allowed is reselling n8n itself as a paid hosting product. Internal automation, including business-critical automation, is explicitly permitted, and executions are unlimited.

How does n8n count executions, and why is that cheaper than with Zapier?

n8n counts complete workflow executions, regardless of how many steps they contain. Zapier and Make, on the other hand, bill per individual step, so a 20-step workflow costs twenty times as much there. For more complex automations, the execution model is therefore structurally cheaper, and self-hosted, the counting is eliminated entirely.

Do I lose my workflows when switching from n8n Cloud to self-hosting?

The workflows, no, they can be exported and imported as JSON. The stored credentials, however, yes: credentials are encrypted with an instance-specific key and must be recreated on the new instance. Webhook URLs also change and must be updated in the connected systems, so plan the move as a small project.

Does the Community edition get the same updates as the paid versions?

Yes, the Community edition is developed from the same source code and continuously receives the same core updates, new nodes and bug fixes. The differences lie in the license-required add-on modules such as SSO or environments, not in how up to date it is. When self-hosting, the only important thing is a clean update process with backups, so that a version jump does not become a risk.