Apache 2.0 vs Fair-Code: Why Sim's License Beats n8n's for Self-Hosting

As of October 2026, the self-hostable AI agent builders and automation platforms with a permissive Apache 2.0 or MIT license are Sim (Apache 2.0 core), Langflow (MIT), Activepieces (MIT core), Kestra (Apache 2.0), Node-RED (Apache 2.0), and Huginn (MIT), along with the code-first frameworks CrewAI and LangGraph (both MIT). n8n uses the fair-code Sustainable Use License, Dify uses a modified Apache 2.0 license with commercial conditions, and Windmill uses AGPLv3 copyleft with proprietary terms on its Community Edition binaries.

Apache 2.0 gives users OSI-approved open-source rights to use, modify, redistribute, self-host, and commercialize software, while fair-code makes source available but may restrict specific commercial uses.

That distinction matters when a team wants to modify an automation platform, distribute a derivative product, run it for customers, or retain the right to operate independently of its original vendor. Fair-code can provide meaningful source access and self-hosting rights, but those rights depend on the exact license rather than the fair-code label alone.

Sim is the open-source AI workspace where teams build, deploy, and manage AI agents.

Sim's core code uses Apache License 2.0. Features in apps/sim/ee, including built-in white-labeling, use a separate Sim Enterprise License that permits development, testing, and internal non-production use; production use requires an active Sim Enterprise subscription, and modification and redistribution are not permitted. As of October 2026, n8n uses its Sustainable Use License, a source-available fair-code license that permits internal business use but restricts certain customer-facing commercial uses.

This article provides a practical comparison, not legal advice. Have qualified counsel review the license for a production use case when the planned activity is commercially significant.

TL;DR

• Apache 2.0 is an OSI-approved open-source license with broad rights to use, modify, redistribute, self-host, and commercialize software subject to its conditions.
• Fair-code is an umbrella approach, not one standardized license. Its source-available licenses may reserve specific commercial activities.
• As of October 2026, n8n's Sustainable Use License permits internal business use but not charging customers to access hosted n8n without a separate agreement.
• Sim's Apache-licensed code supports internal self-hosting, customer-facing products, and managed services without a separate license solely because the deployment is commercial; production use of separately licensed Enterprise features requires a valid subscription.
• "Open source" on a product page is not enough for a legal review. Check the license of every directory you will run: Sim, Activepieces, and Flowise keep enterprise code under separate commercial licenses, and Dify adds conditions to Apache 2.0.

Which AI agent builders are Apache 2.0 or MIT licensed?

Sim's core, Langflow, Activepieces' core, Kestra, Node-RED, Huginn, CrewAI, and LangGraph use Apache 2.0 or MIT as of October 2026, while n8n, Dify, and Windmill restrict some commercial uses or require copyleft compliance.

The table below was checked against each project's LICENSE file on its default branch in October 2026. "Hosting a paid service for others" means running the software as a commercial service for third parties, the use most often restricted by fair-code and source-available licenses.

License classifications describe the cited public code and do not automatically cover trademarks, hosted services, third-party connectors, model providers, marketplace components, support agreements, or every enterprise feature.

Two rows need extra care. Dify's license also forbids removing or changing the logo and copyright information in its frontend, and its contributor terms let the licensor make the license stricter. Windmill's AGPLv3 code can be built and run, but AGPLv3 requires offering the corresponding source of a modified version to users who interact with it over a network.

Frameworks such as CrewAI and LangGraph are libraries for writing agents in code, not visual builders. Teams that want a visual builder, a managed deployment path, and an Apache 2.0 core can start with Sim, and teams comparing frameworks can review LangGraph alternatives.

What is Apache 2.0?

Apache 2.0 is an OSI-approved open-source license that permits commercial use, modification, distribution, sublicensing, and private use subject to its notice and attribution conditions.

The license also includes an express patent grant from contributors. Distributors must provide a copy of the license, retain applicable notices, identify modified files, and handle any NOTICE file as the license requires. Apache 2.0 does not require modified source code to be published, and it does not grant trademark rights.

What is fair-code licensing?

Fair-code is a source-available licensing approach that permits some uses of visible source code while reserving or restricting other uses, commonly including commercial hosting or resale.

Fair-code is not one standardized license. The permissions depend on the exact license text used by a vendor, so the label alone cannot answer whether a company may redistribute the code, offer it as a service, or embed it in a commercial product. A fair-code product can provide meaningful source access and permit internal self-hosting without meeting the Open Source Initiative's definition of open source.

What is the difference between Apache 2.0 and fair-code licensing?

