n8n-io/n8n

n8n is a mature, production-grade automation platform with massive adoption (182k stars, 56k forks) and significant community velocity. Its defensibility derives from: (1) extensive integration catalog (400+) with ongoing maintenance burden creating switching costs; (2) established community and ecosystem (plugins, templates, documentation); (3) self-hosting option creating data gravity for enterprises; (4) hybrid code/no-code model differentiating it from pure visual builders. However, defensibility is constrained by: (1) the core value proposition (workflow automation with visual builder + integrations) is well-understood and reproducible—Zapier, Make, Temporal, Prefect, and others already compete directly; (2) no defensible IP or network effects beyond network of integrations; (3) dominated by large SaaS incumbents (Zapier, Make) that have brand, enterprise sales, and deeper integration portfolios. Platform Domination Risk is HIGH because: cloud giants (AWS, Google, Azure) are investing in low-code automation (AWS Step Functions + visual builders, Google Cloud Workflows, Azure Logic Apps). OpenAI/Anthropic could embed workflow automation into agent products. The self-hosting advantage is eroding as platforms add on-prem/hybrid options. Market Consolidation Risk is HIGH because: Zapier and Make are well-capitalized, have deeper enterprise relationships, and could trivially acquire n8n's user base. n8n's open-source nature is an asset but also a liability—competitors can fork and cloud-wrap it. Displacement Horizon is 1-2 years because: (1) platform vendors are actively building low-code automation features; (2) agent frameworks (LangChain, LlamaIndex) increasingly integrate workflow orchestration; (3) competitor consolidation is ongoing (Make acquired multiple competitors). n8n's defensibility hinges on maintaining community momentum and integration moat faster than platforms can replicate. The 0.0/hr velocity is a concern and may reflect stalled momentum or measurement artifact. The project is NOT a breakthrough—it applies known orchestration patterns (borrowed heavily from Zapier/Make) with a self-hosting angle. Its fair-code model (source-available, not open-source) is a hedging strategy against commoditization but provides limited legal moat.