The 9 best n8n alternatives in 2026, compared

The short answer. The strongest n8n alternatives in 2026 are Activepieces and Windmill if you want to stay open source and self-hosted, Node-RED for event-driven and edge workloads, Tray.ai, Workato, and Microsoft Power Automate if you need managed governance, Make and Zapier for visual automation with no infrastructure to run. Pipedream used to be the pick for developers who would rather write code, but its Workflows product closes on 31 March 2027, so don’t start a migration there.

Teams leave n8n for three reasons. They are tired of operating and patching it. They have hit a limit in production. Or a compliance review has asked who owns audit, access control, and accountability when the automation layer runs on their own infrastructure. Work out which one applies and the list gets short fast.

n8n alternatives at a glance

Pricing checked against each vendor’s published pricing page on 17 September 2026; n8n, Make, Zapier, Activepieces and Windmill re-checked 8 October 2026. n8n publishes in euros. Platforms marked no published price do not publish list prices, including Tray.ai.

n8n’s per-execution pricing is a reasonable model at pilot scale. It’s a different question once you look at what you own at volume.

Open-source alternatives you run yourself

Activepieces

Best for: teams that want to stay open source and self-hosted with a builder close to what they already know.

Activepieces is the closest open-source peer to n8n. The node-based builder is familiar, the project is active, and there is a managed cloud option if you want to stop hosting without changing tools. It has agents on every plan and a built-in MCP server that builds, tests, and publishes flows from your AI assistant.

Trade-offs: it lists 765 pieces, so check your own systems against that list. Its SOC 2 Type 2 program is in progress, not yet certified, by its own account. Self-hosting keeps the operational load you already have: patching, scaling, backups, uptime. Governance is tiered the same way n8n tiers it. SSO and standard roles start on the $200 a month Team plan. SCIM, custom RBAC, audit logs, and secret managers are in the custom-priced Ultimate tier.

Windmill

Best for: engineering teams that would rather write TypeScript, Python, or Go than assemble nodes.

Windmill treats a script as the unit of work and builds flows around it. If most of your n8n workflows are code nodes strung together, the visual layer is adding nothing and Windmill drops it. Flows can include an AI agent step that uses your scripts as tools, and an MCP server exposes scripts and flows to AI assistants, scoped by token.

Trade-offs: non-engineers will not build here. Self-hosting responsibilities are unchanged. The free self-hosted edition has unlimited executions, but SSO past 10 users, audit logs, and SLA-backed support are in the Enterprise tier, which starts at $120 a month and scales with seats and compute units.

Node-RED

Best for: event-driven automation, IoT, and workloads that run close to the hardware.

Node-RED is a long-running open-source flow editor under the OpenJS Foundation, with a large community and no vendor pricing.

Trade-offs: paid support and an SLA come only through a third party such as FlowFuse, which also offers an MCP Server node that exposes flows as tools. The project itself has no SSO, access control, or audit trail, so you build those or add them. It was built for event routing, not business system integration, and the community node catalogue reflects that.

Managed platforms with built-in governance

Tray.ai

Best for: teams that have outgrown self-hosting and need governed access, audit, and agent orchestration on infrastructure someone else runs.

Tray.ai covers integration, automation, and AI agents in one managed platform. The difference from n8n is operational. There is no runtime to size, patch, or keep available. Access control, audit, and agent governance ship with the platform. Agent Gateway controls what an agent can call, per tool and per user, and logs every action.

If you built in n8n from an editor, Tray Headless does the same job. It builds workflows, connectors, authentication, and validation from Claude Code, Cursor, or any MCP client, against the hosted platform, and everything opens in the visual builder. There is a direct comparison with n8n for feature-level detail, and the migration kit covers moving existing workflows.

Trade-offs: we do not publish list pricing, so you cannot evaluate cost without talking to us. It is managed cloud only. If you have a hard requirement to run automation inside your own infrastructure, use one of the open-source options above.

Workato

Best for: large IT-led integration programs where business and technical teams share a governed library of automations.

Workato is a mature enterprise iPaaS with a recipe-based builder and a large connector catalog. It is the established choice when central IT owns the automation program and delegates building to business teams inside guardrails.

It also ships Agent Studio and an MCP Gateway with per-user auth and audit logs.

Trade-offs: Workato publishes no prices, so forecasting starts with a quote rather than a meter you can read. The recipe abstraction constrains deep branching and nested logic, and recipe concurrency defaults to 1 and tops out at 30 unless Customer Success raises it. We cover how Tray and Workato compare on pricing structure and governance separately.

Microsoft Power Automate

Best for: organizations already standardized on Microsoft 365, Azure, and Copilot Studio.

If you already run Microsoft, Power Automate is the least work to adopt. Identity, licensing, and admin are in place, coverage of Microsoft products is deep, and Copilot Studio agents can use MCP servers.