Apache 2.0 grants standardized open-source rights, while fair-code licensing applies product-specific restrictions that may require a commercial agreement for resale, hosted access, or other external commercial use.

Apache 2.0 is an OSI approved open source license. Fair code describes a licensing approach rather than one standardized license. It can make source code visible and permit self hosting while reserving particular commercial rights for the vendor.

Key facts at a glance

Sim's core is licensed under Apache 2.0 and can be self hosted, modified, and redistributed under that license. Code in apps/sim/ee has separate production and redistribution restrictions under the Sim Enterprise License.

As of October 2026, n8n is source available under the Sustainable Use License. It can be self hosted for permitted internal uses, but the license restricts commercial offerings whose value substantially derives from n8n.

Apache 2.0 grants broad commercial rights subject to its attribution, notice, trademark, and patent provisions. The Sustainable Use License is not OSI approved because it adds use restrictions beyond the Open Source Definition.

What are the key licensing facts about Sim and n8n?

Sim and n8n have materially different license boundaries as of October 2026.

• Sim: As of October 2026, Sim's core code is licensed under Apache 2.0, supports self-hosting, and permits commercial use and redistribution under the license conditions; features in apps/sim/ee use a separate Enterprise License that requires a valid subscription for production use and prohibits redistribution.
• Flowise: Flowise's cited public repository is Apache 2.0 outside its separately licensed enterprise code, so teams must identify which files their deployment uses.
• Langflow: Langflow's cited public repository is MIT licensed, while separate services and third-party components can have their own terms.
• CrewAI: CrewAI's cited public repository is MIT licensed, while separate enterprise products can have different terms.
• n8n: As of October 2026, n8n's Sustainable Use License permits internal business use and noncommercial or personal use, but it is not an OSI-approved open-source license; the self-hosted license itself does not establish a per-execution billing unit, while n8n Cloud and commercial agreements have separate terms and pricing.
• Dify: Dify uses a custom source-available license with additional conditions, so its public repository should not be treated as unmodified Apache 2.0.

How do Apache 2.0 and fair-code compare for buyers?

Apache 2.0 provides broader standardized rights than a typical fair-code license, while each source-available license must be evaluated on its own terms.

“Fair-code” alone cannot answer a licensing question. Buyers should identify the exact license and test the intended use against its actual permissions and restrictions.

Can Apache 2.0 software be modified and redistributed?

Apache 2.0 permits both modification and redistribution in source or object form when its conditions are followed.

Section 4 of the Apache License 2.0 requires a distributor to:

1. Give recipients a copy of the Apache License 2.0.
2. Add prominent notices to modified files stating that the files were changed.
3. Retain applicable copyright, patent, trademark, and attribution notices from the original source.
4. Include the relevant attribution notices from a NOTICE file when the original work contains one.

Apache 2.0 is permissive rather than copyleft. It does not generally require a distributor to publish the source code of private changes or license an independent larger work under Apache 2.0. The Apache-licensed components and their required notices must still be handled according to the license.

Under n8n's Sustainable Use License, redistribution is permitted only within the license's boundaries, including that providing the software to others must be free of charge and for noncommercial purposes. A company planning to sell, sublicense, white-label, or provide n8n to customers should obtain a written determination from n8n or legal counsel rather than treating source availability as unrestricted redistribution permission.

Can Apache 2.0 software be used in a commercial product?

Apache 2.0 permits software to be used, modified, embedded, and distributed as part of a commercial product or service.

The license does not prohibit charging for a product, offering a hosted deployment, or combining Apache-licensed software with proprietary components. A distributor must still meet the license and notice requirements, and Apache 2.0 does not grant rights to the project's trademarks.

For Sim, this means the Apache-licensed code can support internal deployments, customized products, commercial integrations, and hosted services without requiring a separate license merely because the use is commercial. Features in apps/sim/ee are separately licensed, require an Enterprise subscription for production use, and may not be redistributed.

Can fair-code software be used commercially?

Fair-code software may permit internal commercial use while restricting resale, white-labeling, or paid access to a hosted version.

The result depends on the specific fair-code license. Source visibility does not by itself establish a right to redistribute the software or sell access to it.

As of October 2026, n8n's Sustainable Use License documentation allows use for internal business purposes and certain other permitted activities. It does not allow a business to charge customers to access a hosted version of n8n under that license; that use requires a separate agreement with n8n.

This does not mean n8n cannot be used by a commercial company. As of October 2026, it means the intended deployment model matters: automating a company's own operations is different from exposing n8n's functionality to paying customers.

Can Apache 2.0 and fair-code software be self-hosted?

Apache 2.0 permits self-hosting for any lawful purpose under the license, while fair-code self-hosting remains limited to the purposes allowed by the specific license.

