Platform review
The automation tool with the best cost-per-execution at volume and the only one you can self-host — at the price of a real learning curve.
- Pricing from
- €20/mo Cloud (annual); free self-hosted
- Free tier
- Yes — Community Edition self-hosted, unlimited executions
- Founded
- 2019
- Best for
- Technical teams, AI-agent builders, agencies, data-residency requirements
Reviewed July 2026
The verdict
The automation tool with the best cost-per-execution at volume and the only one you can self-host — at the price of a real learning curve.
Our recommendation
n8n is the strongest choice for technical teams, agencies, and AI-agent builders who run high workflow volumes and care about cost control. Execution-based billing (one workflow run = one execution, regardless of step count) makes it dramatically cheaper than Zapier at any meaningful volume. Self-hosting on Community Edition is free with unlimited executions, making it the only tool in the category where the infrastructure cost is the actual floor. The trade-off is honest: this is not a beginner platform. Expressions syntax, PostgreSQL migration requirements for production self-hosting, and the node-based canvas all require investment.
Choose it if
You're a technical team, agency, or AI-agent builder running more than 5,000 executions per month and willing to invest in setup.
Avoid it if
You're a non-technical solo founder who needs a working automation in under an hour and has no interest in managing servers or learning expressions syntax.
How we review: This review is based on real-world n8n deployments across agency and product contexts since 2019, combined with primary documentation review, n8n community.n8n.io forum analysis, and cited third-party research. No affiliate relationship exists with n8n; RapidDev receives no compensation for this review.
Scored, dimension by dimension
Every score is earned — each note explains exactly why.
Ease of use
6.5/10The node-based canvas is powerful but developer-leaning. Non-technical users face a documented ramp-up period with expressions syntax (Luxon date formatting, jmespath, $json references) that has no equivalent in Zapier's linear builder. Community threads on r/n8n and community.n8n.io consistently cite this as the primary onboarding friction — it is the platform's real price of admission.
Pricing & value
9.0/10Execution-based billing is n8n's single greatest competitive advantage: one full workflow run counts as one execution regardless of how many steps are inside. A 20-step AI enrichment workflow = 1 execution, versus 20 tasks on Zapier. Community Edition is free with unlimited executions (you pay VPS infra only, typically $5–10/mo for light use). Cloud Pro at €50/mo handles 10,000 executions — Zapier charges approximately $300/mo for an equivalent effective operation count.
Scalability
9.0/10Horizontal queue mode backed by Redis workers, multi-main support on Enterprise, and 200+ concurrent executions make n8n a genuinely scalable substrate. Sub-workflows, bulk operations, and PostgreSQL backing enable production-grade deployments. The documented migration pattern is Cloud → self-hosted n8n (not n8n → a competitor), which is the strongest scalability signal possible: teams grow into more n8n, not out of it.
Performance
8.0/10Reliable when properly configured, but two footguns undercut the default out-of-the-box experience. SQLite — the default database — causes production lock and corruption under concurrent webhook load; community.n8n.io and osher.com.au both document this pattern extensively. No default EXECUTIONS_TIMEOUT means a stuck workflow will consume memory until OOM crash rather than fail gracefully. Both are avoidable with proper setup; neither should catch an informed team by surprise.
Ecosystem & integrations
7.0/10Approximately 400+ official nodes cover the mainstream enterprise stack — Slack, Salesforce, PostgreSQL, HubSpot, Google Workspace, AWS services, GitHub, and more. The HTTP node connects to any REST API with OAuth2 and custom auth, meaning the practical coverage gap versus Zapier's 8,000+ apps matters mostly for niche or legacy SaaS connectors. The 9,500+ community workflow templates on the n8n template library substantially reduce starting friction for common use cases.
Support & community
7.5/10The community.n8n.io forum is active and technically strong, with staff participation and peer resolution for most common issues. Email support on paid Cloud plans; SLA only on Enterprise. The late-2025 Business self-hosted price increase sparked notable community friction (documented on instapods.com and the community forum), and the gap between forum support and Enterprise SLA is wide. For teams between Community and Enterprise, the support tier is forum + email with no contractual SLA.
Vendor lock-in
8.5/10n8n is Apache 2.0 open source (with an Enterprise license for commercial self-hosting features), fully self-hostable, and workflows export as standard JSON that can be version-controlled in Git. This is the lowest vendor lock-in of any platform in the automation category reviewed. Migrating from n8n Cloud to self-hosted n8n requires no workflow rebuilding — a credential re-entry exercise at most, not a platform switch.
AI features
9.0/10Native AI Agent nodes, LangChain and LangGraph integration, a built-in MCP Client node (plus n8n-nodes-mcp community node), human-in-the-loop tool approval (shipped January 2026), and Microsoft Agent 365 Trigger (May 2026) place n8n among the most capable agentic workflow substrates in the category. AI Workflow Builder credits are included on Cloud plans (50 on Starter, 150 on Pro, 1,000 on Enterprise). The main constraint: Starter's 50 AI Builder credits burn fast on complex multi-model agent builds.
Pros & cons
What we like
- Execution-based billing means a 20-step workflow = 1 execution — versus 20 tasks on Zapier; at 10,000 effective operations/month, n8n Cloud Pro costs €50/mo vs ~$300/mo on Zapier.
- Community Edition is free with unlimited executions: the only automation platform in this category you can self-host for the cost of a VPS ($5–10/mo light use, $20–50/mo production-hardened).
- Lowest vendor lock-in in the category: Apache 2.0 open source, workflows export as JSON to Git, fully self-hostable — switching from Cloud to self-hosted requires no workflow rebuilding.
- Native AI Agent nodes + LangChain integration + built-in MCP Client node make n8n the strongest agentic workflow substrate of the five platforms reviewed; human-in-the-loop approval shipped January 2026.
- Horizontal queue mode (Redis-backed workers) and multi-main Enterprise support enable 200+ concurrent executions — genuine production-scale infrastructure, not a managed SaaS ceiling.
- 9,500+ community workflow templates on the template library reduce cold-start friction; the HTTP node with OAuth2 covers any REST API not in the 400+ official node catalog.
- Self-hosting enables GDPR and HIPAA-style data-residency control unavailable on any other platform in the category; Cloud plans use Azure Frankfurt for EU data residency.
- $180M Series C raised October 9, 2025 (Accel, NVIDIA NVentures, Meritech, Redpoint, Deutsche Telekom T.Capital); valuation $2.5B; ~196,000 GitHub stars as of July 2026 — strongest momentum signal in the category.
What we don't
- Steeper learning curve than Zapier or Make: expressions syntax ($json references, Luxon date formatting, jmespath) requires hands-on practice, not just reading docs; documented consistently across r/n8n, community.n8n.io, and third-party reviews.
- Cloud Starter's 2,500 executions/mo ceiling is exhausted in approximately 9 days by a single 5-minute polling workflow (~8,640 executions/mo); the execution math must be modeled before building polling-based automations.
- The pricing gap between Cloud Pro (10,000 executions, €50/mo) and Cloud Business (40,000 executions, €667/mo) is the platform's biggest friction point — a 13× price jump for 4× executions, with no middle tier.
- SQLite default database causes production lock, corruption, and incompatibility with queue mode; migration to PostgreSQL is mandatory before exposing self-hosted instances to concurrent webhook traffic.
- Lost N8N_ENCRYPTION_KEY = permanently unrecoverable stored credentials with no escrow and no recovery path; multiple threads on community.n8n.io document teams discovering this during server migrations.
- No execution timeout by default: stuck or infinite-loop workflows consume memory until an OOM crash rather than failing with a useful error; EXECUTIONS_TIMEOUT env var must be set manually at deployment.
- Self-hosted Business/Enterprise price increase in late 2025 "sparked heated community discussion" (instapods.com; n8n community forum) — pricing trajectory for self-hosted commercial tiers is an open risk.
n8n vs the competition
Head-to-head on the aspects that actually decide the choice. The highlighted cell wins each row.
| Aspect | n8n | Zapier | Make (ex Integromat) |
|---|---|---|---|
| Price at ~10K effective operations/month | €50/mo Cloud Pro or ~$10/mo self-hosted | ~$300/mo | ~$10–16/mo Core/Pro |
| Free tier | Free self-hosted unlimited executions | 100 tasks/mo, 2-step Zaps only | 1,000 credits/mo, 2 scenarios |
| Pre-built integrations count | ~400+ official nodes + any API via HTTP | 8,000+ apps | 3,000+ apps |
| AI and agentic depth | Very high — AI Agents, MCP Client, LangChain, human-in-loop (Jan 2026) | High — Copilot, Agents GA May 2025, MCP server | High — Maia, AI Agents open beta Feb 2026, MCP |
| Self-hosting available | Yes — Community Edition free forever | No | No |
| Vendor lock-in | Low — Apache 2.0 OSS, JSON export, Git versioning | High — no export, US-primary cloud, no self-host | Medium-high — JSON export exists but no self-host |
| Learning curve | Steep — node canvas + expressions syntax | Gentlest in the category — linear builder + Copilot NL | Moderate-steep — visual canvas, more approachable than n8n |
| HIPAA / PHI handling | Yes — via self-hosting (your certification) | No — explicitly no BAA; PHI prohibited (zapier.com/legal/data-privacy) | Unverified — verify Make trust center for current compliance posture |
| Cost for 5-step AI workflow × 1,000 runs/month | 1,000 executions (1 exec per full run) | Up to 5,000 tasks × AI multiplier (3–5× per AI step) = potentially 5,000–25,000 tasks | 5,000 credits (1 credit per module, 5 modules per run) |
| Support tier at entry paid plan | Forum + email (no contractual SLA below Enterprise) | Email (Premier on Team+ only) | Email priority on Pro+ |
Swipe the table sideways to see every competitor.
Pricing, for real
Community Edition
Free (self-hosted)
Unlimited executions; you pay infrastructure only — approximately $5–10/mo for a basic VPS on light use, $20–150/mo for production-hardened PostgreSQL + Redis queue mode setup. No support SLA. The decisive entry point for technical teams.
Starter (Cloud)
€20/mo annual
2,500 executions/mo, 5 concurrent, 1 shared project, 50 AI Workflow Builder credits, forum support. The gatekeeper: 2,500 executions sounds generous until one 5-minute polling workflow consumes ~8,640/mo alone. Webhook-triggered workflows avoid this entirely — build polling awareness before choosing this tier.
Pro (Cloud)
€50/mo annual
10,000 executions/mo, 20 concurrent, 3 shared projects, admin roles, global variables, execution search, 150 AI Workflow Builder credits. The practical sweet spot for teams not yet hitting the Pro ceiling. Cloud-hosted on Azure Frankfurt (EU data residency).
Business (Cloud or self-hosted)
€667/mo annual
40,000 executions/mo, SSO/SAML/LDAP, Git version control, environments, 6 shared projects. Overage: €4,000 per additional 300,000 executions, invoiced 45 days later — a potential surprise line on quarterly invoices if polling workflows spike. Start-up plan: 50% off for companies with fewer than 20 employees and under $5M in funding.
Enterprise (Cloud or self-hosted)
Custom
Unlimited executions option, 200+ concurrent, external secret store, log streaming, dedicated support with SLA, 1,000 AI credits. Enterprise customers include Volkswagen, Delivery Hero, KPMG, Vodafone, and Twitch (n8n.io/customers).
Hidden costs to budget for
Self-hosting infrastructure is NOT included in any plan: budget $5–10/mo for light use on a basic VPS, and $50–150/mo for a production-hardened setup with PostgreSQL, Redis queue mode, and automated backups.
Monthly billing surcharge: approximately 17% more than annual pricing across all Cloud tiers — annual commitment is strongly preferable on n8n.
Sub-workflow execution multiplication on Cloud: each called sub-workflow counts as a separate execution. A workflow that calls 5 sub-workflows per run = 6 executions/run total. Audit sub-workflow usage before finalizing your Cloud tier.
Business self-hosted overage: €4,000 per 300,000 extra executions, billed 45 days after the month closes — a delayed surprise on quarterly invoices if polling-intensive workflows spike unexpectedly.
Value verdict
n8n's pricing model is genuinely exceptional for teams with any technical capacity. A team running 25,000 executions/month faces a binary choice: Cloud Business at €667/mo or self-hosted Community on a ~$20–50/mo VPS. The self-hosted path wins decisively on economics. The only groups for whom n8n isn't the value leader are non-technical teams unable to manage infrastructure, who should evaluate Make's hosted pricing instead.
What it'll cost you
Real monthly cost for three typical profiles — not the headline sticker price.
Solo founder — hobby / validation
€0–20/mo
per month
Assumptions
~2,000 executions/month, webhook-triggered workflows, no polling, basic integrations
Community Edition self-hosted on a basic VPS costs $5–10/mo in infrastructure — the cheapest path if you can manage a Docker deployment. Cloud Starter at €20/mo is the zero-ops alternative, but model the 2,500 execution ceiling against your workflow frequency before signing up; webhook-triggered workflows are safe, polling workflows are not.
Growing startup — ~25K executions/month
€667/mo Cloud Business or ~$20–50/mo self-hosted
per month
Assumptions
Multiple multi-step workflows including some polling, small team, 25,000 executions/month
This is the pricing gap that most hurts mid-size teams: Pro covers 10,000 executions (€50/mo), Business covers 40,000 (€667/mo) — a 13× price jump with no intermediate option. For any team with DevOps capacity, self-hosted Community Edition on a $20–50/mo production VPS is the decisive economic choice here. Teams without infrastructure capacity face the €667/mo Business tier or a Startup discount (50% off for companies under 20 employees and $5M funding).
Agency / enterprise — ~500K executions/month
~$12–50/mo self-hosted or custom Enterprise negotiation
per month
Assumptions
Multiple client workflows, high-frequency webhooks, queue mode required, 500K+ executions/month
At 500,000 executions/month, Cloud Business would require approximately two overage buckets beyond the 40,000 base (at €4,000 per 300,000 extra executions each), making Cloud deeply uneconomical. Self-hosted Community Edition on Hetzner runs documented at approximately $12/mo VPS for production queue-mode setups (automationatlas.io) — the math at this scale strongly favors self-hosting. Enterprise Cloud negotiation is the alternative for teams unwilling to manage infrastructure.
What We See in Practice
Teams arrive at n8n from two paths. The first: cost refugees from Zapier who hit $300+/mo on multi-step workflows and find that execution-based pricing makes the same workload dramatically cheaper — sometimes by 6–10×. The second: AI-agent builders who need LangChain-native nodes, MCP Client support, and human-in-the-loop approval not available in simpler tools. Both groups share a common first friction: the execution ceiling on Cloud Starter hits before they expect it, particularly when any workflow uses polling at 5-minute intervals.
The SQLite-to-PostgreSQL migration is the canonical first production incident on self-hosted setups. Teams run SQLite in Docker for weeks — sometimes months — without issue during development, then hit database locks under real concurrent webhook load. The pattern is entirely predictable and well-documented on community.n8n.io and osher.com.au. The correct sequence is: choose PostgreSQL before any credential is added, set the encryption key in a password manager before first use, and enable EXECUTIONS_TIMEOUT before any workflow goes live.
Agencies managing n8n for multiple clients find the multi-project feature (3 on Pro, 6 on Business) the key organizational unit for client separation. Queue mode with multiple worker processes is the actual scalability lever at agency scale — not the Cloud plan tier. The encryption key footgun surfaces most predictably during server migrations and Docker container recreations: teams that never documented the key discover it when credentials stop working after a clean rebuild. This is entirely recoverable only by re-entering all credentials from scratch — there is no key escrow or recovery mechanism.
Our field verdict
For technical teams and AI-agent builders, n8n is the highest-value automation infrastructure available in 2026 — the combination of execution-based pricing, self-hosting, and native LangChain/MCP support has no direct competitor. The platform demands an informed operator; reward it with proper setup discipline and it repays the investment at every scale.
What the community says
The n8n community is technically engaged and candid. The dominant positive themes are the cost savings versus Zapier, the self-hosting flexibility, and the AI/agent capabilities. The dominant pain points are execution math surprises on polling workflows and the encryption key footgun on self-hosted setups — both of which are operational, not product bugs, but are frequently encountered by teams who didn't read the setup checklist. The late-2025 Business price increase generated real community backlash and is an ongoing tension point.
Most common complaints
Polling workflows blow past Cloud Starter's 2,500 executions/month in approximately 9 days for a single 5-minute cron — most new users discover this after building, not before
Business self-hosted and Enterprise price increases in late 2025 'sparked heated community discussion' — commercial self-hosting pricing trajectory is an ongoing frustration
Lost N8N_ENCRYPTION_KEY = permanently unrecoverable stored credentials with zero recovery path — discovered during server migrations or container rebuilds
SQLite default database causes production locks and corruption under concurrent webhook load; new self-hosters frequently hit this in their first production incident
Steeper learning curve than Zapier or Make for non-developers — expressions syntax and the node canvas require more upfront investment than alternative tools
Most praised
- Execution-based pricing delivers dramatic cost savings on multi-step workflows versus Zapier and Make — cited across virtually every positive community review and migration story
- Code nodes (JavaScript and Python) and the HTTP node give practical unlimited extensibility without switching to a developer tool
- Self-hosting and data control is unique in the category — LATAM teams in particular cite cheap VPS self-hosting as the decisive economic advantage
- AI and agentic capabilities (LangChain, MCP Client, human-in-the-loop) consistently rated very high by users building LLM-backed automation workflows
Deep dive
Editor & Learning Curve
n8n's node-based canvas is the platform's defining UX characteristic — and its biggest polarizer. Technical users who think in graphs find it more expressive than Zapier's linear builder or Make's scenario canvas; you can model complex branching logic, loops, and sub-workflow orchestration visually. The 9,500+ community workflow templates on the n8n template library substantially reduce cold-start friction: for most common automation patterns (CRM sync, webhook processing, LLM enrichment), a starting template exists. The friction point is expressions syntax: $json references, Luxon date formatting for time manipulation, jmespath for nested JSON traversal — these require hands-on practice, not just documentation reading. Community threads consistently cite this as the primary onboarding friction for users coming from Zapier's point-and-click interface. Non-technical users who need a working automation in under an hour should be directed to Zapier or Make instead; this is not a shortcoming of n8n so much as an honest statement of its design target.
Self-Hosting & Deployment
n8n is the only automation platform in this five-tool comparison that supports self-hosting, and it is the feature that makes the platform structurally different from everything else in the category. Docker Compose setup for basic self-hosting takes approximately 15 minutes for someone with server experience. Production hardening — switching from SQLite to PostgreSQL, enabling Redis-backed queue mode, configuring backups, setting EXECUTIONS_TIMEOUT, managing the encryption key securely — requires 4–8 hours of focused work. This is not a casual deployment, but it is well-documented and within reach of any developer with infrastructure exposure. Community Edition is free forever with unlimited executions, making the infrastructure cost ($5–150/mo depending on load) the true total cost of ownership. GDPR and HIPAA-style data residency control comes as a natural consequence of self-hosting — your data never leaves your infrastructure.
AI & Agentic Capabilities in 2026
n8n's AI feature set as of mid-2026 is the strongest in the automation category for genuinely agentic use cases. Native AI Agent nodes with tool-calling capability, LangChain and LangGraph integration for complex chain-of-thought orchestration, and a built-in MCP Client node (plus the community n8n-nodes-mcp) make n8n a natural substrate for building production LLM workflows. Human-in-the-loop tool approval, shipped in January 2026, enables workflows where an agent's proposed actions are reviewed by a human before execution — a critical feature for high-stakes automations. The Microsoft Agent 365 Trigger, added in May 2026, extends agent orchestration into the Microsoft 365 ecosystem. AI Workflow Builder credits (50 on Starter, 150 on Pro, 1,000 on Enterprise) allow natural-language workflow construction for less technical team members. The main constraint on the Starter tier: 50 AI Builder credits burn fast on complex multi-model agent builds that involve iterative refinement.
Pricing Model Mechanics
Execution-based billing is n8n's single most important differentiator and requires explicit understanding before choosing a tier. One full workflow run = one execution, regardless of how many nodes, steps, or branches are inside. A 20-step AI enrichment workflow that processes 500 records runs as 500 executions — not 10,000 tasks as it would on Zapier. This makes n8n dramatically cheaper for complex multi-step workflows at any meaningful volume. The footgun in the model is polling: a workflow set to poll an API or email inbox every 5 minutes generates approximately 8,640 executions per month — blowing past Cloud Starter's 2,500 ceiling in roughly 9 days. The fix is to prefer webhook-triggered workflows wherever the source system supports webhooks. Sub-workflow execution counts are the second hidden multiplier on Cloud plans: each called sub-workflow = a separate execution, so a workflow calling 5 sub-workflows per run = 6 executions/run total.
Integration Depth
Approximately 400+ official nodes cover the mainstream enterprise stack comprehensively: databases (PostgreSQL, MySQL, MongoDB, Redis), CRMs (Salesforce, HubSpot, Pipedrive), communication (Slack, Teams, Gmail, Twilio), cloud services (AWS S3, GCS, Azure), and core developer tools (GitHub, Jira, Linear, Notion). The HTTP node with OAuth2 and custom authentication support provides a practical escape hatch for any REST API not covered by official nodes — the real integration ceiling is engineering time to implement, not a hard platform limit. The pre-built catalog of ~400 nodes is approximately 5% of Zapier's 8,000+, which matters for long-tail niche SaaS connectors (specific legacy CRMs, legacy ERPs, obscure vertical tools). For modern SaaS stacks built on common components, the gap is rarely encountered in practice.
Error Handling & Reliability
n8n's error handling capabilities are well-designed for production workflows. Error workflow triggers fire on any node failure, enabling centralized error notification (Slack alert, Jira ticket, email) without embedding error logic in every workflow. Automatic retries with configurable backoff, debug-in-editor execution replay, and searchable execution history (on Pro and above) make debugging concrete rather than guesswork. The two reliability footguns are setup-time decisions, not platform bugs: no default EXECUTIONS_TIMEOUT means stuck workflows consume memory until OOM crash, and SQLite default means concurrent webhook load causes database locks. Both are solved during initial deployment if the setup checklist is followed. Cloud SLA is only contractually guaranteed at Enterprise tier; Community self-hosters and Cloud Starter/Pro/Business users rely on platform availability without a contractual uptime commitment.
Security & Compliance
n8n publishes a SOC 3 public report; SOC 2 certification is available to Enterprise customers. Cloud infrastructure runs on Azure in Frankfurt, EU — providing EU data residency for managed Cloud customers without any additional configuration. For self-hosted deployments, AES-256 encryption of stored credentials is managed locally via the N8N_ENCRYPTION_KEY environment variable — which is also the platform's most serious operational risk. Losing this key means all stored credentials become permanently unrecoverable; there is no key escrow, no recovery path, and no support ticket that can restore them. Documentation on community.n8n.io is explicit about this: the key must be stored in a password manager and documented in deployment configuration before any credential is added to the instance. Self-hosted HIPAA and GDPR-style data-residency compliance is entirely within the deployer's control — and entirely their responsibility.
Community & Ecosystem Health
n8n's community is the most technically engaged of the five automation platforms reviewed. The community.n8n.io forum has active staff participation, detailed community-written solutions, and a culture of sharing workflow patterns. ~196,000 GitHub stars as of July 2026 place n8n as the dominant open-source signal in the workflow automation category. The 9,500+ community templates are a real asset — they represent peer-validated workflow patterns, not marketing-generated examples. The ecosystem shadows are the late-2025 Business self-hosted price increase (which generated genuine community backlash) and the Cloud Starter execution ceiling (a top pinned concern in community pricing guides). Enterprise-tier support with SLA comes at significant cost; free and lower-tier users rely on forum resolution, which is generally effective but has no contractual time guarantee.
Where the platform ceiling is
The question no affiliate blog answers: how far this scales before you outgrow it.
The ceiling
Cloud tiers scale from 5 concurrent executions (Starter) to 20 (Pro) to 200+ (Enterprise). Data is hosted in Azure Frankfurt. Self-hosted deployments scale horizontally via Redis-backed queue mode with multiple worker processes; multi-main configuration is available on Enterprise for high-availability setups. Sub-workflows count separately on Cloud billing, which matters when modeling execution quotas at scale. Execution history storage limits apply per plan — check n8n.io/pricing for current per-plan retention periods.
When to leave
Signal 1: Cloud Starter execution budget is exhausted in week 2 from polling workflows — this means immediately upgrading to Pro or evaluating self-host, not staying on Starter. Signal 2: Cloud Business at €667/mo exceeds the cost of a production-hardened Hetzner VPS running self-hosted n8n (~$20–50/mo) plus the ops overhead to manage it — the documented crossover point where self-hosting becomes economically dominant. Signal 3: needing more than 200 concurrent executions on managed Cloud triggers Enterprise negotiation or a self-host Kubernetes deployment.
Where teams go next
Teams overwhelmingly migrate from n8n Cloud to self-hosted n8n — not from n8n to a competitor. Documented case: Hetzner VPS at $12/mo versus Cloud at €667/mo (automationatlas.io). Workflows export as JSON and re-import without modification; credentials require re-entry after migration. For agencies needing custom self-hosted infrastructure design — queue mode, PostgreSQL, Redis, backup pipelines — RapidDev runs n8n self-hosted builds as part of vibe-coder backend setups.
Platform momentum
- $180M Series C raised October 9, 2025 — investors include Accel, NVIDIA NVentures, Meritech Capital Partners, Redpoint Ventures, and Deutsche Telekom T.Capital (blog.n8n.io/series-c; Bloomberg); valuation $2.5B at time of raise.
- ARR exceeding $40M; usage 10× year-over-year; 230,000+ active users reported as of March 2025 (Ventureburn; PitchBook data).
- ~196,000 GitHub stars as of July 9, 2026 — the strongest open-source signal in the workflow automation category by a significant margin (github.com/n8n-io/n8n).
- Active AI roadmaphuman-in-the-loop tool approval shipped January 2026; Microsoft Agent 365 Trigger shipped May 2026; MCP Client node available built-in.
- SAP investment reportedly made May 2026 (Tracxn — verify via primary sources before citing); enterprise customer base includes Volkswagen, Delivery Hero, KPMG, Vodafone, and Twitch (n8n.io/customers).
Our outlook
n8n is the momentum leader in workflow automation in 2026 — self-hosting as an AI-agent substrate is a structural industry tailwind that amplifies n8n's differentiation. The near-term watch items are the Cloud Starter execution ceiling (an ongoing community friction that a revised pricing tier could address) and the trajectory of self-hosted commercial pricing (the late-2025 Business tier increase was the first significant test of community tolerance for pricing evolution).
Who it's for
Developer and technical teams wanting cost control at volume
Good fitExecution-based billing combined with self-hosting delivers the best cost-per-operation in the category. Code nodes (JavaScript and Python) and the HTTP node cover any integration gap that the 400+ official nodes don't address.
AI-agent builders and LLM workflow engineers
Good fitNative LangChain integration, MCP Client node, human-in-the-loop approval (January 2026), and AI Agent nodes make n8n the strongest dedicated agentic workflow substrate of the five platforms reviewed — purpose-built for the patterns that define AI automation in 2026.
Agencies handling high-volume automations for multiple clients
Good fitSelf-hosted queue mode scales across client workloads with execution cost linear to compute rather than n8n seats. Multi-project organization (3 on Pro, 6 on Business) provides client separation at the project level.
Data-residency-constrained organizations (GDPR, HIPAA)
Good fitSelf-hosting provides full data control with no data leaving your infrastructure; Cloud Frankfurt gives EU data residency on managed plans. The only automation platform in this comparison where HIPAA-style control is architecturally achievable.
Non-technical solo founders who want first automation in under 30 minutes
Poor fitSteep learning curve, expressions syntax, and self-hosting complexity make n8n a poor choice for users who need an immediate working automation. Zapier or Make are better starting points and will remain so for this persona.
Teams with no ops capacity scaling past 10K executions without DevOps resources
Poor fitThe €50/mo Pro to €667/mo Business pricing gap — a 13× price jump for 4× executions — leaves a structural missing middle for teams growing past 10,000 executions/month who lack the DevOps capacity to self-host. This cohort is underserved by n8n's current tier structure.
Your first 30 days
A practitioner's runbook to get productive fast — the shortcuts we wish we'd known.
Sign up for Cloud Starter or spin up Docker Compose (15-minute basic setup). Build 2–3 workflows using the node canvas and official community templates.
Practitioner tip: Pick a webhook-triggered workflow first, not a polling one. A single 5-minute polling workflow burns 8,640 executions/month — exhausting Starter's 2,500 ceiling in 9 days. Webhooks have no execution counting overhead beyond the actual trigger event.
Learn the expression editor: $json for current node data, $node["Node Name"].json for upstream data, Luxon date formatting ($now.toFormat("yyyy-MM-dd")), and jmespath for nested JSON traversal.
Practitioner tip: Set EXECUTIONS_TIMEOUT on any self-hosted instance before first production use. Without it, a stuck or infinite-loop workflow consumes memory silently until an OOM crash — not a graceful error. Add error trigger workflows that send Slack notifications before going live.
Migrate from SQLite to PostgreSQL; enable queue mode with Redis; set N8N_ENCRYPTION_KEY in a password manager and in deployment configuration simultaneously.
Practitioner tip: Document the encryption key in at least two offline locations the moment you set it — before adding any credential to the instance. community.n8n.io has multiple threads from teams who lost it during container recreation; there is no recovery path.
Add AI Agent nodes; connect LLM providers (OpenAI, Anthropic Claude, local Ollama); explore MCP Client for Claude or ChatGPT orchestration. Evaluate Cloud versus self-host cost math when approaching 10,000 executions/month.
Practitioner tip: Model polling workflows against your tier's execution ceiling before enabling them at full frequency. At 10,000 executions/month on Cloud Pro, a single 5-minute polling workflow consumes the entire quota — consider 15-minute intervals or webhook alternatives.
Alternatives worth a look
Zapier
Read our reviewBetter when: Non-technical founders who need the widest integration catalog (8,000+ apps) and the fastest time-to-first-automation with zero server management.
Make (ex Integromat)
Read our reviewBetter when: Visual-canvas power without self-hosting at the lowest hosted price for complex multi-step scenarios — approximately $10–16/mo Core versus €50/mo n8n Cloud Pro for similar effective operation counts.
IFTTT
Read our reviewBetter when: Consumer personal triggers (smart home, cross-posting) at $3–15/mo flat rate with zero technical complexity and no execution counting at all.
Frequently asked questions
Is n8n worth it in 2026?
Yes — for technical teams and AI-agent builders. n8n's execution-based pricing (one workflow run = one execution regardless of step count) makes it dramatically cheaper than Zapier at any meaningful volume. The $180M Series C raised in October 2025, ~196,000 GitHub stars, and active AI roadmap (LangChain, MCP Client, human-in-the-loop) confirm the platform's momentum. The honest caveat: n8n is not worth the setup cost for non-technical users who need their first automation running in under an hour.
Is n8n free?
The Community Edition is free indefinitely — you self-host it and pay only for the VPS infrastructure, which runs approximately $5–10/month for light use and $20–50/month for a production-hardened setup with PostgreSQL and Redis. Cloud plans start at €20/month (Starter, 2,500 executions) with no free Cloud tier. The Community Edition's free unlimited executions is n8n's single most important differentiator versus every other automation platform in the category.
How does n8n compare to Zapier?
n8n wins decisively on cost at volume: €50/month Cloud Pro for 10,000 executions versus approximately $300/month on Zapier for the same effective operation count. n8n wins on self-hosting, vendor lock-in (Apache 2.0 open source versus no Zap export format), HIPAA compliance via self-hosting, and AI/agent depth. Zapier wins on integration breadth (8,000+ apps versus ~400+ official n8n nodes), learning curve (linear builder versus node canvas + expressions), and time to first working automation. The inflection point where n8n becomes the clear choice is approximately 5,000 executions/month for technical teams.
What is the n8n execution ceiling on Cloud plans?
Cloud Starter: 2,500 executions/month (5 concurrent). Cloud Pro: 10,000 executions/month (20 concurrent). Cloud Business: 40,000 executions/month (pricing as of July 2026). Enterprise: negotiated, with 200+ concurrent available. Critical warning: a single 5-minute polling workflow generates approximately 8,640 executions/month alone — blowing past Starter's ceiling in roughly 9 days. Always use webhook-triggered workflows where possible; model polling-workflow execution counts before choosing a tier.
Can n8n handle HIPAA-compliant workflows?
Yes — via self-hosting. Self-hosted n8n gives you complete data residency control, enabling HIPAA-style compliance because PHI never leaves your infrastructure. You are responsible for all aspects of HIPAA certification on your self-hosted instance (BAA, audit logging, access controls, encryption at rest). Cloud n8n on Azure Frankfurt provides EU data residency but does not currently publish a HIPAA BAA for Cloud customers. Zapier explicitly prohibits PHI routing with no BAA option.
What happens if you lose the n8n encryption key?
All stored credentials become permanently unrecoverable. There is no key escrow, no support path to regenerate or recover the key, and no way to decrypt credentials without it. The only resolution is re-entering every credential from scratch. Store the N8N_ENCRYPTION_KEY in a password manager and in deployment configuration files before adding any first credential to the instance. community.n8n.io has multiple threads documenting this exact scenario during server migrations and Docker container recreations.
Should I use n8n Cloud or self-host?
Self-host if you have any DevOps capacity at all — the economic case is overwhelming above 10,000 executions/month. Cloud Starter (€20/mo, 2,500 executions) and Cloud Pro (€50/mo, 10,000 executions) make sense for small teams who want zero infrastructure management. The Pro-to-Business gap (€50/mo to €667/mo) is where the self-hosting math becomes undeniable: a production-hardened Hetzner VPS runs documented at approximately $12/month (automationatlas.io) versus €667/month for Cloud Business with 4× the execution allowance.
What database should n8n use in production?
PostgreSQL. SQLite is n8n's default database but is not suitable for production deployments: it causes database locks under concurrent webhook load, is incompatible with queue mode (required for horizontal scaling), and has a documented history of corruption under heavy use (community.n8n.io; osher.com.au). Migrate to PostgreSQL before exposing any self-hosted instance to real traffic — not after the first production incident.
Is n8n good for building AI agents?
n8n is arguably the strongest dedicated AI agent workflow platform available in 2026 among no-code/low-code automation tools. Native AI Agent nodes with tool-calling, LangChain and LangGraph integration, a built-in MCP Client node for connecting Claude and ChatGPT, human-in-the-loop tool approval (January 2026), and Microsoft Agent 365 Trigger (May 2026) make it purpose-built for agentic automation patterns. It consistently rates as the strongest in its category for AI-agent use cases.
Can RapidDev help set up n8n for my team?
Yes — RapidDev builds self-hosted n8n infrastructure as part of vibe-coder backend setups, including PostgreSQL + Redis queue mode configuration, encryption key management, and workflow architecture for agencies and technical teams. If you're evaluating n8n for your team's stack, a free scoping call is available at rapidevelopers.com/contact.
Outgrowing n8n?
- We build production apps on these platforms
- Custom build when you hit the ceiling
- Fixed price, you own 100% of the code
30-min call. No commitment.