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.
| Tool | License | OSI open source? | Self-host free | Offer as a service? |
|---|---|---|---|---|
| Activepieces | MIT (core) | Yes | Yes | Yes, core under MIT terms |
| Node-RED | Apache-2.0 | Yes | Yes | Yes |
| Kestra | Apache-2.0 (core) | Yes | Yes | Yes, core under Apache terms |
| Windmill | AGPL-3.0 | Yes | Yes | Only under AGPL network terms |
| Automatisch | AGPL-3.0 | Yes | Yes | Only under AGPL network terms |
| n8n | Sustainable Use License | No (fair-code, source-available) | Yes | No, 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.