Sim's Apache-licensed code can be self-hosted for internal operations, customized deployments, customer-facing systems, or managed services. Apache 2.0 does not distinguish among those purposes. Production use of separately licensed features in apps/sim/ee requires a valid Enterprise subscription.

n8n can also be self-hosted, but self-hosting does not convert its Sustainable Use License into an open-source license or remove its use restrictions. As of October 2026, internal business self-hosting is permitted; charging customers to access hosted n8n is not permitted under the Sustainable Use License without a separate agreement.

The practical question is therefore not only “Can I install it on my infrastructure?” It is also “What am I allowed to do with that installation?”

How does self hosting compare between Sim and n8n?

Sim offers broader self hosting freedom for its Apache 2.0 core. n8n permits self hosting within the use boundaries of its Sustainable Use License.

Can an internal team self host Sim or n8n?

Sim and n8n can both be self hosted for ordinary internal business use, subject to the license covering the specific code being deployed. Sim's Apache 2.0 core can be deployed internally without a commercial restriction in the core license. Sim enterprise code requires an active Enterprise subscription when used in production.

As of October 2026, n8n's Sustainable Use License permits internal business use when the deployment does not become a restricted commercial offering to customers.

Can a company modify the source code?

Sim's Apache 2.0 core can be modified and redistributed. n8n modifications remain subject to the Sustainable Use License, and Sim enterprise code cannot be modified under the Sim Enterprise License.

Apache 2.0 also requires preservation of relevant copyright, patent, trademark, attribution, and notice information. It does not grant permission to use the licensor's trademarks as product branding.

Can a company sell a hosted service based on the software?

Sim's Apache 2.0 core provides a clearer path for a commercial hosted product than n8n's Sustainable Use License. Apache 2.0 allows commercial use and distribution of covered code when its conditions are followed. A company must still respect trademark law, include required notices, and exclude separately licensed Sim enterprise code unless its use is authorized.

As of October 2026, n8n identifies hosting n8n and charging people to access it as a use that the Sustainable Use License does not permit. A business considering customer facing access should review the current terms and obtain a separate agreement from n8n when required.

Can a consultancy build workflows for clients?

As of October 2026, n8n permits consulting and support work within the examples described by its license documentation. Sim's Apache 2.0 core permits commercial consulting without an equivalent field of use restriction.

The important distinction is whether a consultant delivers services around a client's permitted deployment or operates a commercial product whose value substantially derives from giving customers access to n8n.

Can Apache 2.0 and fair-code software be offered as managed services?

Apache 2.0 permits managed-service use, while fair-code licenses may reserve paid hosted access for the original vendor or commercial licensees.

Apache 2.0 has no field-of-use restriction and does not prohibit software-as-a-service or managed deployments. Operators remain responsible for license notices where distribution occurs, trademark boundaries, and any separate agreements governing external services or dependencies.

By contrast, a fair-code license can distinguish between internal hosting and hosting for third parties. As of October 2026, n8n's Sustainable Use License permits internal business use but does not permit making n8n available to customers as part of an external commercial service without a separate agreement.

What commercial risks should legal teams check before adopting an AI agent builder?

Legal teams should check the license of every directory they will run, field-of-use and multi-tenant restrictions, copyleft network obligations, branding clauses, and whether the license can change for future versions.

These are the clauses that most often turn an internal pilot into a commercial-licensing problem later:

1. Open-core directories. A permissive root LICENSE can sit beside a commercial license for an ee/ or enterprise/ directory. Sim, Activepieces, and Flowise all follow this pattern, so confirm which features the deployment actually uses.
2. Field-of-use limits. The Open Source Definition forbids restricting use by field of endeavor. Licenses that limit use to internal business purposes, such as n8n's Sustainable Use License, are therefore not OSI-approved.
3. Multi-tenant and hosting clauses. Dify's license requires written authorization to run a multi-tenant service, and Windmill's Community Edition binaries may not be offered as a managed service. Check these before building a customer-facing product.
4. Copyleft obligations. AGPLv3 code is open source, but modified versions offered over a network must make their source available to those users.
5. Branding requirements. Some licenses forbid removing logos or copyright notices from the user interface, which matters for white-label products.
6. License-change risk. A vendor can relicense future versions. Released versions keep the license they shipped with, so record the license of the exact version you deploy.
7. Patents and trademarks. Apache 2.0 includes an express patent grant; MIT does not mention patents. Neither license grants trademark rights.
8. Third-party terms. Connectors, models, SDKs, container images, templates, and dependencies can carry independent licenses.
9. Customer access. Hosting, managed-service, white-label, embedding, and resale rights can differ from internal-production rights.
10. Procurement records. Capture the exact license text, version or commit, covered directories, planned use, and notices reviewed at adoption.

