Home  >  Companies  >  n8n
Fair-code workflow automation and AI orchestration platform available as self-hosted Community Edition, n8n Cloud, and enterprise deployments

Revenue

$100.00M

2026

Valuation

$2.50B

2025

Funding

$253.50M

2025

Details
Headquarters
Berlin, Germany
CEO
Jan Oberhauser
Website
Milestones
FOUNDING YEAR
2019

Revenue

Sacra estimates that n8n hit $100M in annual recurring revenue (ARR) in April 2026, up from $70M at the end of 2025.

Growth accelerated as n8n shifted from general-purpose workflow automation toward AI orchestration. By late 2025, more than 80% of workflows on the platform involved AI agents. The free self-hosted Community Edition had 1.7 million monthly active builders, providing a funnel into n8n Cloud and Enterprise subscriptions as teams moved from experimentation to governed production deployments.

n8n increasingly charges for complete workflow executions rather than individual steps or seats, allowing revenue to expand as customers run more production automations across their organizations.

Valuation & Funding

SAP invested more than EUR 60M in n8n in May 2026 at a $5.2B valuation, more than double the prior round's valuation. The investment included a multi-year commercial agreement to embed n8n inside SAP Joule Studio.

n8n raised a $180M Series C in October 2025 at a $2.5B valuation, led by Accel with participation from Meritech Capital Partners and Redpoint. Highland Europe previously led a EUR 55M (approximately $60M) Series B in March 2025. Felicis Ventures led the Series A, with earlier participation from Sequoia Capital, firstminute capital, HV Capital, Visionaries Club, NVentures, T.Capital, Harpoon Ventures, and Evantic Capital.

Total primary funding raised stands at approximately $240M, excluding the SAP secondary investment.

Product

n8n is a visual workflow automation and AI orchestration platform. Users build workflows on a canvas by connecting nodes, each of which performs a discrete job, such as reading or transforming data, calling an AI model, running JavaScript or Python, branching on a condition, waiting for human approval, or writing to another system.

Workflows start with a trigger, such as a form submission, webhook, scheduled time, or chat message. Data then flows through connected nodes, with users able to inspect the input and output of each step. A lead-handling workflow, for example, might receive a form submission, look up the company through an enrichment provider, ask an LLM to classify the lead, apply deterministic routing rules based on geography and deal size, create a CRM record, and notify a sales rep in Slack within one visual graph.

The platform connects to more than 1,000 integrations. When a dedicated node is unavailable, users can call any REST or GraphQL API through an HTTP Request node, import a cURL command, install a community-built node, or write a custom one. This combination of visual building and unrestricted code lets a business operator configure standard nodes while an engineer adds a custom transformation or internal API call within the same workflow.

For AI agent orchestration, an AI Agent node combines a language model, system instructions, permitted tools, optional memory, and structured output parsing. Tools can include other n8n nodes, HTTP calls, MCP tools, or sub-workflows. The agent determines which tool to call and what to do next, while deterministic steps handle known API calls, compliance checks, and data updates. Human approval gates can pause execution before actions such as issuing refunds or modifying customer records.

Chat Hub provides a ChatGPT-like interface through which non-technical employees can interact with approved agents and models without accessing the workflow canvas, separating builders who maintain workflows from employees who use them through natural language. n8n's AI Workflow Builder generates functioning workflows from written descriptions, while its instance-level MCP server lets external AI tools such as Claude Code or Cursor create and execute n8n workflows programmatically.

Customers can use n8n Cloud, managed by n8n and hosted in Frankfurt, or self-host through Docker, Kubernetes, or other customer-controlled infrastructure. Self-hosting gives organizations network access to private systems and control over data residency and upgrade timing. Version 2.0, released in December 2025, added secure-by-default behavior, execution isolation, autosave, versioned publishing, and concurrency protection for multi-user editing.

Business Model

n8n uses its free, source-available Community Edition as a bottom-up acquisition channel. Organizations convert to paid plans when workflows become operationally important and require collaboration, governance, security, or managed infrastructure. Its B2B go-to-market combines product-led adoption with enterprise sales.

Monetization has three channels. n8n Cloud subscriptions start at EUR 20 per month for 2,500 executions and scale through Pro and Enterprise tiers. Paid self-hosted Business and Enterprise licenses allow customers to run n8n on their own infrastructure while paying for SSO, SAML, LDAP, role-based access, Git-based environments, scaling, audit capabilities, and support. Under OEM and embed agreements, software vendors integrate n8n's workflow engine into their products with annual execution-volume commitments. The SAP partnership embeds n8n in Joule Studio, with usage drawing from customers' existing SAP BTP consumption credits.

