Open-source automation licences: what you can do commercially
Twelve of 17 projects carry an OSI-approved licence, and six set conditions on hosting or resale OSI list.
Automatisch is in both counts, because AGPL is OSI-approved but adds a source duty Automatisch AGPL.
Abstract
This guide reads the licence files of 17 automation, orchestration and AI-workflow projects. It answers four commercial questions for each: internal use, hosting for clients, embedding in a paid product and selling a hosted service. Each file was read from the project's own repository and re-checked on 16 Nov 2026.
Key figures
Licences on OSI's approved list
- Mixed
- Windmill
- Not listed
- n8n, Inngest, Pipedream, Dify
Windmill LICENSE, second change since 2025
- First change
- 7 Mar 2025
- Internal use
- no commercial licence needed
Flowise repository, read-only
- Licence
- Apache 2.0, enterprise folder apart
- Announced
- 29 Jul 2026
Which projects are actually open source?
Twelve of 17 projects carry an OSI-approved licence.
Windmill is split, while n8n, Inngest, Pipedream and Dify sit outside OSI's list altogether OSI list.
| Project | OSI-approved? | Licence in repo | Separate enterprise licence |
|---|---|---|---|
| OSI-approved licence 12 | |||
| Activepieces | Yes | MIT | packages/ee/ and server ee folder |
| Node-RED | Yes | Apache 2.0 | None found |
| Huginn | Yes | MIT | None found |
| Automatisch | Yes | AGPL-3.0 | Files with .ee. in the name |
| Kestra | Yes | Apache 2.0 | Enterprise Edition features beyond the repo |
| Apache Airflow | Yes | Apache 2.0 | None found |
| Temporal | Yes | MIT | None found |
| Prefect | Yes | Apache 2.0 | None found |
| Dagster | Yes | Apache 2.0 | None found |
| Trigger.dev | Yes | Apache 2.0 | None found |
| Langflow | Yes | MIT | None found |
| Flowise | Yes | Apache 2.0 | Enterprise folder |
| Mixed 1 | |||
| Windmill | Mixed | AGPLv3, Apache 2.0 for client libraries and OpenFlow spec, proprietary Community Edition build | Enterprise-flagged code |
| Not on OSI's list 4 | |||
| n8n | No | Sustainable Use License 1.0 | Files with .ee. in the name |
| Inngest | No | SSPL 1.0, Apache 2.0 after 3 years | None found |
| Pipedream (public repo) | No | Pipedream Source Available License 1.0 | None found |
| Dify | No | Modified Apache 2.0 | Commercial licence from the producer if its conditions are met |
In words
- n8n, Not on OSI's list: Sustainable Use License 1.0 n8n licence. Separate enterprise licence: Files with .ee. in the name n8n licencen8n EE licence.
- Activepieces, OSI-approved: MIT Activepieces licence. Separate enterprise licence: packages/ee/ and server ee folder Activepieces licenceActivepieces ee licence.
- Node-RED, OSI-approved: Apache 2.0 Node-RED licence. Separate enterprise licence: None found.
- Windmill, Mixed: AGPLv3, Apache 2.0 for client libraries and OpenFlow spec, proprietary Community Edition build Windmill licence. Separate enterprise licence: Enterprise-flagged code Windmill licence.
- Huginn, OSI-approved: MIT Huginn licence. Separate enterprise licence: None found.
- Automatisch, OSI-approved: AGPL-3.0 Automatisch licence. Separate enterprise licence: Files with .ee. in the name Automatisch licenceAutomatisch EE licence.
- Kestra, OSI-approved: Apache 2.0 Kestra README. Separate enterprise licence: Enterprise Edition features beyond the repo Kestra README.
- Apache Airflow, OSI-approved: Apache 2.0 Airflow licence. Separate enterprise licence: None found.
- Temporal, OSI-approved: MIT Temporal licence. Separate enterprise licence: None found.
- Prefect, OSI-approved: Apache 2.0 Prefect licence. Separate enterprise licence: None found.
- Dagster, OSI-approved: Apache 2.0 Dagster commit. Separate enterprise licence: None found.
- Trigger.dev, OSI-approved: Apache 2.0 Trigger.dev licence. Separate enterprise licence: None found.
- Inngest, Not on OSI's list: SSPL 1.0, Apache 2.0 after 3 years Inngest licence. Separate enterprise licence: None found.
- Pipedream (public repo), Not on OSI's list: Pipedream Source Available License 1.0 Pipedream licence. Separate enterprise licence: None found.
- Langflow, OSI-approved: MIT Langflow licence. Separate enterprise licence: None found.
- Flowise, OSI-approved: Apache 2.0 Flowise licence. Separate enterprise licence: Enterprise folder Flowise licenceFlowise EE licence.
- Dify, Not on OSI's list: Modified Apache 2.0 Dify licence. Separate enterprise licence: Commercial licence from the producer if its conditions are met Dify licence.
- OSI status of each licence is from OSI's list of approved licences OSI list.
- Five repos hold enterprise code under a separate licence: n8n, Activepieces, Windmill, Automatisch and Flowise n8n licenceActivepieces licenceWindmill licenceAutomatisch licenceFlowise licence.
Cite as Automation Atlas, Open-source automation licences, licence files read 16 Nov 2026.
Twelve carry OSI licences, one is split and four are not: Windmill mixes AGPLv3 with proprietary terms, and four sit outside OSI's list OSI list. Six set conditions on hosting or resale, and Automatisch is in both groups Automatisch AGPL.
Which of these projects are ending?
Two are: Flowise's repository is archived, and Pipedream Workflows closes on 31 Mar 2027, so check both before you pick either one Flowise repoPipedream docs.
| Product | Last day | Warning given | What to do next |
|---|---|---|---|
| Flowise | 31 Aug 2026 end of life; repo archived 13 Aug 2026 Flowise repoFlowise notice | 33 days, announced 29 Jul 2026 Flowise notice | The announcement tells users to fork the code. Apache 2.0 allows that for the open code, but not the enterprise folder. Flowise noticeAirflow licenceFlowise licenceFlowise EE licence |
| Pipedream Workflows | 31 Mar 2027 Pipedream docs | Six months, per the notice Pipedream docs | Export workflows as JSON before data is deleted on 30 Apr 2027. The repo licence excludes commercial use, so check it before you fork. Pipedream docsPipedream licence |
The shutdown tracker carries the same dates for both, as well as the warnings and next steps.
Can you use it inside your own company?
Internal use is allowed under 16 of the 17, and Pipedream is the exception, a vague one, since its public repo excludes any commercial use Pipedream licence and the file doesn't say whether internal use counts.
Windmill says internal use of its Community Edition needs no commercial licence, a line added on 25 Oct 2026 Windmill licenceWindmill, 25 Oct 2026. As for n8n, it limits use to your own internal business purposes n8n licence, and its FAQ counts use inside your own product as internal n8n FAQ.
Enterprise folders need a paid licence for production use at n8n, Activepieces, Automatisch and Flowise n8n EE licenceActivepieces ee licenceAutomatisch EE licenceFlowise EE licence, whilst Windmill's enterprise-flagged code is proprietary Windmill licence.
Can a consultancy host it for clients?
For n8n, the deciding question is client access, whatever the client count or revenue.
The FAQ allows unlimited clients on your own instance, as long as they can't create or edit workflows n8n FAQ.
In words
- You start by running n8n for clients under the Sustainable Use License.
- Can clients build or edit workflows, through a custom UI, the API, MCP or an AI agent? If yes, it is not allowed n8n FAQ.
- If no, n8n's FAQ allows it with no limit on client count, so access is what decides it n8n FAQ.
- White-labelling n8n or forking it into your own automation product is not allowed n8n FAQ.
- On your own instance you may charge for setup and maintenance, which is the green route in the drawing n8n FAQ.
- On the client's own server it's allowed too, provided you don't also host it for them n8n FAQ.
- Inside your product, it is allowed as a backend engine, if end users never reach its UI or configure workflows n8n FAQ.
Drawn from n8n's licence FAQ, read 16 Nov 2026. The green route is the agency case the FAQ answers in your favour.
Yes for most, and six projects set conditions or say no. MIT and Apache 2.0 grant the right to distribute, sublicense and sell Huginn licenceAirflow licence. That covers Activepieces, Node-RED, Huginn, Kestra, Airflow, Temporal, Prefect, Dagster, Trigger.dev, Langflow and Flowise for their open code.
| Project | Host for clients | Embed or white-label | Sell as a hosted service |
|---|---|---|---|
| n8n | Yes if clients cannot build or edit workflows; no if they can n8n FAQ | Hidden backend in your product: yes. White-label or fork into a product: no n8n FAQ | No, others only free and non-commercial n8n licence |
| Windmill | Community Edition: needs an agreement Windmill licence | Commercial licence needed, except iframed public apps Windmill licence | Community Edition: needs an agreement Windmill licence |
| Automatisch | Conditions: modified versions must offer source to network users Automatisch AGPL | Same AGPL source duty Automatisch AGPL | Same AGPL source duty Automatisch AGPL |
| Inngest | Conditions: publish the Service Source Code Inngest licence | Same SSPL service clause Inngest licence | Publish the Service Source Code; Apache 2.0 after three years Inngest licence |
| Pipedream | No, all commercial use is excluded Pipedream licence | No, all commercial use is excluded Pipedream licence | No, competing online services are excluded Pipedream licence |
| Dify | No multi-tenant use without written authorisation Dify licence | Backend service allowed; logo and copyright stay in the frontend Dify licence | Multi-tenant needs written authorisation; commercial licence if conditions are met Dify licence |
n8n's licence FAQ answers the agency question in your favour, since consulting and automation services are explicitly permitted, with no limit on client count n8n FAQ. That being said, clients may not build or edit workflows on your instance n8n FAQ. Installing on a client's own server is allowed too, provided you don't also host it n8n FAQ.
A Windmill build from source without the enterprise flag follows AGPLv3 Windmill licence, so re-exposing it to users means complying with AGPLv3 or buying a commercial licence Windmill licence.
Can you embed or white-label it?
Five of 17 projects keep enterprise code in the same repository, under another licence.
Activepieces is the plainest case, with MIT code outside its ee folders and an Enterprise licence needed inside them Activepieces licenceActivepieces ee licence.
This figure in words
- Activepieces is MIT-licensed outside its enterprise folders, which lets you use, sell and sublicense it Activepieces licenceHuginn licence.
- Code in packages/ee and the server ee folder is under an Enterprise licence Activepieces licence that production use needs, priced by seats Activepieces ee licence.
- n8n n8n licencen8n EE licence, Automatisch Automatisch licenceAutomatisch EE licence, Flowise Flowise licenceFlowise EE licence and Windmill Windmill licence split the same way.
- So five of the 17 projects keep enterprise code in the same repository under another licence.
- In the drawing the repository is a frame with a tinted floor, and the enterprise folders are a hatched frame set into its back corner.
- The green line is the one doorway into them. The four small copies beside it are n8n, Automatisch, Flowise and Windmill, each with the same hatched frame inside.
Drawn from the licence files of each repository, read 16 Nov 2026. Depth shows only that one boundary sits inside another; the count is printed.
Only the permissive projects give a clean yes, and even there trademarks are not licensed, as Apache 2.0 says in plain terms Airflow licence.
n8n is the case to read twice. You may run it as a hidden backend for your product n8n FAQ, but you may not let your users build workflows through it, and you may not white-label it n8n FAQ. The FAQ calls shipping n8n to customers inside a paid product grey territory, so confirm it with n8n first n8n FAQ.
Dify is the odd one, since it allows commercial use as a backend service Dify licence, but the logo rule means a white-labelled frontend isn't allowed Dify licence.
Can you sell it as a hosted service?
This is where the licences split hardest, because permissive projects allow it freely. Which is awkward, since the restricted ones are the ones you'd most want to resell.
SSPL is the heaviest condition, because it reaches the code you use to run the service as well as the program itself Inngest licence. Inngest's Apache 2.0 future licence applies to each release three years after it ships Inngest licence.
n8n and Windmill say no without an agreement n8n licenceWindmill licence, Pipedream bars online services that compete with its products Pipedream licence, and Dify wants written authorisation for multi-tenant use Dify licence.
What do fair-code and source-available mean?
Both terms mean you can read and run the code, but the licence limits what you can sell. The Sustainable Use License, SSPL and Pipedream's licence are source-available, and none is on OSI's approved list OSI list.
Dify's licence adds conditions to Apache 2.0, so it isn't on that list either OSI list.
AGPL sits on the open side of the line, since it's on OSI's list OSI list and it's copyleft, so network users of a modified version get the source Automatisch AGPL, though it doesn't ban hosting.
Which licences changed in 2025 or 2026?
Three licence edits since 2025 changed what you may do.
Two were Windmill's and one was Flowise's, whilst the other five projects only edited notices.
In words
- Windmill: 7 Mar 2025, proprietary enterprise wording and Community Edition terms Windmill, 7 Mar 2025; 25 Oct 2026, paragraphs on re-exposing Windmill and on internal use Windmill, 25 Oct 2026. This changes what you may do.
- Flowise: 27 May 2025, commercial licence added for the enterprise directory Flowise commit. This changes what you may do.
- Dify: 26 Feb and 28 Mar 2025, wording, then business contact details removed Dify commit. Notices only, no change to what you may do.
- Kestra: 13 Sep 2026, copyright holder name Kestra commit. Notices only, no change to what you may do.
- Apache Airflow: 13 Sep 2026, notices for bundled font subcomponents Airflow commit. Notices only, no change to what you may do.
- Dagster: 12 May 2025, typo and copyright year Dagster commit. Notices only, no change to what you may do.
- Temporal: 2 May 2025, per-file headers removed, MIT terms unchanged Temporal commit. Notices only, no change to what you may do.
- The other ten licence files last changed in 2024 or earlier n8n licenceActivepieces licenceNode-RED licenceHuginn licenceAutomatisch historyPrefect licenceTrigger.dev licenceInngest licencePipedream licenceLangflow licence.
Licence file changes in 2025 and 2026, from each repository's commit history, checked 16 Nov 2026. Filled dot: changes what you may do. Ring: notices only.
Two projects changed what you may do, and five only edited notices. Windmill changed its terms twice, most recently on 25 Oct 2026 Windmill, 25 Oct 2026. The other ten files last changed in 2024 or earlier.
Limits of this page
This is a reading of licence texts, not legal advice. Licence files change, and a commercial agreement can override them, so ask a lawyer first, particularly before you host for clients or resell.
Kestra's Enterprise Edition terms, Dify's commercial licence and Windmill's commercial licence are not published in the files read, so this page doesn't cover them.
Questions
Is n8n open source?
Not by OSI's list. Its Sustainable Use License is not on it OSI list. It limits use to your own internal business purposes, or non-commercial or personal use n8n licence.
Can an agency host n8n for its clients?
Yes, on your own instance, if clients cannot create or edit workflows. You may charge for setup and maintenance n8n FAQ. Letting clients build through a custom UI, the API, MCP or an AI agent is not allowed n8n FAQ.
Is Activepieces fully MIT?
No. Code outside its enterprise directories is MIT Activepieces licence. packages/ee and the server ee folder need an Enterprise licence for production, priced by user seats Activepieces licenceActivepieces ee licence.
Can I sell Windmill as a managed service?
Not the Community Edition, without an explicit agreement Windmill licence. A build from source without the enterprise flag is AGPLv3, so re-exposing it means AGPLv3 duties or a commercial licence Windmill licence.
Which projects can I resell as a hosted service?
The MIT and Apache 2.0 projects, for their open code. Both licences grant the right to distribute and sublicense Huginn licenceAirflow licence. Neither licenses the project's trademarks Airflow licence.
Sources
Licence files in each repository
- n8n, LICENSE.md, Sustainable Use License 1.0Dated 24 Dec 2024, the file's last change. Read 16 Nov 2026.
- n8n, LICENSE_EE.md, n8n Enterprise LicenseDated 29 Aug 2022, the file's last change. Read 16 Nov 2026.
- Activepieces, LICENSEDated 15 Feb 2024, the file's last change. Read 16 Nov 2026.
- Activepieces, packages/ee/LICENSEPage undated. Read 16 Nov 2026.
- Node-RED, LICENSE, Apache 2.0Dated 29 Sep 2020, the file's last change. Read 16 Nov 2026.
- Windmill, LICENSEPage undated. Read 16 Nov 2026.
- Huginn, LICENSE, MITDated 17 Mar 2013, the file's last change. Read 16 Nov 2026.
- Automatisch, LICENSEPage undated. Read 16 Nov 2026.
- Automatisch, LICENSE.agplPage undated. Read 16 Nov 2026.
- Automatisch, LICENSE.enterprisePage undated. Read 16 Nov 2026.
- Kestra, README.mdPage undated. Read 16 Nov 2026.
- Apache Airflow, LICENSE, Apache 2.0Page undated. Read 16 Nov 2026.
- Temporal, LICENSE, MITPage undated. Read 16 Nov 2026.
- Prefect, LICENSE, Apache 2.0Dated 8 Mar 2022, the file's last change. Read 16 Nov 2026.
- Trigger.dev, LICENSE, Apache 2.0Dated 21 Aug 2023, the file's last change. Read 16 Nov 2026.
- Inngest, LICENSE.md, SSPL 1.0Dated 23 Sep 2024, the file's last change. Read 16 Nov 2026.
- Pipedream, LICENSE, Pipedream Source Available License 1.0Dated 3 Jan 2023, the file's last change. Read 16 Nov 2026.
- Langflow, LICENSE, MITDated 18 Apr 2024, the file's last change. Read 16 Nov 2026.
- Flowise, LICENSE.mdDated 27 May 2025, the file's last change. Read 16 Nov 2026.
- Flowise, packages/server/src/enterprise/LICENSE.mdPage undated. Read 16 Nov 2026.
- Dify, LICENSE, modified Apache 2.0Dated 28 Mar 2025, the file's last change. Read 16 Nov 2026.
Licence history, from commits
- Windmill on GitHub, LICENSE commit 3ba2016Dated 7 Mar 2025. Read 16 Nov 2026.
- Kestra on GitHub, LICENSE commit a075c41Dated 13 Sep 2026. Read 16 Nov 2026.
- Temporal on GitHub, LICENSE commit 91893f1Dated 2 May 2025. Read 16 Nov 2026.
- Dagster on GitHub, LICENSE commit eafa8fbDated 12 May 2025. Read 16 Nov 2026.
- Dify on GitHub, LICENSE commit d565802Dated 28 Mar 2025. Read 16 Nov 2026.
- Windmill on GitHub, LICENSE commit 83ea0efDated 25 Oct 2026. Read 16 Nov 2026.
- Flowise on GitHub, LICENSE.md commit 5a37227Dated 27 May 2025. Read 16 Nov 2026.
- Apache Airflow on GitHub, LICENSE commit 5b28f1fDated 13 Sep 2026. Read 16 Nov 2026.
- Automatisch on GitHub, LICENSE commit historyDated 12 Feb 2023. Read 16 Nov 2026.
Licence FAQ, notices and the OSI list
- n8n docs, Community license FAQPage undated. Read 16 Nov 2026.
- Open Source Initiative, OSI-approved licencesDated 16 Nov 2026. Read 16 Nov 2026.
- Flowise on GitHub, Flowise repository, archivedDated 13 Aug 2026. Read 16 Nov 2026.
- Flowise on GitHub, Discussion 6727, winding down FlowiseDated 29 Jul 2026. Read 16 Nov 2026.
- Pipedream, Workflows docs, shutdown noticePage undated. Read 16 Nov 2026.
Each chip in the text opens its source here. Licence files were read on 10 Nov 2026 and re-checked on 16 Nov 2026.