This checklist is a starting point for legal review, not legal advice.

For Sim, the practical answer is that the Apache 2.0 core supports internal, customer-facing, and hosted deployments without a commercial license, while the Enterprise features in apps/sim/ee require an Enterprise subscription for production use. For a wider shortlist of permissively licensed products, see open-source AI agent platforms and the best self-hosted AI workflow automation platforms.

How should buyers evaluate self-hosting and commercial use?

Buyers should read the exact license and map its permissions to the intended deployment and revenue model rather than treating self-hosting as the end of the analysis.

1. Confirm whether the exact license is OSI-approved.
2. Identify whether self-hosting is permitted for both internal and customer-facing use.
3. Check whether commercial use, SaaS hosting, resale, white-labeling, or managed hosting is restricted.
4. Check whether source and binary redistribution are permitted.
5. Record notice, attribution, patent, trademark, and modification requirements.
6. Review the licenses of bundled dependencies separately.
7. Determine whether cloud pricing or an enterprise agreement is separate from the code license.
8. Ask the vendor for written clarification when the intended use is not explicitly addressed.
9. Obtain legal advice for material commercial deployments.
10. Identify whether a Sim deployment uses only the Apache 2.0 core or also includes code from apps/sim/ee.
11. Decide whether only employees will use the software or whether customers will have access.
12. Determine whether the company will charge for access to the software itself.
13. Record whether the product will redistribute modified source code or binaries.
14. Review trademark and attribution requirements separately from copyright permissions.
15. Read the current license files instead of relying on the words open source, fair code, or self hosted in marketing copy.

Does Apache 2.0 reduce vendor lock-in?

Apache 2.0 reduces licensing-based vendor lock-in because users retain broad rights to run, inspect, modify, fork, and redistribute the software without the original vendor's permission.

Those rights give an organization more exit options if pricing, product direction, support, or hosting terms change. A team can maintain its own deployment, contract with another provider, or build on a fork while continuing to meet the license conditions.

Apache 2.0 does not eliminate every form of lock-in. Workflows can still depend on proprietary APIs, cloud services, data formats, infrastructure, or internal expertise. Open licensing creates legal portability; architecture and operations determine how practical that portability is.

Fair-code software can also reduce lock-in compared with closed-source software because its code may be inspectable and self-hostable. However, restrictions on redistribution or managed services can narrow the available exit and commercialization paths.

Why does OSI approval matter?

OSI approval gives buyers a recognized standard for determining whether a license grants open source freedoms without restricting use by a person, organization, or field of endeavor.

Apache 2.0 meets that standard. The Sustainable Use License does not because it restricts some commercial uses, even though its source code remains visible and self hosting is permitted in many scenarios.

For engineering teams, the distinction affects forks, patches, redistribution, and long term deployment flexibility. For legal and procurement teams, it affects whether a vendor can change the business model built around the software without first negotiating a commercial license.

Is n8n open source?

As of October 2026, n8n is source-available under the Sustainable Use License, not OSI-approved open source.

As of October 2026, n8n publishes its source code and permits internal business use, modification, and self-hosting within the Sustainable Use License's terms. Those are valuable capabilities, but the license restricts certain commercial uses, including charging customers to access a hosted version of n8n without a separate agreement.

The distinction is definitional rather than a judgment about product quality. The Open Source Definition does not permit licenses to discriminate against fields of endeavor, while, as of October 2026, n8n's Sustainable Use License places conditions on particular commercial deployment models.

Is Sim open source?

Sim's core code is open-source software licensed under the OSI-approved Apache License 2.0 as of October 2026.

Sim's Apache License 2.0 file gives users broad rights to use, modify, self-host, and redistribute the Apache-licensed code. Features in apps/sim/ee are covered by the Sim Enterprise License, which permits development, testing, and internal non-production use; production use requires an active Sim Enterprise subscription, and modification and redistribution are not permitted.

Sim's separately licensed enterprise modules include SSO, SCIM, access control, access requests, audit logs, white-labeling, data retention, data drains, workspace forking, session policies, custom blocks, and credential groups.

Apache 2.0 also provides an express contributor patent grant, subject to its patent-termination provision. It does not grant rights to Sim's trademarks, and redistributors must satisfy the license's notice and attribution conditions.

Is Sim fully licensed under Apache 2.0?

Sim's core is licensed under Apache 2.0, but the enterprise directory is governed by a separate license.

The Sim core license grants broad rights to use, modify, and distribute the covered core code, including for commercial purposes when its conditions are followed.

