n8n: access to the editor changes the business case

Internal automation, a customer-facing engine and an embedded editor are different commercial products.

Evidence and interpretation

Public-source desk research checked 16 October 2026. Company statements are attributed; commercial conclusions are Offaxis analysis. Illustrative scenarios are labeled. We have not independently tested products or audited company accounts.

Map the user before estimating cost

Our thesis is that automation software should be evaluated against who creates workflows, who operates them and who receives the output. Two products can use the same underlying engine while facing different licensing, support and revenue economics. A generic claim that a self-hosted tool is “free” does not settle the commercial design of a customer-facing product.

What the current vendor guidance says

n8n’s help centre distinguishes internal Community-edition use from scenarios where external users build or configure workflows. Its OEM page describes embedding the workflow editor as a separate commercial offering with its own terms. These pages establish the vendor’s published distinctions, not a legal determination for every possible architecture. Exact use cases should be checked against the current terms and confirmed with the vendor when unclear. [1][2]

Three roles that are easy to confuse

An internal automation team builds workflows for its own organization. A managed-service provider operates workflows and delivers results to customers. A software product may allow customers to configure logic or use an embedded editor. Our interpretation is that the economic model changes as customers gain control over configuration, because usage, support and licensing requirements can change together. The labels alone do not determine which contract applies.

Commercial layer	What is supplied	Evidence to examine
Internal automation	Organization controls the workflow	Operations and appropriate internal-use terms
Managed outcome	Customer receives an output	Service scope, support cost and license fit
Customer-configurable product	External user creates or changes logic	Commercial agreement and configuration boundary

Why self-hosting still has a price

A self-hosted deployment needs hosting, updates, backups, monitoring and recovery. A customer-facing service also needs a response when a workflow fails or a connected service changes. These are operating-cost categories, not n8n price claims. They should be modeled alongside the appropriate license rather than being treated as work that disappears when the software is downloaded.

Commercial sensitivity

Suppose a synthetic automation service receives 2,000 currency units per month from customers and incurs 300 in infrastructure, 400 in applicable software charges and 900 in direct support. The remaining 400 precedes sales, development, tax and other costs. If support doubles, that contribution becomes negative. The figures are illustrative, not n8n pricing. The point is to test exception handling and customer complexity before promising unlimited service.

What to decide before launch

Write down who can edit logic, which interfaces they use, where credentials are held and who handles failed executions. Confirm the relevant commercial terms before selling the product. Then run realistic workflows with expired credentials, changed inputs and external service errors. The thesis strengthens when the same operating model serves repeat customers with manageable support. It weakens when every workflow becomes a bespoke project whose cost is invisible in the subscription price.