n8n just crossed 185,000 GitHub stars—and it's not because of hype. It's because the tool actually solves the problem that Zapier, Make, and Pipedream created: vendor lock-in.

The Technical Reality

Built on TypeScript (91% of codebase) with Vue.js frontend, n8n runs on Node.js 22+ and supports SQLite, PostgreSQL, and MariaDB. The architecture enables queue mode execution with multi-main scaling for high-availability deployments. You can run it on Docker, npm, or bare metal.

What makes it different from the SaaS alternatives? Self-hosting with zero execution limits. Your NUC or mini PC can run unlimited workflows. No per-step billing, no API throttling, no data leaving your infrastructure.

The MCP Integration That Changed Everything

Version 2.14 introduced official MCP (Model Context Protocol) server support with 16 tools. This is the critical differentiator for AI workflow development.

The MCP tools include:

  • create_workflow_from_code and update_workflow for SDK-based workflow management
  • get_sdk_reference returns actual TypeScript type definitions for exact node parameters
  • search_nodes and get_suggested_nodes for discovering integrations by function
  • validate_workflow catches errors before deployment

Community benchmark: A 13-node workflow was built in 2 minutes with Claude via MCP. Token efficiency hit 31K across 11 MCP calls—the query-on-demand architecture only loads 3% of the node catalog per workflow.

Why Users Are Switching

Reddit sentiment analysis from r/selfhosted and r/automation reveals the real reasons:

  1. Cost: 5-10x cheaper than Zapier at scale. One user built 6 finance automation workflows with Claude Haiku integration for $0.01 per 100 transactions.

  2. Self-hosting: Data privacy, compliance, full control. Homelab users run Headscale monitoring, Telegram notifications, and Reddit content summarization entirely on local hardware.

  3. Technical flexibility: JavaScript and Python code nodes. npm package support. Custom node creation for proprietary APIs.

  4. AI-native: LangChain integration for AI agents. Built-in evaluations framework for testing workflows. Data Tables for persistent AI context storage.

The Learning Curve Problem

Not everything is smooth. Reddit threads from r/automation show legitimate frustration:

"Moving from if-this-then-that to JSON structures, mapping arrays, debugging unclear error messages is hurting my brain." — Beginner user

"Setup that should take 20 minutes often ends up taking 6 hours." — r/automation

The MCP integration has its own issues. AI assistants sometimes generate workflows with outdated node versions from training data. The fix: call get_node before configuring any node to fetch current parameters.

Competitor Positioning

| Feature | n8n | Zapier | Make | Pipedream | |---------|-----|--------|------|-----------|| | Self-hosting | Yes | No | No | Limited | | Pricing model | Per execution | Per task | Per operation | Per execution | | AI integration | Native LangChain | Add-on | Limited | AI steps | | MCP support | Official v2.14+ | No | No | No | | Integrations | 400+ | 6,000+ | 1,500+ | 400+ |

Why people still choose Zapier: integration library (6,000+ apps), enterprise SLAs, lower learning curve for non-technical users, brand recognition.

Funding and Growth

October 2025: $180M Series C at $2.5B valuation. Total funding: $240M. Investors: Accel, Meritech, Redpoint, NVIDIA's NVentures, Sequoia, Felicis. User growth: 6x in 2025. Revenue growth: 10x in 2025.

The company position is clear: AI orchestration platform for technical teams, not consumer automation. The fair-code license (Sustainable Use License + n8n Enterprise License) enables self-hosting while protecting commercial interests.

The Bottom Line

n8n wins for teams that need: self-hosted infrastructure, AI agent orchestration, MCP integration, code flexibility, and cost control at scale. Zapier wins for: non-technical users, maximum integration coverage, and enterprise support ecosystem.

The MCP support is the genuine innovation. It enables Claude, ChatGPT, and Cursor to create and modify workflows directly—something no competitor offers. For AI-first engineering teams, that's the deciding factor.