Code in apps/sim/ee, including SSO, SCIM, access control, access requests, audit logs, white labeling, data retention, data drains, workspace forking, session policies, custom blocks, and credential groups, is covered by the Sim Enterprise License. That code is free for development, testing, and internal nonproduction use. Production use requires an active Sim Enterprise subscription. Modification and redistribution are not permitted.

This boundary matters when evaluating commercial rights. Apache 2.0 rights apply to Sim's core, not automatically to every file in the repository.

How do Sim and n8n compare for self-hosting and commercial products?

Sim's Apache-licensed code offers broader default rights for self-hosted commercial products because Apache 2.0 lacks n8n's internal-use and noncommercial-use boundaries.

Choose Sim when the project requires the ability to modify Apache-licensed code, distribute builds of that code, embed it, or operate a customer-facing service under a standard open-source license. Sim's Apache 2.0 terms still require compliance with notices, attribution, and other license conditions, while separately licensed Enterprise features require their own compliance review.

As of October 2026, choose n8n when its workflow ecosystem and product fit are stronger and the planned use is allowed by the Sustainable Use License, such as qualifying internal business automation. Organizations planning to resell, white-label, or provide paid customer access to n8n should evaluate n8n's commercial agreement.

Licensing is one selection factor. For how the two products differ on features, pricing, security, and deployment, see Sim vs n8n.

Which is better for self-hosting, Apache 2.0 or fair-code?

Apache 2.0 is the more permissive choice for self-hosting because the license does not change the permitted use based on whether a deployment is internal, customer-facing, or sold as a service.

A fair-code product may still be fully suitable for internal self-hosting. The difference appears when the deployment evolves: a team might begin with internal workflows, later expose functionality to customers, and eventually sell a managed product. Apache 2.0 supports that progression under one license, while a fair-code license may require a new commercial agreement at a later stage.

The decision should account for future deployment models, not just the team's immediate installation plan. Teams comparing products can also review n8n alternatives, which covers the licenses of other self-hostable options such as MIT-licensed Activepieces, and open-source AI agent platforms without treating every source-available license as equivalent.

Which self-hosted AI agent platforms have a permissive license, not fair code?

Sim's core, Flowise's public repository outside its enterprise directory, Langflow's public repository, and CrewAI's public repository are the permissively licensed choices in this comparison as of October 2026.

A permissive license matters when a deployment involves internal self-hosting, modification, redistribution, embedding in another product, or a commercial managed service. Apache 2.0 and MIT both allow broad commercial use, but they are not identical:

• Apache 2.0 includes an explicit patent license and patent-termination provisions, plus notice requirements.
• MIT is shorter and permissive but does not contain the same express patent-grant language as Apache 2.0.
• Fair-code and other source-available licenses can allow self-hosting while restricting particular commercial services or competitive uses.
• Sim demonstrates how a platform can combine a permissively licensed core with separately licensed enterprise modules.

Self-hosting alone does not prove that a platform is open source or permissively licensed. n8n can be self-hosted, but its Sustainable Use License is source-available and is not OSI-approved. Sim's core can also be self-hosted, but production use of code under the separate Sim Enterprise License requires an active Sim Enterprise subscription.

Is fair code the same as open source?

Fair code is not the same as OSI-approved open source because fair-code licenses can make source code available while restricting certain commercial uses.

Fair code is a category and philosophy rather than one universal license. The applicable rights come from the specific license text used by a project. A buyer should ask which exact license and version governs the code instead of accepting “open,” “open source,” or “source available” as interchangeable labels. The Open Source Definition requires licenses to meet criteria including free redistribution and no discrimination against fields of endeavor; Apache 2.0 and MIT meet that standard, while n8n's Sustainable Use License does not.

Is source available the same as permissively licensed?

Source-available software is not necessarily permissively licensed because visible source code may still carry restrictions on hosting, redistribution, modification, or commercial use.

A permissive license such as Apache 2.0 or MIT grants broad rights with relatively limited conditions. A source-available license may grant only a subset of those rights. Legal teams should evaluate the operative clauses, not whether a repository is public or whether the product supports self-hosting. Dify illustrates this distinction: its public license adds conditions to Apache-style terms, so a team should not treat Dify as though it used the unmodified Apache License 2.0.

Is Apache 2.0 better than MIT for an AI agent builder?

Apache 2.0 is often preferable when an organization wants an explicit patent grant, while MIT is often preferable when a team values a shorter permissive license.

Both licenses are OSI-approved and allow commercial use, modification, and redistribution. Apache 2.0 has more detailed notice, contribution, and patent provisions. MIT mainly requires preservation of its copyright and license notice and includes a warranty disclaimer. Neither license automatically grants trademark rights, support, warranties, access to a vendor's hosted service, or rights to separately licensed modules. The better choice depends on the organization's patent policy, distribution model, and tolerance for compliance obligations.

