n8n Pricing: Cloud, Community, and Self-Hosted Costs

Buying path

For most teams, the default entry is the managed cloud route because n8n operates the runtime and the buyer can estimate the subscription from workflow executions. That keeps the first decision focused on expected production runs and required collaboration rather than server sizing and platform maintenance.

Self-hosting is a separate operating choice. Community Edition removes the n8n license charge for the standard self-hosted product, but it transfers infrastructure, upgrades, backups, monitoring, security, and incident response to the buyer. Treat it as a control and capability decision, not a promise of zero total cost.

Upgrade triggers

Upgrade when production execution volume, concurrent runs, shared projects, retention, administration, or governance controls become operational constraints. The relevant threshold is the workflow run, not the number of steps in that workflow, so frequent triggers and chat interactions can consume an allowance faster than a visually complex workflow that runs rarely.

For self-hosters, the paid boundary appears when organizational controls such as environments, source-controlled promotion, single sign-on, scaling, or vendor-backed procurement matter more than the free edition's feature set. Business-critical operations may also justify a sales-assisted route when formal support, external secrets, log streaming, or custom capacity are required.

API and team boundaries

An n8n subscription pays for the automation platform and its workflow-execution allowance. It is not a prepaid balance for third-party APIs, databases, messaging services, or AI model providers called from a workflow; those vendors bill the credentials and usage attached to their services.

The n8n public API and CLI are control surfaces for an n8n instance, not a separately priced n8n developer API product. Cloud keeps hosting inside the subscription, while self-hosted teams carry runtime costs. AI Assistant credits govern that preview feature on eligible plans; they do not erase model, sandbox, search, or API expenses created by production automations.

Final pricing check

Before paying, estimate production executions from schedules, webhook events, and expected chat turns, then test how concurrency and queued work affect the service level you need. Confirm whether the quoted price is monthly or annual, whether VAT applies, and how retention and collaboration limits align with the operating model.

For self-hosted licensing, verify which instances will share the execution quota, how the daily license check fits network policy, and what an overage or upgrade would cost. Also review the Sustainable Use License if the deployment will be embedded, white-labeled, resold, or offered to customers as a hosted service.