Home / Software Alternatives

Make.com Alternatives That Are Actually Open Source: A License-by-License Audit

Red backlit keyboard and code on laptop screen create a tech-focused ambiance.

Photo: Danny Meneses / Pexels

The word "open source" is doing unpaid work in this category

Make is a hosted, proprietary automation platform. The people searching for an open source alternative usually want one of three distinct things, and roundups that blur them serve none: the right to self-host without a license fee, the right to inspect and modify the code, or the right to build a business on top of the tool. Different licenses grant different subsets of those rights, and the most recommended tool in this category grants fewer of them than its reputation suggests.

So this article grades licenses, not feature lists. For each candidate: the exact license, what it permits, what it forbids, and where the boundary between the free code and the paid edition sits. The general Make exit, graded on billing and features at any license, is the Make.com alternatives flagship; the ranked verdict across the whole field is in best Make.com alternatives. This page is only for readers whose requirement is the license itself.

ToolLicenseOSI open source?Self-host freeOffer as a service?
ActivepiecesMIT (core)YesYesYes, core under MIT terms
Node-REDApache-2.0YesYesYes
KestraApache-2.0 (core)YesYesYes, core under Apache terms
WindmillAGPL-3.0YesYesOnly under AGPL network terms
AutomatischAGPL-3.0YesYesOnly under AGPL network terms
n8nSustainable Use LicenseNo (fair-code, source-available)YesNo, restricted by the license

The correction first: n8n is source-available, not open source

n8n is an excellent tool and the most common Make exit, which is exactly why its license deserves precision. n8n ships under the Sustainable Use License, a fair-code license written for the project. It lets you use, modify, and self-host the software for your own internal purposes, and the source is public. What it does not do is meet the Open Source Initiative definition: the license restricts using the software to build a competing hosted service and reserves certain enterprise features for paid editions. Calling n8n open source is not a harmless rounding; a team that embeds n8n into a product it sells can find itself outside the license. If your requirement is "self-host a Make-like builder for my own company," n8n qualifies and its cloud pricing (Starter at $20 per month billed annually for 2,500 executions) is irrelevant because you will never pay it. If your requirement is an OSI license, read on; n8n is not on that list.

MIT and Apache-2.0: the licenses with no traps

Activepieces is the closest structural match to Make that carries a permissive license: a visual builder with pieces (its word for integrations) whose community edition core is MIT-licensed. MIT is the shortest serious license in software: use, copy, modify, and distribute, including commercially and as a service, with attribution. The edition boundary is the thing to audit rather than the license: some enterprise features sit outside the MIT core, so a team that needs those specific features is buying a commercial license for them while the core stays MIT. For a Make refugee who wants the visual model without copyleft or fair-code conditions, this is the bench leader.

Node-RED is the elder of the category: a flow-based automation runtime from the Node.js ecosystem, Apache-2.0 licensed, stewarded under the OpenJS Foundation. Apache-2.0 grants the same broad rights as MIT plus an explicit patent grant, which matters to companies whose legal teams review licenses rather than vibes. Node-RED is more runtime than product: you wire nodes on a canvas and the result is closer to a program than to a Make scenario, dashboards and integrations are community-built, and there is no vendor cloud story to upsell you. For engineers leaving Make because they wanted code-shaped control with a visual surface, it is the most defensible license on this page and the oldest codebase here.

Kestra takes the same Apache-2.0 core in a different direction: workflows declared as YAML, event-driven orchestration, Git sync, built for data and platform engineers rather than operations teams connecting SaaS apps. Its open source edition is the real product for self-hosters; the cloud and enterprise editions add governance and are priced in ways this dataset records as honest nulls rather than guessing. If your Make scenarios were really data pipelines wearing an automation costume, Kestra's license and its shape agree with each other.

AGPL-3.0: genuinely open source, with a network clause

Windmill and Automatisch are both AGPL-3.0, which is an OSI-approved license with one famous condition: if you modify the software and let others use it over a network, you must offer those users the modified source. For a company self-hosting either tool internally, AGPL costs nothing and restricts nothing in practice. For a company planning to resell automation as a service built on either tool, AGPL is the whole business model question, and it must be answered with the license text, not with a blog post.

The tools themselves differ sharply. Windmill is developer-first: scripts in Python, TypeScript, and other languages become scheduled jobs, internal apps, and APIs, and it is dramatically faster than polling-based builders for code-shaped work. Automatisch is the closest AGPL answer to Make's own shape: a visual, no-code builder for connecting apps and automating busywork, younger and smaller in integration count, but legible to the non-engineers who actually used Make. Choose Windmill when the authors are developers; choose Automatisch when they are not.

What self-hosting actually commits you to

Every tool on this page is free as in license; none is free as in operations. A self-hosted automation platform is production infrastructure: it holds credentials for every service it touches, so it needs patching, backups, access control, and someone paged when it stops at 3 a.m. The Make bill you are escaping buys exactly that operational burden being someone else's. The license audit below is the checklist to run before adopting any of these, because the license determines what you may do with the tool after the honeymoon: embed it, resell it, modify it, or walk away from a paid edition boundary you did not know existed.