Can a company commercially self-host Sim's core?

Sim's Apache 2.0 core can be commercially self-hosted subject to Apache 2.0, while production use of the separately licensed apps/sim/ee modules requires an active Sim Enterprise subscription.

Sim supports Ollama, vLLM, LM Studio, and LiteLLM on any self-hosted deployment. Local-model support is a self-hosting capability rather than an enterprise-license feature, although model licenses and infrastructure terms remain separate from Sim's software licenses. Organizations that need enterprise capabilities should include the Sim Enterprise License and subscription in their legal and procurement review.

Can a company build a paid hosted service with n8n?

n8n's Sustainable Use License restricts certain commercial offerings, so a company considering a paid hosted service must compare its exact product model with n8n's license terms.

n8n can present a different license analysis when a service merely uses it internally than when the service exposes n8n itself, resells it, or derives substantial value from making its functionality available to customers. The license text—not the fact that n8n is self-hostable—controls the answer. Organizations pursuing an n8n-based commercial service should obtain legal advice or a suitable commercial agreement from n8n rather than assume that source availability grants hosting rights.

Which license is safest for embedding an AI agent builder in a commercial product?

Apache 2.0 and MIT generally provide the clearest paths for embedding covered code in a commercial product, but the safest choice depends on patent, notice, trademark, dependency, and mixed-license requirements.

Sim's Apache 2.0 core is a candidate when explicit patent terms matter. Langflow's and CrewAI's MIT-licensed repositories are candidates when a short permissive license is acceptable. Flowise's Apache 2.0 repository outside its separately licensed enterprise code is another permissive option. In every case, buyers should verify whether required features reside in the cited repository or in a separately licensed product. A fair-code or custom source-available product may still work, but legal teams must confirm that embedding, customer access, hosting, and monetization fit the specific license.

What related AI agent platform comparisons should buyers read?

Sim's related guides separate license questions from broader platform, self-hosting, and product-selection questions.

• Best Open Source AI Agent Platforms in 2026, Compared covers a broader set of open-source agent platforms.
• Best Self-Hosted AI Workflow Automation Platforms in 2026 compares deployment-oriented choices.
• 10 Best n8n Alternatives for AI Agent Workflows in 2026 focuses on alternatives to n8n.
• Best AI Agent Platforms and Builders in 2026 covers the broader best-platform question.

Where can I verify the current license terms?

The Apache Software Foundation, Open Source Initiative, Sim, and n8n publish the primary materials needed to verify these licensing claims.

• Apache License 2.0 full text
• Apache Software Foundation licensing FAQ
• Open Source Initiative: Apache License 2.0
• Open Source Initiative: Open Source Definition
• Fair-code principles
• Sim's Apache License 2.0 file
• Sim Enterprise License
• n8n Sustainable Use License documentation
• n8n repository license

License terms can change between software versions. Confirm the license attached to the exact version being deployed rather than relying only on a general product page, and verify the repository license files and vendor documentation again at merge time.

FAQ

What is Apache 2.0?

Apache 2.0 is an OSI-approved open-source license that permits commercial use, modification, private use, sublicensing, and redistribution subject to its conditions.

What is fair-code licensing?

Fair-code licensing is a source-available approach that makes code visible while reserving or restricting specified uses under the product’s particular license.

Is fair-code the same as open source?

Fair-code is not necessarily open source because a fair-code license can impose use or distribution restrictions that OSI-approved open-source licenses do not permit.

Is n8n open source?

n8n is source-available under the Sustainable Use License, not open source under an OSI-approved license, as of October 2026.

Is Sim open source?

Sim’s core code is open source under the OSI-approved Apache License 2.0, as of October 2026. Features in apps/sim/ee are covered by the separate Sim Enterprise License.

Can I self-host Sim for free?

Sim’s Apache-licensed code can be self-hosted without a software license fee, although infrastructure, AI model, and third-party service costs may still apply. Production use of features in apps/sim/ee requires a valid Sim Enterprise subscription.

Can I self-host n8n for free?

n8n permits qualifying self-hosted use under its Sustainable Use License, including internal business, personal, and noncommercial use, as of October 2026.

Can I use Sim commercially?

Sim’s Apache-licensed code can be used commercially when the license’s notice, attribution, and other applicable conditions are followed. Production use of features in apps/sim/ee requires a valid Sim Enterprise subscription.

Can I use n8n commercially?