Trade-offs: the full Microsoft integration story spans Power Automate, Logic Apps, Azure Data Factory, and Copilot Studio, each with its own admin and licensing. Premium is $15 per user per month billed yearly, and unattended RPA is priced separately at $150 per bot per month, so your bill tracks headcount and bots, not workflow volume. There’s a fuller breakdown of how Tray compares with Power Automate and Logic Apps across non-Microsoft systems.

Visual automation without the operational load

Make

Best for: visual builders who want credit-based pricing and published rates.

Make gives you a visual canvas with more structural flexibility than a linear trigger-action model, at a lower entry price than most platforms here. It also has Make AI Agents (labelled beta) and an MCP server.

Trade-offs: cloud only, no self-hosted option. A single scenario run is capped at 40 minutes on paid plans, and Make’s security page does not mention HIPAA. If a compliance review is what moved you off n8n, that gap is the thing to check first. See how Tray and Make differ on audit and access control.

Zapier

Best for: the widest connector catalog and the fastest path from idea to running automation.

Zapier connects more applications than anything else on this list and takes the least setup.

It also ships Zapier Agents and a hosted Zapier MCP server, where each tool call uses two tasks.

Trade-offs: a Code step runs for 30 seconds on Pro and Team, published task tiers top out at 2M a month, and per-task billing adds up at volume. SCIM is Enterprise only, and Zapier does not support HIPAA. We lay out where those engine limits sit against Tray’s, and what per-task billing looks like at volume.

Pipedream

Best for: no longer a place to move workflows to.

Pipedream was the code-first pick on this list: it bills compute rather than tasks and supports several languages. Workday acquired it, and Pipedream now says Workflows is shutting down on 31 March 2027, with no new signups in the meantime (checked 8 October 2026). Its focus is Connect, an integration layer for developers building their own AI agents.

Trade-offs: if you are leaving n8n for Pipedream Workflows, you would be migrating twice. We cover what that means if you are already on Pipedream.

How to choose

• Stay open source and self-hosted, with a familiar builder: Activepieces
• Stay self-hosted but write code instead of building nodes: Windmill
• Event-driven or edge workloads: Node-RED
• Stop operating infrastructure, and governance is why you are moving: Tray.ai
• Central IT owns the program and delegates building: Workato
• Already standardized on Microsoft: Power Automate
• Visual building at the lowest published price: Make
• Largest connector catalog: Zapier
• Write code on managed infrastructure: Windmill’s cloud edition, now that Pipedream Workflows is closing

What actually moves teams off n8n

Three things come up repeatedly. There are five signs you have outgrown it if you want the longer version, and a breakdown of what staying costs in risk, overhead, and scale.

Operational cost. Most of the cost of self-hosted n8n is engineering time. Updates, monitoring, backups, and incident response all land on someone, and none of it shows up on an invoice. We broke down what self-hosting n8n actually costs and built a calculator so you can work out your own number.

Security and patching. We keep a running n8n security tracker with every high and critical advisory since December 2025, the versions each affects, and the release that fixes it. The count moves with every refresh, so the tracker states the current figure rather than this post. Check the version you run against the list in your browser. On 11 March 2026, CISA added one of them, CVE-2025-68613, to its Known Exploited Vulnerabilities catalog: confirmed exploitation, in the wild. In May 2026, Singapore’s Cyber Security Agency reported that a later fix circumvented an earlier one, so instances that had already patched were still exposed. Every one of these has a patch. Each patch is an upgrade someone has to schedule, test, and roll out, and self-hosted, that queue is yours, which is the question behind who patches when the next CVE drops.

Compliance scope. When a customer or an auditor asks who is responsible for the automation layer, a self-hosted deployment puts that scope on you. n8n runs a public trust centre at trust.n8n.io covering its own service. That scope stops at the instance you run yourself, which is who owns your SOC 2 report when you self-host.

These are arguments about who carries the operational burden. The software is good. The answer changes once a deployment stops being a few workflows and starts being something the business depends on.

Sources

Vendor pricing, checked 8 October 2026 unless marked:

• n8n pricing
• Make pricing, which also lists the 40-minute scenario run limit
• Zapier pricing, for task tiers, Code step limits and SCIM
• Activepieces pricing
• Windmill pricing
• Microsoft Power Automate pricing, checked 17 September 2026

Vendor and public-body documentation:

• Workato recipe settings, for recipe concurrency
• Zapier: Is Zapier HIPAA compliant?
• Pipedream Workflows, for the 31 March 2027 shutdown
• CVE-2025-68613 in the National Vulnerability Database, and the CISA Known Exploited Vulnerabilities catalog

Agent and MCP details for each vendor are linked from its comparison page, alongside the sources behind them.