Pricing is execution-based: a complete workflow run counts as one execution, regardless of how many nodes it contains. All paid plans include unlimited users and workflows, tying revenue expansion to production usage rather than seat count. Complex, multi-step workflows can therefore cost less on n8n than on platforms that charge per task or operation, while unlimited users reduce the cost of adding collaborators.

Expansion typically starts when an individual developer automates a task. A small team then creates shared workflows, additional departments request automations, and the workflows become business-critical, prompting the organization to purchase Business or Enterprise for governance, environments, and support. Higher execution volume and adoption across departments expand the contract over time. Consultants and systems integrators add delivery capacity without requiring n8n to scale professional services at the same rate.

Competition

n8n competes across horizontal SaaS automation, enterprise integration, and AI agent infrastructure. Competition is shifting from connecting applications to governing AI agents that take actions across applications.

Cloud-first automation

Zapier is the most recognizable competitor among SMBs and business users, with more than 9,000 integrations and broad brand recognition. Its managed authentication layer and new MCP and SDK capabilities allow developers to use its integration catalog from external agent environments. Make targets mid-market operations teams with visual tools for complex workflows, more than 3,000 integrations, and AI agent capabilities. Both offer simpler onboarding for basic SaaS-to-SaaS automation.

n8n differentiates on complex workflows and pricing. Task-based pricing on Zapier and credit-based pricing on Make become expensive for multi-step processes, while n8n charges for complete executions with unlimited steps. Neither Zapier nor Make offers comparable self-hosting, data residency control, or native code extensibility.

Enterprise integration platforms

Workato and Tray.io compete for enterprise integration and process automation budgets through governance, connector certification, and established procurement relationships. UiPath offers a broader automation stack spanning RPA, process mining, document processing, and agent orchestration through Maestro. Microsoft Power Automate and Copilot Studio bundle workflow and agent capabilities into existing Microsoft 365 and Azure contracts, reducing the apparent incremental cost of automation for Microsoft-standardized organizations.

n8n competes through deployment neutrality, bottom-up adoption, and model-agnostic AI orchestration. Its weakness is that self-hosting may require more internal platform engineering and governance design at large enterprises, while traditional iPaaS vendors offer more turnkey compliance and broader implementation partner networks.

Open-source and code-first alternatives

Activepieces is the closest open-source challenger, offering an MIT-licensed Community Edition with no caps on users, flows, or runs. This model is attractive for embedded and white-label use cases where n8n's Sustainable Use License creates friction. Windmill targets engineering teams that want code as the primary artifact, with workflows layered around it, while Node-RED retains a niche in IoT and edge deployments.

Among code-first agent tools, LangGraph and Temporal compete when developers need granular control over agent state, durable execution, and detailed evaluation. These frameworks lack n8n's business-app connectors and visual accessibility, but can serve as the production runtime for high-value, long-running agent processes. Replit, Lovable, Bolt.new, and Base44 also overlap as AI application builders move into workflow execution, although workflow-specific and app-builder products are likely to coexist.

Platform bundling

The longer-term threat is vertical integration by systems-of-record vendors. Workday acquired Pipedream for developer connectivity, Flowise for low-code agents, and Sana for knowledge and UX, assembling an orchestration stack grounded in HR and finance data. Salesforce combines Agentforce, MuleSoft, and Data Cloud. SAP is both a partner and a potential competitor if it deepens native orchestration inside Joule.

n8n's response is vendor neutrality. Customers may resist making a single application vendor the control plane for workflows spanning multiple systems. n8n markets itself as the independent orchestration layer, but must preserve that identity as its SAP relationship deepens.

TAM Expansion

n8n's TAM expansion follows a progression from developer workflow automation to enterprise AI infrastructure, broadening both its addressable market and revenue opportunity per customer.

From builder tool to employee-facing AI layer

Chat Hub extends n8n from a platform for technical builders to an internal interface used across organizations. A small group of developers can create governed agents that thousands of employees access through natural language, shifting the unit of expansion from workflow creators to enterprise-wide active users and agent interactions.

This builder-and-consumer split allows n8n to monetize both automation development and the execution volume generated by a broader workforce. Trendyol reported more than 1,000 users and 700 active workflows, while Stepstone expanded from four early users toward a 3,000-employee rollout, showing how adoption can extend beyond the original technical team.

