n8n can be inexpensive to start, but it is not automatically cheap to run well. As of June 1, 2026, n8n’s public pricing starts at €20 per month billed annually for Starter, €50 per month billed annually for Pro, and €667 per month billed annually for the self-hosted Business plan, while Enterprise is custom. The real buying question is not just the headline price. It is whether your workflow volume, hosting model, governance needs, and internal technical capacity make n8n a low-cost win or a platform that quietly adds operating overhead.
For many businesses, n8n is worth it when workflows are complex, multi-step, and frequent enough that per-step automation tools get expensive. It becomes less obviously attractive when you need self-hosted control, stronger security controls, or a team that can keep the platform healthy over time.
What n8n actually costs right now
n8n’s pricing model is simpler than many automation tools in one important way: paid plans are based on workflow executions, not on how many individual steps happen inside a workflow. n8n also removed active workflow limits on paid plans and now emphasizes unlimited users, unlimited workflows, and unlimited steps, which makes the sticker price look especially attractive for technical teams building dense automations.
- Starter: €20 per month billed annually for 2,500 workflow executions on n8n Cloud.
- Pro: €50 per month billed annually for 10,000 workflow executions on n8n Cloud.
- Business: €667 per month billed annually for 40,000 workflow executions, but this plan is self-hosted only.
- Enterprise: custom pricing, available as cloud or self-hosted, for teams with stricter governance, compliance, or scale needs.
- Community Edition: there is also a free self-hosted version, but free software does not mean free production operations.
The biggest budgeting trap is assuming the low cloud entry price tells the whole story. It only tells you the platform subscription. It does not tell you what your execution volume will become, whether your workflows need paid upstream APIs, or whether your team can comfortably operate a self-hosted instance.
Where the budget changes faster than buyers expect
Execution volume matters more than workflow complexity
n8n is financially attractive when you run complicated workflows because one end-to-end run still counts as one execution. That is good news if you are replacing step-metered automation. But if you have a workflow triggered every few minutes, or a chatbot-style workflow that fires repeatedly inside a conversation, execution volume can climb fast. A cheap pilot can become a capacity-planning exercise once the workflow is live across a team or customer-facing process.
Cloud versus self-hosted is the real fork in the road
If n8n Cloud fits your needs, the software cost stays easy to understand. The economics change when you need the Business plan, because Business is self-hosted only. That means your budget is no longer just a subscription decision. It becomes a stack decision that includes infrastructure, upgrades, monitoring, backup discipline, and someone who owns reliability.
Collaboration and governance features can force a plan jump
Many teams start by pricing n8n like a solo builder tool. That misses the point. Once you need SSO, SAML, LDAP, version control with Git, different environments, or longer operational insights, you are no longer evaluating Starter or Pro economics. You are evaluating whether the Business or Enterprise path makes sense for how your organization actually works.
Self-hosting is not free just because the license is free
n8n’s documentation is clear that self-hosting requires real technical knowledge around server and container setup, resource management, security, and configuration. That means the free Community Edition is best understood as a software license decision, not a full total-cost-of-ownership answer. If your team already runs internal platforms, self-hosting may be efficient. If not, the labor cost can outweigh the savings quickly.
Example budget scenarios buyers can model
The most useful way to budget n8n is to separate platform price from operating cost. The platform subscription is public. The operating cost depends on your architecture, workflow count, and how much internal ownership n8n needs.
Illustrative n8n budget scenarios
| Scenario | Likely plan path | Public platform price | What to budget beyond the plan |
|---|---|---|---|
| Testing one or two internal automations | Starter cloud | €20/mo billed annually | Workflow design time, any paid app APIs, light owner time |
| Small team running production workflows daily | Pro cloud | €50/mo billed annually | Execution growth, admin ownership, external AI or SaaS usage |
| Company under 100 employees needing stronger controls | Business self-hosted | €667/mo billed annually | Hosting, security, upgrades, monitoring, backups, internal support |
| Regulated or high-scale rollout | Enterprise | Custom | Architecture planning, governance, support expectations, scale testing |
If you are deciding between n8n and another automation stack, model three numbers side by side: subscription cost, internal operating cost, and the cost of the manual work you expect to remove. That is where the real comparison lives.
A simple ROI and payback formula for n8n
A practical payback formula is:
Payback period = total launch cost divided by monthly net savings.
In plain language, add up implementation effort, platform cost, and any new operating cost. Then divide that by the monthly labor cost, error reduction, or throughput gain the workflow creates.
A simple annual ROI formula is:
ROI = (annual value created minus annual cost) divided by annual cost.
For n8n, the value side usually comes from a mix of:
- hours no longer spent on repetitive operations,
- fewer handoff errors between systems,
- faster turnaround on customer or internal requests,
- avoided spend on higher-cost step-based automation tools, and
- better process consistency across teams.
The cost side usually includes more than the subscription. For cloud buyers, it is the plan plus workflow ownership and any external services used inside the automation. For self-hosted buyers, it also includes the people and infrastructure required to run the platform safely.
Hidden costs and risks buyers often miss
- Chat and agent workflows can multiply executions: if your use case is conversational or event-heavy, usage can grow faster than teams expect.
- External AI spend is separate: n8n may orchestrate the workflow, but model usage, SaaS transactions, or API calls can still sit outside the n8n bill.
- Business is not a cloud upgrade: teams that assume they can simply toggle from Pro cloud into Business later may be surprised, because Business is self-hosted only.
- Operational ownership is real: somebody has to monitor failed runs, maintain credentials, update workflows, and keep dependencies from drifting.
- Cheap automation can still be bad automation: if the process itself is unstable, n8n may automate the noise instead of creating real savings.
How to decide whether n8n is worth it
n8n is usually worth it when you have technically capable owners, multi-step workflows, and enough recurring process volume to justify building a durable automation layer. It is especially appealing when per-step pricing elsewhere makes complex automations feel artificially expensive.
It is less compelling when your team mainly wants a completely managed environment with minimal operational responsibility, or when the workflows are too low-volume to justify ongoing ownership. In those cases, the cheapest subscription may not be the cheapest total outcome.
The right decision is not “Is n8n cheap?” It is “Does n8n give us enough workflow leverage to justify the subscription, the setup path, and the operating model we are taking on?” Buyers who answer that question clearly usually make much better automation decisions than buyers who focus on the sticker price alone.