n8n Review 2026: Cloud vs Self-Hosted, Costs, and Buyer Fit
n8n review 2026: compare Cloud pricing, Community self-hosting, execution limits, license restrictions, security, support, and buyer fit.
Limits: We did not create an n8n Cloud account, deploy Community Edition, build workflows, measure reliability, or test support response times. Prices and limits are public list terms viewed in euros with annual billing selected; taxes, overages, negotiated terms, infrastructure, and third-party API charges are excluded. Security and compliance statements are vendor claims from n8n's published documentation and were not independently audited by us.
n8n is a strong choice for technical teams that value complex workflows, execution-based billing, and a real self-hosting option. The recommendation is conditional because Community shifts operations to the buyer, omits important governance features, and uses a commercially restricted source-available license.
- Technical teams that want code-capable visual automation and deployment choice
- Internal automation where multi-step workflows benefit from per-execution rather than per-step billing
- Operators prepared to own a self-hosted database, backups, patching, monitoring, and recovery
- Your team needs a fully managed no-code product with technical support below Enterprise
- You need SSO, shared projects, external secrets, Git environments, or multi-main availability at Community pricing
- You plan to resell hosted n8n access or collect customer credentials without written commercial terms
On this page
n8n is a visual workflow automation platform built for teams that want more control than a typical no-code connector. It combines a node-based editor with code steps, webhooks, API access, custom nodes on self-hosted deployments, and a choice between n8n Cloud and software you operate yourself. The Cloud plans meter complete workflow executions rather than individual steps. [S1][S2]
That flexibility creates the central buying trade-off. n8n Cloud removes infrastructure work but applies plan limits. Community Edition removes the software subscription and gives you deployment control, but it makes your team responsible for security, updates, storage, monitoring, and recovery. [S2][S6]
Bottom line
Verdict: conditional. n8n belongs on the shortlist for technical teams building complex internal automations, especially when self-hosting or per-execution billing matters. Community Edition offers most core product capabilities without a license fee, while Starter and Pro provide a managed route with predictable published allowances. [S1][S3]
The conditions matter. Community is not the complete enterprise product for free: projects, workflow and credential sharing, SSO, environments, external secrets, log streaming, external binary storage, multi-main mode, and Git version control require paid editions. The source is available, but the Sustainable Use License restricts some customer-facing and resale uses. [S3][S4]
This is a desk-research review based on n8n’s current pricing, product, operations, license, security, and support documentation. We did not run the product or measure performance.
n8n pricing in 2026
The public pricing page displayed these annual-billing prices on September 21, 2026: [S1]
| Plan | Deployment | Published price | Included production usage |
|---|---|---|---|
| Community | Self-hosted | EUR0 software fee | Customer-controlled infrastructure and retention |
| Starter | n8n Cloud | EUR20/month billed annually | 2,500 executions, 5 concurrent executions, 1 shared project |
| Pro | n8n Cloud | EUR50/month billed annually | 10,000 executions, 20 concurrent executions, 3 shared projects |
| Business | Self-hosted | EUR667/month billed annually | 40,000 executions, 6 shared projects, SSO, environments, and Git version control |
| Enterprise | Cloud or self-hosted | Custom quote | Custom executions, 200+ concurrency, advanced governance, and dedicated support with SLA |
All listed plans include unlimited users, workflows, integrations, and workflow steps. Those words do not mean unlimited workload: Cloud still caps monthly executions, production concurrency, saved executions, storage, and retention according to plan. [S1]
An execution is one complete run of a workflow, regardless of its step count. That can be favorable for a long workflow that would consume many operations or tasks on another platform. It is less favorable when a high-frequency trigger creates thousands of short runs. Estimate monthly trigger events and resulting workflow executions rather than comparing headline prices alone. [S1]
Concurrency and retained history
Starter allows five concurrent production executions and Pro allows 20. The concurrency rule applies to executions started by trigger or webhook nodes; manual, sub-workflow, and error executions do not consume that regular Cloud limit. Runs above the limit wait in a first-in, first-out queue rather than failing immediately. [S1][S5]
The pricing page also separates workflow-version history from execution history. Starter lists one day of workflow history and Pro five days. Saved execution data is removed when the first plan limit is reached, whether that is the count, storage allowance, or retention window. Buyers who need long debugging windows should model retained data, not only monthly runs. [S1]
Cloud or self-hosted?
n8n Cloud is the straightforward route when the team does not want to install or maintain the platform. n8n manages hosting, updates, and scaling. Self-hosting gives you control over the environment and configuration, but installation, infrastructure, maintenance, and scaling become your responsibility. n8n explicitly recommends Cloud for buyers without technical expertise and self-hosting for buyers with infrastructure resources or custom deployment requirements. [S2]
Community Edition is free indefinitely and includes almost the complete feature set. Registering a Community instance by email adds folders, debug-in-editor, and custom execution data at no charge. Queue mode and standard logging are included. [S3]
The missing controls are material for teams. Community does not include projects, shared workflows and credentials, SAML or LDAP SSO, environments, external secret stores, external binary storage, log streaming, multi-main mode, or Git-based version control. Without sharing, only the instance owner and the user who creates an item can access its workflows and credentials. [S3]
The real cost of Community Edition
The software license fee can be zero while the service still has a meaningful operating cost. A production owner needs to provide compute, a database, persistent storage, TLS, encryption at rest, monitoring, upgrades, capacity planning, backups, and incident recovery. [S2][S7]
n8n’s backup documentation is specific about what recovery requires. A complete backup includes the .n8n folder because it holds configuration and the credential encryption key, plus PostgreSQL when used, external binary or execution storage, and custom-node directories. Workflow and credential exports alone omit users, roles, execution history, variables, settings, and the encryption key. [S6]
This makes self-hosting a good fit only when someone owns those duties. A low-cost server is not a complete total-cost estimate if no one has tested restore procedures, patching, certificate renewal, alerting, or database recovery.
License boundaries
n8n is source-available under its Sustainable Use License, which n8n describes as fair-code rather than OSI open source. The license permits internal business use, personal and non-commercial use, modification, and certain redistribution. It also permits consulting, workflow development, setup, and maintenance for a customer’s internal server. [S4]
The main restrictions affect product companies and managed-service ideas. The Community license does not permit white-labeling n8n for paying customers or charging people for access to hosted n8n. A customer-facing backend is generally allowed only when it does not collect end users’ credentials; n8n’s own examples distinguish a chatbot using the operator’s credentials from a service collecting each user’s HubSpot credentials. Uses outside the published boundaries require a separate commercial agreement. [S4]
For ordinary internal automation, the license is comparatively clear. For embedded automation, managed hosting, or a SaaS feature that handles customer credentials, obtain written confirmation from n8n rather than treating source availability as unrestricted commercial permission.
Security and support
n8n says its Cloud service runs on Microsoft Azure in the European Union, encrypts traffic in transit, and encrypts customer data, credentials, databases, and backups at rest with Azure server-side AES-256 encryption. It publishes SOC-oriented controls; the detailed SOC 2 report is available to Enterprise customers and a SOC 3 report is public. These are supplier statements, not tests performed for this review. [S7]
Self-hosting changes the responsibility line. n8n hashes account passwords, but self-hosters must configure TLS through a reverse proxy and arrange encryption at rest. Infrastructure control can help satisfy an architecture requirement, but it does not itself create secure configuration, compliance, recovery capability, or an incident-response process. [S7]
Support is another plan gate. All users can use the community forum. Standard Cloud plans can email n8n about billing and administration, but technical support is directed to the forum. Cloud and self-hosted Enterprise receive email support with an SLA; public documentation does not state the response targets, so buyers should confirm them in the contract. [S1][S8]
Pros and cons
Pros
- Charges per completed workflow execution rather than per step [S1]
- Managed Cloud and a genuine self-hosted Community option [S2]
- Community includes most core workflow features and can be registered for extra free tooling [S3]
- Code-capable workflows, APIs, CLI controls, custom nodes, and queue mode support technical use cases [S1][S3]
- Cloud security documentation covers encryption, hosting, backups, and assurance reports [S7]
Cons
- Community transfers patching, security, backup, monitoring, and recovery work to the buyer [S2][S6][S7]
- Important collaboration and governance controls require Business or Enterprise [S3]
- Starter and Pro rely on forum support for technical issues [S8]
- Cloud concurrency and retained execution history can constrain production debugging before the monthly execution allowance does [S1][S5]
- The Sustainable Use License restricts resale, white-label, hosted-access, and some customer-credential use cases [S4]
n8n versus the alternatives
n8n’s strongest distinction is the combination of visual automation, technical extensibility, and self-hosting. Make provides a polished managed visual platform but not a self-hosted control plane; compare the billing and hosting trade-offs in our n8n vs Make guide. Zapier prioritizes ease of use and integration breadth, while n8n gives technical teams more control; our Zapier alternatives roundup covers that wider choice.
Activepieces is the closest licensing contrast. It uses an MIT license, while n8n uses the commercially restricted Sustainable Use License. Read our Activepieces review if permissive open-source terms matter more than n8n’s feature depth. Pipedream is another developer-focused option, but it is cloud-only and meters compute; see our Pipedream review.
Who should choose n8n
Choose n8n if a technical team needs complex multi-step automation, wants to mix a visual canvas with code and APIs, or requires control over where the platform runs. Cloud Starter or Pro is the cleaner choice when setup speed matters and forum-based technical support is acceptable. Community is compelling for internal automation when the organization already operates databases and services and can treat n8n as production infrastructure. [S1][S2][S3]
Enterprise is the more credible fit when business-critical workflows require dedicated support, external secrets, log streaming, extended retention, stronger scaling, or contractual governance. Confirm the exact controls, response targets, and data terms in the quote rather than inferring them from the standard Cloud trial. [S1][S8]
Who should skip it
Skip self-hosted n8n if no one owns updates, backups, observability, security hardening, and recovery. Skip Community when safe teamwork depends on shared projects, shared credentials, SSO, environments, external secrets, or multi-main availability. [S2][S3][S6]
Look elsewhere, or obtain a commercial agreement, if the business model is to resell hosted n8n, white-label it, or collect customers’ credentials in a product powered substantially by n8n. Also reconsider the standard Cloud tiers if production incidents require direct technical support rather than a public forum. [S4][S8]
Final verdict
n8n receives a conditional recommendation with medium confidence. The official documentation supports a strong case for technical internal automation: flexible workflows, predictable per-execution metering, managed Cloud plans, and a capable free self-hosted edition. [S1][S2][S3]
The recommendation remains conditional because the attractive Community price excludes major governance controls and transfers real operational work to the buyer. The license also needs careful review for customer-facing products, and technical support below Enterprise is community-based. Before buying, model actual execution and concurrency demand, list required governance controls, test backup restoration, and confirm that the intended commercial use fits the license. [S3][S4][S5][S6][S8]
Sources
- n8n Plans and Pricingn8n, accessed Sep 21, 2026
- Choose how to use n8nn8n, accessed Sep 21, 2026
- Compare editionsn8n, accessed Sep 21, 2026
- Sustainable Use Licensen8n, accessed Sep 21, 2026
- Understand concurrencyn8n, accessed Sep 21, 2026
- Back up and restoren8n, accessed Sep 21, 2026
- Security at n8nn8n, accessed Sep 21, 2026
- Where to get helpn8n, accessed Sep 21, 2026