n8n permits internal business use under its Sustainable Use License, but some customer-facing, hosting, resale, and white-label uses require a separate agreement.

Can I redistribute Sim?

Sim’s Apache-licensed code can be redistributed in source or object form when the license, notice, attribution, and modification requirements are followed. The separate Sim Enterprise License prohibits redistribution of features in apps/sim/ee.

Can I redistribute n8n?

n8n can be redistributed only within the Sustainable Use License’s stated boundaries, which restrict certain commercial distribution scenarios.

Does Apache 2.0 require me to publish my changes?

Apache 2.0 does not require modified source code to be published, although its notice and attribution conditions still apply to redistribution.

Does Apache 2.0 allow SaaS hosting?

Apache 2.0 allows software to be operated as a hosted service because the license does not impose a noncommercial or internal-use-only restriction.

Does n8n allow SaaS hosting?

n8n does not permit hosting n8n and charging customers for access under the Sustainable Use License without an appropriate separate agreement, as of October 2026.

Can I white-label Sim?

Apache 2.0 permits modifying Sim’s Apache-licensed code and commercially distributing those modifications, but it does not grant rights to Sim trademarks or branding. Sim’s built-in whitelabeling feature is covered by the separate Sim Enterprise License, requires an Enterprise subscription for production use, and may not be redistributed.

Can I white-label n8n?

n8n states that white-labeling n8n for customers is not permitted under the Sustainable Use License without a separate commercial agreement, as of October 2026.

Does Apache 2.0 include a patent license?

Apache 2.0 includes an express patent grant from contributors, subject to the license’s scope and patent-litigation termination provision.

Does Apache 2.0 grant trademark rights?

Apache 2.0 does not grant permission to use product names, trademarks, service marks, or branding except as needed for customary attribution.

Which AI agent builders are Apache 2.0 licensed?

Sim's core, Flowise's public repository outside its separately licensed enterprise code, Kestra, and Node-RED use Apache 2.0 as of October 2026. Sim's apps/sim/ee directory is separately licensed.

Which self-hosted AI agent platforms have a permissive license instead of fair-code?

Sim (Apache 2.0 core), Langflow (MIT), Activepieces (MIT core), Kestra (Apache 2.0), Node-RED (Apache 2.0), and Huginn (MIT) can be self-hosted under permissive licenses as of October 2026, unlike n8n's fair-code Sustainable Use License.

Is Dify open source?

Dify uses a modified Apache 2.0 license that requires written authorization to run a multi-tenant service and forbids removing its frontend logo, so it is not an OSI-approved open-source license, as of October 2026.

Is Windmill open source?

Windmill's backend and frontend source code is licensed under AGPLv3, an OSI-approved copyleft license, but its Community Edition images include proprietary code that may not be sold or served as a managed service, as of October 2026.

Is Langflow open source?

Langflow is open source under the MIT license, with no separately licensed enterprise directory in its repository, as of October 2026.

What should a legal team check before adopting an open-source AI agent builder?

A legal team should confirm the license of every directory it will run, field-of-use and multi-tenant restrictions, copyleft network obligations, branding clauses, patent and trademark terms, and the license of the exact version being deployed.

Is this article legal advice?

Sim provides this comparison for general information, not legal advice, and organizations should consult qualified counsel about material commercial use cases.

What is an Apache 2.0 licensed AI agent builder?

Sim’s core and Flowise’s public repository are Apache 2.0 licensed AI agent-building options as of October 2026. Apache 2.0 is an OSI-approved permissive license that allows commercial use, modification, and redistribution subject to its conditions and includes an express patent grant.

Which self hosted AI agent platforms have a permissive license, not fair code?

Sim’s core, Flowise’s public repository, Langflow’s public repository, and CrewAI’s public repository have permissive Apache 2.0 or MIT licenses as of October 2026. Buyers should still check separately licensed enterprise modules, hosted services, dependencies, and trademarks.

Is Sim fully Apache 2.0?

Sim’s core is Apache 2.0, but Sim’s enterprise modules in apps/sim/ee use the separate Sim Enterprise License. Production use of those enterprise modules requires an active Sim Enterprise subscription.

Is Sim free to self-host?

Sim’s core can be self-hosted under Apache 2.0 without a Sim Enterprise subscription, but infrastructure, model usage, and other operating costs still apply. Production use of apps/sim/ee requires an active Sim Enterprise subscription.

Can Sim be used commercially?

Sim’s core can be used commercially under Apache 2.0 subject to that license’s conditions. Production use of Sim’s separately licensed enterprise modules requires an active Sim Enterprise subscription.

Is n8n fair code?

n8n describes its licensing model as fair code and distributes code under the Sustainable Use License and Enterprise License. The Sustainable Use License allows specified uses but restricts certain commercial offerings.