Interactive tool

Comparison Builder

Pick two or three products and see them side by side on the numbers that decide the purchase.

MeasureActivepiecesn8nNode-RED
Starting paid priceFree$20 per month, flatFree
Free optionFree plan: the self-hosted Community Edition is free under MITFree plan: the self-hosted Community Edition is free with unlimited executions on your own server; cloud plans have no free tierFree plan: the whole tool is free and open source; there is no paid tier
PlansCommunity Edition (self-hosted): free · Cloud paid tiers: not publishedStarter (Cloud): $20/mo flat · Pro (Cloud): $50/mo flat · Business (self-hosted license): $800/mo flatNode-RED: free
PlatformsWeb, Linux, DockerWeb, Self-hostedLinux, macOS, Windows, Raspberry Pi
Best forteams leaving hosted automation bills, self-hosted Zapier-shaped workflows, agencies standardizing flowstechnical teams with multi-step workflows, makers who can self-host, teams burned by per-step billinghome automation logic, IoT glue, self-hosted integrations
StrengthsFamiliar builder with an open source core; Self-host to keep data and costs in-house; Growing pieces library for common SaaS toolsBills per whole execution, so a 30-step workflow costs the same as a 2-step one; Free self-hosted edition with no execution cap; Unlimited users on every planVisual flows with real logic: functions, switches, and subflows; Huge community node library for devices and services; Runs on very small hardware
Watch out forCloud pricing reads conflict, so verify before budgeting; Smaller integration catalog than Zapier; Enterprise features sit outside the MIT editionCloud has no free tier; free means running your own server; Business is self-hosted only and jumps to $800 a month; Self-hosting means you own updates, backups, and uptimeYou host, secure, and back it up yourself; Flow sprawl needs discipline at scale; No hosted consumer tier to fall back on

Lowest entry price: Activepieces at Free per month flat. Real free plan: Activepieces, n8n, Node-RED. Entry price is the floor, not the decision: check the plan line above for the tier that actually includes the feature you need.

All figures from vendor pricing pages, checked November 18, 2026. Some vendors price by contacts, tasks, or operations instead of seats; those notes are in the plan data and the linked pricing guides.

Interactive tool

Run the license audit before you adopt

Check off each step as you finish it. Your progress stays on this page.

0 of 5 complete

0% done

The verdict by intent

You want Make's visual builder under a permissive license: Activepieces, MIT core, with the edition boundary audited before you depend on an enterprise feature. You want the most legally boring license in the category and your authors are engineers: Node-RED (Apache-2.0) or Kestra (Apache-2.0 core) for pipeline-shaped work. Your authors are developers who think in scripts: Windmill, accepting AGPL terms that only bite if you resell it as a service. Your authors are non-engineers and you want a Make-shaped canvas: Automatisch under AGPL-3.0, or Activepieces if the AGPL network clause is a problem. You just want to self-host cheaply and will never resell anything: n8n is a fine tool, adopted with your eyes open about the fact that its Sustainable Use License is fair-code, not open source.

Related guides

More from this corner of the chart: these companion guides compare the nearest alternatives and head to head matchups.

Frequently asked questions

Is n8n really not open source?

Correct, under the OSI definition. n8n uses the Sustainable Use License, a fair-code license: the source is public and self-hosting for internal use is free, but the license restricts offering the software as a competing service and reserves some features for paid editions. It is source-available, which is a different and narrower thing than open source.

Which Make alternative has the most permissive license?

Activepieces (MIT core) and Node-RED and Kestra (Apache-2.0) are the permissive end of the bench. MIT and Apache-2.0 allow commercial use, modification, and offering the software as a service; Apache-2.0 adds an explicit patent grant, which some legal teams prefer.

What does AGPL-3.0 actually restrict?

AGPL-3.0 restricts one specific thing: if you modify the software and provide it to users over a network, you must make your modified source available to those users. Internal self-hosting for your own team triggers no obligation. It matters when the plan is to build a hosted product on top of Windmill or Automatisch.

Can I self-host these tools for free forever?

The licenses say yes for the editions listed: Activepieces' MIT core, Node-RED, Kestra's Apache-2.0 core, Windmill, and Automatisch can all be self-hosted without a license fee. The costs that remain are yours: servers, patching, backups, and the credentials security of a platform that holds keys to your other services.

Why does the license matter if I am not a lawyer?

Because the license decides three practical questions: whether you may embed the tool in something you sell, whether a feature you depend on can move behind a paid edition boundary, and whether you can take your workflows and leave if the vendor changes terms. Those are business questions that happen to be answered in legal text.

What is the closest open source match to Make itself?

Activepieces for shape: a visual builder with a large integration catalog, under an MIT core. Automatisch is the AGPL-3.0 option with a similarly no-code shape but a smaller catalog. Node-RED and Kestra are better tools for engineers than they are Make lookalikes, and Windmill is a script platform first.

Photo credits: Danny Meneses (Pexels). Photos are served from this site; follow the credit to the library page for the original.