Enterprise integration and iPaaS displacement

n8n can expand from departmental automation into the broader integration-platform-as-a-service market, competing for budgets held by Workato, MuleSoft, and legacy middleware. Its execution-based pricing, with unlimited users and workflow steps, can reduce costs for complex, multi-step enterprise processes relative to per-task or per-operation platforms.

Enterprise workloads include ERP and CRM synchronization, employee onboarding, IT service management, security response automation, document intake and classification, procurement, and supply-chain operations. The August 2025 pricing redesign removed active-workflow limits and shifted monetization to executions, enabling broader organizational adoption and the consolidation of more processes on n8n.

Strategic distribution and sovereign deployment

The SAP partnership gives n8n access to large enterprises that might otherwise reject a younger independent vendor during procurement. n8n runs as a managed environment on SAP Business Technology Platform, uses existing BTP consumption credits, and connects to SAP context and Knowledge Graph data. The arrangement could serve as a repeatable model for ecosystems where n8n provides the orchestration layer and the partner provides distribution and installed-base access.

Self-hosting differentiates n8n as enterprises seek to keep models, credentials, and sensitive data within controlled environments. Private-cloud, air-gapped, and sovereign deployments expand its addressable market in financial services, healthcare, the public sector, and other regulated industries across Europe, the Middle East, and Asia, where US-hosted SaaS may not meet procurement or data-residency requirements. A free self-hosted edition, local-model support, and a browser-based development experience provide a lower-cost entry into these geographies before local sales investment.

Risks

Platform commoditization: Microsoft, Salesforce, Workday, and SAP are incorporating multi-agent orchestration, MCP connectors, identity management, and organizational-data access into their installed platforms, which could relegate n8n to edge integration as strategic orchestration shifts to vendors that already control identity, productivity applications, and core business data.

Licensing and monetization tension: The free self-hosted Community Edition allows many technical teams to operate substantial workloads without paying n8n, while the Sustainable Use License's restrictions on external-facing and white-label use create friction for agencies, SaaS builders, and potential embedding partners, and tighter enforcement could weaken the community goodwill behind n8n's distribution advantage.

Security concentration: n8n instances hold application credentials and can execute arbitrary code across connected systems, making a compromised deployment a high-value target, while 2026 security advisories included multiple high or critical issues involving sandbox escapes, remote code execution, and credential exfiltration, a pattern that could undermine enterprise trust even when fixes are released quickly, particularly because self-hosted customers are responsible for patching.

News

DISCLAIMERS

This report is for information purposes only and is not to be used or considered as an offer or the solicitation of an offer to sell or to buy or subscribe for securities or other financial instruments. Nothing in this report constitutes investment, legal, accounting or tax advice or a representation that any investment or strategy is suitable or appropriate to your individual circumstances or otherwise constitutes a personal trade recommendation to you.

This research report has been prepared solely by Sacra and should not be considered a product of any person or entity that makes such report available, if any.

Information and opinions presented in the sections of the report were obtained or derived from sources Sacra believes are reliable, but Sacra makes no representation as to their accuracy or completeness. Past performance should not be taken as an indication or guarantee of future performance, and no representation or warranty, express or implied, is made regarding future performance. Information, opinions and estimates contained in this report reflect a determination at its original date of publication by Sacra and are subject to change without notice.

Sacra accepts no liability for loss arising from the use of the material presented in this report, except that this exclusion of liability does not apply to the extent that liability arises under specific statutes or regulations applicable to Sacra. Sacra may have issued, and may in the future issue, other reports that are inconsistent with, and reach different conclusions from, the information presented in this report. Those reports reflect different assumptions, views and analytical methods of the analysts who prepared them and Sacra is under no obligation to ensure that such other reports are brought to the attention of any recipient of this report.

All rights reserved. All material presented in this report, unless specifically indicated otherwise is under copyright to Sacra. Sacra reserves any and all intellectual property rights in the report. All trademarks, service marks and logos used in this report are trademarks or service marks or registered trademarks or service marks of Sacra. Any modification, copying, displaying, distributing, transmitting, publishing, licensing, creating derivative works from, or selling any report is strictly prohibited. None of the material, nor its content, nor any copy of it, may be altered in any way, transmitted to, copied or distributed to any other party, without the prior express written permission of Sacra. Any unauthorized duplication, redistribution or disclosure of this report will result in prosecution.