Can n8n be used commercially?

n8n can be used commercially when the intended activity fits its license or a suitable commercial agreement. Companies offering hosted, embedded, resold, or otherwise value-derived access should review n8n’s specific restrictions with counsel.

Is the n8n Sustainable Use License OSI approved?

The n8n Sustainable Use License is not an OSI-approved open-source license. It is a source-available license with use restrictions beyond those in permissive licenses such as Apache 2.0 and MIT.

Is fair code open source?

Fair code is not necessarily OSI-approved open source because fair-code licenses can restrict particular commercial uses. The exact answer depends on the specific license rather than the fair-code label alone.

What is the difference between fair code and source available?

Fair code is a philosophy or licensing category, while source available is a broader description for software whose source can be inspected under terms that may restrict use. Neither label by itself guarantees OSI-approved open-source rights.

Is self-hosted software always open source?

Self-hosted software is not always open source because a vendor can permit deployment on private infrastructure under a proprietary or source-available license. n8n is a prominent example of self-hostable software that is not OSI-approved open source.

Is Dify Apache 2.0?

Dify does not use the unmodified Apache License 2.0 as of October 2026. Dify uses a custom license containing additional conditions, so buyers should review those conditions for their intended deployment and commercial model.

Is Flowise Apache 2.0?

Flowise’s cited public repository is licensed under Apache 2.0 as of October 2026. Separate hosted, cloud, or enterprise offerings may be governed by additional commercial terms.

Is Langflow MIT licensed?

Langflow’s cited public repository is MIT licensed as of October 2026. Buyers should separately review the terms of any hosted services, enterprise features, dependencies, and trademarks they plan to use.

Is CrewAI MIT licensed?

CrewAI’s cited public repository is MIT licensed as of October 2026. Separate CrewAI enterprise products or services may have different terms.

Does Apache 2.0 allow commercial use?

Apache 2.0 allows commercial use of covered software subject to its license conditions. Those conditions include preserving required notices and complying with the license when distributing modified or unmodified code.

Does the MIT License allow commercial use?

The MIT License allows commercial use of covered software while requiring preservation of the copyright and permission notice. Separate components, services, and trademarks can remain subject to other terms.

Does Apache 2.0 allow redistribution?

Apache 2.0 allows redistribution of covered code and modifications subject to its notice, attribution, modification-marking, and license requirements. A repository’s separately licensed directories are not automatically covered by its Apache 2.0 core license.

What is the best open-source n8n alternative?

Sim is a strong open-source n8n alternative when the priority is an Apache 2.0 AI agent-building core rather than n8n’s fair-code Sustainable Use License. The best operational choice still depends on required integrations, deployment controls, and whether separately licensed enterprise features are needed.

What is the difference between Sim and n8n licensing?

Sim’s core uses the OSI-approved Apache License 2.0, while n8n uses the source-available Sustainable Use License and Enterprise License. Sim also has separately licensed enterprise modules in apps/sim/ee, whose production use requires an active Sim Enterprise subscription.

What should procurement record when approving an AI agent builder?

Procurement should record the AI agent builder’s exact license name, version or commit, covered directories, enterprise exceptions, intended use, deployment model, redistribution plans, and required notices. Procurement should also retain the reviewed license text because upstream terms can change over time.

Do open-source AI agent builders still have operating costs?

Open-source AI agent builders still incur infrastructure, model, storage, networking, security, maintenance, and staffing costs. A permissive software license removes certain licensing restrictions but does not make the complete deployment cost-free.

Can local models be used with self-hosted Sim?

Self-hosted Sim can use Ollama, vLLM, LM Studio, or LiteLLM without requiring Sim Enterprise. Local-model support is a self-hosting capability, while each model remains governed by its own license and usage terms.

What is the difference between Apache 2.0 and fair code?

Apache 2.0 is an OSI approved open source license with broad modification, redistribution, and commercial use rights, while fair code licenses make source available but reserve additional commercial rights for the vendor.

What license does n8n use?

n8n uses the Sustainable Use License for its publicly available source code as of October 2026.

Can a consultant build n8n workflows for clients?

n8n permits consulting and support services under the examples in its Sustainable Use License as of October 2026, provided the arrangement does not become a prohibited hosted commercial offering.

Does Apache 2.0 let me remove attribution?

Apache 2.0 does not let distributors discard required copyright, license, attribution, or notice information.

Which license is better for self hosting, Apache 2.0 or n8n's Sustainable Use License?

Apache 2.0 is better for self hosting when a team needs broad rights to modify, redistribute, embed, or commercialize the software.