TL;DR

n8n is the most-starred workflow-automation OSS project (180k+ stars). Distinctive feature: execution-based pricing — one workflow run costs the same whether it has 2 steps or 40. That's a structural advantage over Zapier-style per-step billing for AI chains and multi-API enrichment.

• Starter EUR 20/mo (2,500 executions); Pro EUR 50/mo (custom quota + 20 concurrent + workflow history); Business EUR 667/mo (40k executions, SSO, SAML, Git, multi-environment, self-hosted only).
• The Pro → Business cliff is 13× — you cross it for SSO + multi-environment + Git versioning, not capacity.
• Sustainable Use License (not OSI-approved). Self-host for your team is fine; running it as a managed service for customers is not.
• Community Edition (self-hosted, free) is genuinely full-featured. Move to cloud Pro when you need parallel executions or workflow history.
• AI Workflow Builder credits are the next monetization lever as agentic workflows dominate.

n8n is a workflow automation tool designed for technical teams. It occupies a middle ground between Zapier (which is user-friendly but expensive) and building everything from scratch (free but time-consuming).

The platform enables users to connect apps, databases, APIs, and AI models into automations called workflows. With over 180,000 GitHub stars, it represents the most-starred workflow automation project globally and has accelerated growth as development teams recognize their need to productionize AI agents.

Disclosure: Beton uses n8n for core GTM automation.

The Distinctive Feature: Execution-Based Pricing

Unlike most automation tools that charge per step (Zapier calls these "tasks"), n8n employs execution-based pricing. One complete workflow run — from trigger to finish — costs the same regardless of how many steps it contains.

For straightforward automations this distinction matters little. However, for complex workflows involving AI chains, multi-API enrichment pipelines, and conditional branching, this represents a substantial structural advantage. A 40-step workflow costs identically to a 2-step one.

Pricing Plans

Starter — EUR 20/month (annual)

• 2,500 executions monthly
• 5 concurrent executions
• 1 shared project, 50 AI Workflow Builder credits
• Cloud-hosted

Pro — EUR 50/month (annual)

• Custom execution quota (user-configured)
• 20 concurrent executions
• 3 shared projects, 150 AI credits
• Workflow history, global variables, admin roles, execution search
• Cloud-hosted

Business — EUR 667/month (annual)

• 40,000 executions monthly
• 6 shared projects
• SSO, SAML, LDAP, Git version control, multiple environments
• Self-hosted only

Enterprise — Contact sales

• 200+ concurrent executions, unlimited projects
• Log streaming, external secret store, 365-day execution logs
• Cloud or self-hosted options

Annual billing provides 17% savings. Startups with under 20 employees receive 50% off Business tier pricing.

The Pricing Cliff

A substantial jump exists between Pro (EUR 50/month) and Business (EUR 667/month) — a 13-fold increase. The Business tier requires self-hosting while adding essential enterprise features like SSO, multi-environment setup, and Git-based version control. This pricing structure intentionally targets organizations possessing existing DevOps capacity seeking simply a license.

Licensing Considerations

The Community Edition operates under n8n's Sustainable Use License — neither MIT, Apache, nor OSI-approved. Key restriction: users may self-host for their own team but cannot create competing products or operate it as a managed service for customers.

License selection directly influences monetization strategy. Apache 2.0 or MIT would permit anyone to fork and commercialize n8n-as-a-service. The Sustainable Use License prevents this, protecting n8n's cloud business while permitting community use.

AGPLv3 takes a different approach: requiring modified version distributions to be open-sourced while preventing AGPL code embedding in commercial customer products without licensing.

For typical n8n users automating their own infrastructure, the license remains irrelevant. For anyone considering building atop n8n, it presents a deal-breaker.

Value Assessment

Self-hosting users needing SSO or multiple environments should almost always pay for Business tier — these represent substantive features rather than luxuries.

Individual contributors and small teams should begin with Community Edition self-hosted, which provides genuine completeness with all integrations, unlimited workflows, and unlimited users.

Migration to cloud Pro (EUR 50/month) makes sense upon requiring parallel executions or workflow history.

One consideration: AI Workflow Builder credits function as a second metering mechanism layered atop executions. Currently limits remain generous enough to avoid impact, yet as agentic workflows dominate usage patterns, this represents the transparent next monetization lever.

How n8n pricing scales

n8n bills by workflow executions in flat tiers. The Community edition self-hosts free; SSO/SAML only appears on the top Enterprise tier.

n8n entry pricing. Business/Enterprise (SSO, Git, multi-env) sit well above Starter.

FAQ

Is n8n open source?

Community Edition ships under n8n's Sustainable Use License — not OSI-approved. You can self-host for your own team; you can't operate it as a managed service for external customers without a commercial agreement.

How does n8n pricing differ from Zapier?

Zapier charges per task (each step). n8n charges per workflow execution — one run from trigger to finish, regardless of step count. For complex AI chains and multi-step enrichment pipelines, n8n is structurally cheaper.

When should I move from Community Edition to cloud?

When you need parallel executions, workflow history, or admin features. Self-hosted Community is fully featured for individuals and small teams. Pro at EUR 50/mo unlocks 20 concurrent executions and audit-friendly tooling.

Why is the Pro to Business jump so big?

13× ($50 → $667) because Business is the SSO/SAML/Git/multi-environment tier, self-hosted only. It's positioned for orgs that already have DevOps capacity and need a license — not capacity.