Best n8n alternatives when self-hosting is a nonstarter

The right alternative depends on the operator's hardest constraint, not on which tool is most popular. Read down the constraint column, then across to the pick.

Every column below is defended against a primary source in the sections that follow. Prices are as of the article's last review date.

Before comparing individual products, separate the two families the shortlist splits into.

Hosted (the vendor runs the server): Make, Zapier, n8n Cloud, Pipedream. You pay a monthly subscription and never touch infrastructure. The pricing is the price. The trade-off is a per-task, per-credit, or per-execution meter.

Open-source self-hosted (you run the server): Activepieces, Windmill, Node-RED, and n8n Community Edition. The software is free (subject to each project's license terms) but the cost is your time and hosting bill. Executions are usually unlimited within what your server can process.

License matters here for procurement and legal review, not just philosophy. Activepieces Community Edition is MIT-licensed. Windmill Community Edition is AGPLv3. Node-RED is Apache 2.0. n8n uses the Sustainable Use License, which is source-available fair-code, not permissive open source. If your organization requires an OSI-approved permissive license, that narrows the shortlist to Activepieces, Windmill, or Node-RED.

Prices verified against each vendor's pricing page on September 9, 2026. Free-tier and code-language claims verified against the vendor's pricing page or documentation on the same date.

Make is the answer for operators who liked n8n's visual workflow editor but do not want to self-host. The visual node editor is philosophically similar (though visually different), the workflow model handles branching and parallel paths cleanly, and the price at typical volumes is competitive with n8n Cloud.

Pricing (verified 2026-09-09): Core is $9 per month at 10,000 credits when billed annually or $12 billed monthly. Pro is $21 per month at 10,000 credits.

Credits are not equivalent to n8n workflow executions, so these prices alone do not establish savings for the same workload — model the actual credit consumption first.

Best avoided when your workflows depend heavily on running arbitrary code. Make has code modules but they are less flexible than n8n's Code node.

Evaluate Zapier if its current catalog supports a required trigger or action missing from your proposed n8n or Make setup. Check the actual connector rather than assuming every niche app is supported.

Pricing (verified 2026-09-09): Professional starts at $19.99 USD per month billed annually for 750 tasks. At 2,000 tasks the annual view shows $49 per month or $73.50 billed monthly. Tasks count billable usage within workflows, so do not compare this allowance one-for-one with n8n executions.

Best avoided when monthly task volumes get large. Per-task pricing scales quickly and Make or a self-hosted tool typically becomes cheaper past a few thousand tasks per month.

Pricing (verified 2026-09-09): The US pricing interface shows n8n Cloud Starter at $24 USD per month billed monthly for 2,500 workflow executions, and Pro at $60 USD monthly for 10,000. The EUR annual view lists €20 and €50 per month respectively; those are distinct currency and billing scenarios, not conflicting quotes for the same purchase.

Self-hosted Community Edition avoids a Cloud subscription but requires hosting, storage, backups, updates, and operational work. Throughput is limited by the server's resources and configuration.

Best avoided when self-hosting was the specific reason you were on n8n in the first place. If Cloud takes that advantage away, other tools become competitive on price.

Activepieces answers a specific question: what if you want n8n's model but need a permissively-licensed open-source foundation? The Community Edition is MIT-licensed per the project's GitHub repository, and the same price applies whether you run it on the vendor's cloud or your own servers.

Pricing (verified 2026-09-09): Free forever with 100 credits per day, unlimited flows, single user, and MCP + API access. Plus is $16 per month billed yearly. Team is $166 per month billed yearly. Ultimate is custom.

AI and MCP: The free plan includes AI agents and Model Context Protocol support. AI steps consume additional credits based on model tier (fast model 2 credits, smart model 10, frontier 20). Plus and above can connect their own AI provider keys, which reduces the credit cost to 1 per step and moves model cost to the user's provider bill.

Integrations: The vendor reports 760+ integrations.

Best avoided when you need a specific niche connector Activepieces hasn't shipped yet — the catalog is smaller than Zapier's — or when your usage pattern generates many rapid runs and would exhaust the free-tier daily credit cap. Free-tier runs pause when the daily quota is exhausted until the next day.

Windmill is a developer platform for workflows, scripts, and internal apps. It is the strongest pick when the team is comfortable writing code and wants unlimited executions on self-hosted infrastructure.

License and self-hosting (verified 2026-09-09): AGPLv3 per the windmill-labs/windmill GitHub repository. Windmill Labs states the Community Edition is free to use internally in an organization without a commercial license. Deployment options documented include Docker Compose, Kubernetes Helm, and Fargate.

Free tier (verified 2026-09-09): Unlimited executions. Up to 50 users total (10 with SSO), 3 workspaces, and 4 groups. Standard triggers (Postgres, WebSocket, MQTT, email) are included. Job-run retention is 30 days.

Paid pricing (verified 2026-09-09): Enterprise starts around $120 per month. The vendor's own configurator produces $170 per month for 1 developer, 2 standard workers (2 compute units), and 8 native subworkers.

Code languages: Windmill's GitHub README lists Python, TypeScript, Go, Bash, SQL, GraphQL, PowerShell, and Rust.

Best avoided when nobody on the team wants to write code, or when your requirement is a visual builder for non-technical stakeholders.

Pipedream sits between the pure no-code tools and self-hosted developer platforms. It is hosted (no server to run) but every workflow step can drop into custom code.

Code languages (verified 2026-09-09): Pipedream's own documentation lists Node.js 20, Python, Go, and Bash as officially supported code-step languages.

Pricing (verified 2026-09-09): Free plan available. Basic is $29 per month monthly ($348 billed annually). Advanced is $49 per month ($588 annually). Connect is $99 per month ($1,188 annually). A Custom tier is available for larger workloads.

Best avoided when the team is non-technical and needs a visual builder, or when self-hosting is a hard requirement — Pipedream's pricing page does not document a self-hosting option.

Node-RED is a flow-based programming tool originally built for wiring together devices, APIs, and event streams. It dominates in IoT, hardware integration, and event-driven workflows, and is a poor fit for most general SaaS automation.

License and cost (verified 2026-09-09): Apache 2.0 per the node-red/node-red GitHub repository. Free. No vendor subscription. Hosting is the operator's responsibility — Node-RED is a Node.js service.

Community: The project reports over 5,000 shared nodes and flows built by the community.

Best avoided when the workload is standard SaaS-to-SaaS automation. Zapier, Make, and Activepieces cover that terrain better and with less operator setup.

The 2026 SERP for n8n alternatives frequently frames the competition as AI-agent orchestration. This is worth naming even though most operators looking for n8n alternatives still want workflow automation, not agent orchestration.

The distinction:

• Workflow automation runs deterministic flows triggered by events. n8n, Make, Zapier, n8n Cloud, Activepieces, Windmill, Pipedream, and Node-RED are all in this camp.
• Agent orchestration runs LLM-driven agents that pick tools and steps at inference time. Products in that camp (Gumloop, Vellum, Lindy) are frequently listed as "n8n alternatives" but solve a different problem.

Where the two overlap: several of the workflow tools ship AI agent and MCP support. Activepieces' free plan explicitly includes AI agents and MCP; n8n itself ships AI agent and LangChain nodes; Pipedream has mature hosted MCP support. If the primary need is agent orchestration rather than workflow automation, an agent platform is a better starting point than any tool on this list — but for straightforward n8n replacement, workflow tools remain the correct category.

No tool on this list directly imports n8n workflow JSON. Every migration is a manual rebuild. Cost estimates below are rough judgment, not measured benchmarks:

• To Make: Rebuild in the Make node editor. Workflows with heavy Code-node logic will need custom code modules or a redesign — Make's code modules are more limited than n8n's Code node.
• To Zapier: Rebuild trigger-by-trigger. If a Zapier connector exists for every integration in the current n8n flow, this can be faster than expected; when a connector doesn't exist, the workflow may not translate at all.
• To n8n Cloud: Trivial. n8n workflows are portable JSON between n8n instances of the same major version.
• To Activepieces: Rebuild in the Activepieces flow editor. AI-agent-heavy workflows may translate well because both platforms treat MCP as first-class.
• To Windmill: Rewrite as scripts and flows in Python, TypeScript, Go, or one of the other supported languages. Most productive when the original n8n workflow had heavy Code-node logic anyway.
• To Pipedream: Rebuild step-by-step. Code steps translate roughly one-to-one for teams already writing Node.js or Python.
• To Node-RED: Only relevant if the flow is IoT or event-driven. General SaaS automation should not migrate here.

n8n workflow JSON is portable between n8n instances and can serve as reference documentation during a rebuild in any tool.

For most operators who cannot self-host: Make. Best combination of price, capability, and workflow model.

For operators whose primary need is app coverage: Zapier.

For teams that specifically need n8n's workflow model but cannot self-host: n8n Cloud is legitimate; do not pick it out of loyalty if Make would serve better.

For teams that require a permissively-licensed open-source foundation and want to self-host: Activepieces (MIT Community Edition) is the sharpest answer today. Windmill (AGPLv3) is the code-first counterpart.

For developer-heavy teams that want hosted execution: Pipedream.

For IoT, hardware, or event-driven workflows only: Node-RED.

These are editorial judgments based on published vendor material, not measured performance benchmarks. Validate against your actual workflow before committing.