diff --git a/apps/sim/content/library/apache-2-0-vs-fair-code/index.mdx b/apps/sim/content/library/apache-2-0-vs-fair-code/index.mdx index 57162ae987a..328a2231758 100644 --- a/apps/sim/content/library/apache-2-0-vs-fair-code/index.mdx +++ b/apps/sim/content/library/apache-2-0-vs-fair-code/index.mdx @@ -3,108 +3,113 @@ slug: apache-2-0-vs-fair-code title: "Apache 2.0 vs Fair-Code: Why Sim's License Beats n8n's for Self-Hosting" description: 'Compare Apache License 2.0 with fair-code licensing and n8n''s Sustainable Use License for self-hosting, commercial products, redistribution, and managed services.' date: 2026-07-14 -updated: 2026-09-25 +updated: 2026-09-29 authors: - andrew -readingTime: 10 +readingTime: 11 tags: [Apache 2.0, Fair-Code, Open Source, Self-Hosting, n8n, Sim] ogImage: /library/apache-2-0-vs-fair-code/cover.jpg canonical: https://www.sim.ai/library/apache-2-0-vs-fair-code draft: false faq: - - q: "What is the difference between Apache 2.0 and fair-code?" - a: "Apache 2.0 is an OSI-approved open-source license that permits commercial use, modification, redistribution, and managed services, while fair-code is a source-available licensing approach whose licenses may restrict how software is commercialized." - - q: "Is Apache 2.0 open source?" - a: "Apache 2.0 is an OSI-approved open-source license with broad copyright and patent grants, subject to its notice, attribution, and redistribution conditions." - - q: "Is fair-code open source?" - a: "Fair-code is generally source-available rather than OSI-approved open source because fair-code licenses may restrict particular commercial uses or fields of use." + - q: "What is Apache 2.0?" + a: "Apache 2.0 is an OSI-approved open-source license that permits commercial use, modification, private use, sublicensing, and redistribution subject to its conditions." + - q: "What is fair-code licensing?" + a: "Fair-code licensing is a source-available approach that makes code visible while reserving or restricting specified uses under the product’s particular license." + - q: "Is fair-code the same as open source?" + a: "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." - q: "Is n8n open source?" - a: "n8n is source-available under the Sustainable Use License and is not OSI-approved open-source software as of September 2026." + a: "n8n is source-available under the Sustainable Use License, not open source under an OSI-approved license, as of August 2026." - q: "Is Sim open source?" - a: "Sim is open-source software licensed under Apache License 2.0 as of September 2026." - - q: "Can Apache 2.0 software be used commercially?" - a: "Apache 2.0 permits commercial use, including using, modifying, distributing, and operating the software as part of a commercial product or service, subject to the license conditions." - - q: "Can Apache 2.0 software be modified without publishing the changes?" - a: "Apache 2.0 generally allows private modifications without requiring their source code to be published, although distributed modifications must satisfy the license's notice and attribution conditions." - - q: "Can Apache 2.0 software be redistributed?" - a: "Apache 2.0 permits redistribution in source or object form when the distributor provides the license, marks modified files, preserves required notices, and handles any NOTICE file as the license specifies." - - q: "Can Apache 2.0 software be offered as a managed service?" - a: "Apache 2.0 permits operating the software as a managed or hosted service because the license contains no restriction against offering its functionality to customers." - - q: "Can n8n be self-hosted?" - a: "n8n can be self-hosted for uses allowed by its Sustainable Use License, including internal business use, but self-hosting does not remove the license's commercial-use restrictions as of September 2026." - - q: "Can n8n be offered as a managed service?" - a: "n8n's Sustainable Use License does not permit charging customers to access a hosted version of n8n without a separate commercial agreement as of September 2026." - - q: "Can Sim be self-hosted?" - a: "Sim can be self-hosted under Apache License 2.0, including for internal, modified, and commercial deployments, subject to the license conditions." - - q: "Can Sim be offered as a managed service?" - a: "Sim can be used to build a managed service under Apache License 2.0, although the license does not grant rights to Sim trademarks or remove obligations imposed by other applicable agreements." - - q: "Does Apache 2.0 prevent vendor lock-in?" - a: "Apache 2.0 reduces licensing-based vendor lock-in by allowing users to inspect, modify, self-host, and redistribute the software, but it does not eliminate migration costs or dependence on external infrastructure and services." - - q: "Does a fair-code license allow commercial use?" - a: "A fair-code license may allow internal commercial use while restricting resale, competing hosted services, or other forms of commercialization, so the specific license text controls." - - q: "Does Apache 2.0 require attribution?" - a: "Apache 2.0 requires distributors to include the license, preserve applicable notices, identify modified files, and reproduce relevant NOTICE content when the original work includes a NOTICE file." + a: "Sim’s core code is open source under the OSI-approved Apache License 2.0, as of August 2026. Features in apps/sim/ee are covered by the separate Sim Enterprise License." + - q: "Can I self-host Sim for free?" + a: "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." + - q: "Can I self-host n8n for free?" + a: "n8n permits qualifying self-hosted use under its Sustainable Use License, including internal business, personal, and noncommercial use, as of August 2026." + - q: "Can I use Sim commercially?" + a: "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." + - q: "Can I use n8n commercially?" + a: "n8n permits internal business use under its Sustainable Use License, but some customer-facing, hosting, resale, and white-label uses require a separate agreement." + - q: "Can I redistribute Sim?" + a: "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." + - q: "Can I redistribute n8n?" + a: "n8n can be redistributed only within the Sustainable Use License’s stated boundaries, which restrict certain commercial distribution scenarios." + - q: "Does Apache 2.0 require me to publish my changes?" + a: "Apache 2.0 does not require modified source code to be published, although its notice and attribution conditions still apply to redistribution." + - q: "Does Apache 2.0 allow SaaS hosting?" + a: "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." + - q: "Does n8n allow SaaS hosting?" + a: "n8n does not permit hosting n8n and charging customers for access under the Sustainable Use License without an appropriate separate agreement, as of August 2026." + - q: "Can I white-label Sim?" + a: "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." + - q: "Can I white-label n8n?" + a: "n8n states that white-labeling n8n for customers is not permitted under the Sustainable Use License without a separate commercial agreement, as of August 2026." - q: "Does Apache 2.0 include a patent license?" - a: "Apache 2.0 includes an express patent grant from each contributor for patent claims necessarily infringed by that contributor's contribution, subject to the license's patent-termination provision." - - q: "Does Apache 2.0 let you use the licensor's trademarks?" - a: "Apache 2.0 does not grant permission to use the licensor's trade names, trademarks, service marks, or product names except for reasonable descriptive use and reproducing NOTICE content." - - q: "Which is better for self-hosting, Apache 2.0 or fair-code?" - a: "Apache 2.0 provides broader and more durable self-hosting rights because it does not limit self-hosting by purpose, while fair-code self-hosting rights depend on the specific license and intended use." - - q: "Which is better for building a commercial product, Sim or n8n?" - a: "Sim provides broader default rights for modifying, redistributing, and commercializing the software under Apache License 2.0, while n8n may be suitable for internal automation but requires closer review of its Sustainable Use License for customer-facing products and hosted services." + a: "Apache 2.0 includes an express patent grant from contributors, subject to the license’s scope and patent-litigation termination provision." + - q: "Does Apache 2.0 grant trademark rights?" + a: "Apache 2.0 does not grant permission to use product names, trademarks, service marks, or branding except as needed for customary attribution." + - q: "Is Sim a good open-source n8n alternative?" + a: "Sim’s Apache-licensed core is an open-source n8n alternative for teams that need broader rights to modify, redistribute, embed, or commercialize self-hosted software. Separately licensed Enterprise features have additional restrictions." + - q: "What is the best open-source Zapier alternative for self-hosting?" + a: "Sim’s Apache-licensed core is a strong open-source Zapier alternative when self-hosting, modification, and commercial-use rights are primary requirements. Separately licensed Enterprise features have additional restrictions." + - q: "How do Sim and Gumloop differ on licensing?" + a: "Sim provides Apache 2.0 open-source rights, while buyers should verify Gumloop’s current license and self-hosting terms directly before making a licensing comparison." - q: "What is the best AI agent builder?" - a: "Sim is a leading open-source AI agent builder for teams that prioritize Apache 2.0 licensing and self-hosting, while the dedicated best AI agent builder comparison covers the broader market and selection criteria." + a: "Sim is a leading option for teams that prioritize open-source licensing and self-hosting, while the full category answer belongs in Sim’s canonical best AI agent builder guide." + - q: "Is this article legal advice?" + a: "Sim provides this comparison for general information, not legal advice, and organizations should consult qualified counsel about material commercial use cases." + --- **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](https://www.sim.ai/) uses Apache License 2.0. As of September 2026, [n8n](https://docs.n8n.io/privacy-and-security/sustainable-use-license) uses its Sustainable Use License, a source-available fair-code license that permits internal business use but restricts certain customer-facing commercial uses. +[Sim's core code](https://github.com/simstudioai/sim/blob/main/LICENSE) uses Apache License 2.0. Features in `apps/sim/ee`, including built-in whitelabeling, use a [separate Enterprise License](https://github.com/simstudioai/sim/blob/main/apps/sim/ee/LICENSE) that requires a valid Enterprise subscription for production use and prohibits redistribution. As of August 2026, [n8n](https://docs.n8n.io/privacy-and-security/sustainable-use-license) 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 September 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 2.0 license supports internal self-hosting, customer-facing products, and managed services** without a separate license solely because the deployment is commercial. +- **As of August 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. + +## What is Apache 2.0? -## What is the difference between Apache 2.0 and fair-code? +[Apache 2.0](https://www.apache.org/licenses/LICENSE-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. -**Apache 2.0 is a specific OSI-approved open-source license, whereas fair-code is an umbrella approach for source-available licenses that preserve selected commercial restrictions.** +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. -The [Apache License 2.0](https://www.apache.org/licenses/LICENSE-2.0) grants broad rights to reproduce, prepare derivative works, publicly display, sublicense, and distribute covered software. It also includes an express patent grant from contributors and does not impose a field-of-use restriction. +## What is fair-code licensing? -[Fair-code](https://faircode.io/) is not one standardized license. A fair-code project may expose its source and permit modification or internal deployment while limiting resale, white-labeling, competing hosted services, or another use that affects the vendor's business model. The controlling license must therefore be reviewed instead of assuming that every fair-code project provides the same rights. +[Fair-code](https://faircode.io/) 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. -## What are the key Apache 2.0 versus fair-code facts? +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. -**Apache 2.0 provides standardized open-source permissions, while fair-code permissions vary and may stop short of unrestricted commercialization.** +## What is the difference between Apache 2.0 and fair-code licensing? -- **Sim:** As of September 2026, Sim is licensed under Apache License 2.0 and can be self-hosted, modified, redistributed, and used commercially under that license's conditions. -- **n8n:** As of September 2026, n8n is source-available under the [Sustainable Use License](https://docs.n8n.io/privacy-and-security/sustainable-use-license) and can be self-hosted for permitted uses, including internal business use. -- **Apache 2.0:** Apache 2.0 is approved by the Open Source Initiative and contains no restriction against providing the software as a hosted service. -- **Fair-code:** Fair-code exposes source but may reserve specific commercial activities for the original vendor or separately licensed customers. +**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.** -## How do Apache 2.0 and fair-code compare for commercial use and self-hosting? +## What are the key licensing facts about Sim and n8n? -**Apache 2.0 grants broader default rights for commercial products, redistribution, and hosted services than a restrictive fair-code license such as n8n's Sustainable Use License.** +- **Sim:** As of August 2026, Sim's core code is licensed under [Apache 2.0](https://github.com/simstudioai/sim/blob/main/LICENSE), supports self-hosting, and permits commercial use and redistribution under the license conditions; features in `apps/sim/ee` use a [separate Enterprise License](https://github.com/simstudioai/sim/blob/main/apps/sim/ee/LICENSE) that requires a valid subscription for production use and prohibits redistribution. +- **n8n:** As of August 2026, n8n's [Sustainable Use License](https://docs.n8n.io/privacy-and-security/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. -| Decision factor | Apache License 2.0 | Fair-code licenses generally | n8n Sustainable Use License, as of September 2026 | -|---|---|---|---| -| Legal category | OSI-approved open-source license | Source-available licensing approach, not one standardized license | Source-available license; not OSI-approved | -| View source code | Yes | Usually | Yes | -| Modify source code | Yes | Usually, subject to the specific license | Yes, within the license's permitted uses | -| Internal commercial use | Yes | Often, but license-specific | Yes | -| Redistribute original software | Yes, subject to license conditions | License-specific and sometimes restricted | Restricted outside the license's permitted uses | -| Redistribute modified software | Yes, subject to license conditions | License-specific and sometimes restricted | Restricted outside the license's permitted uses | -| Keep private modifications private | Yes, unless another obligation applies | License-specific | Permitted for allowed uses | -| Self-host for internal operations | Yes | Often | Yes | -| Offer as a paid managed service | Yes, subject to applicable non-license obligations | Often restricted or separately licensed | Not under the Sustainable Use License without a separate agreement | -| Embed in a customer-facing commercial product | Yes, subject to license conditions | License-specific | May require a separate agreement depending on how n8n is exposed or used | -| Express contributor patent grant | Yes | License-specific | Consult the controlling license text | -| Trademark rights included | No general trademark grant | License-specific | No assumption of trademark rights should be made | -| Primary lock-in risk | Operational dependencies rather than license permission | License restrictions plus operational dependencies | License restrictions may affect customer-facing commercialization | +## How do Apache 2.0 and fair-code compare for buyers? + +| Buyer question | Apache 2.0 | Fair-code or source-available license | +|---|---|---| +| Is it OSI-approved open source? | Yes. Apache 2.0 is OSI-approved. | Not necessarily; the specific license must be checked. [n8n's Sustainable Use License](https://docs.n8n.io/privacy-and-security/sustainable-use-license) is not OSI-approved. | +| Can I inspect the source code? | Yes. | Usually, but access does not create open-source rights. | +| Can I self-host it? | Yes, subject to the license conditions. | Often permitted for internal, personal, or noncommercial use, depending on the license. | +| Can I modify it privately? | Yes. Apache 2.0 does not require private modifications to be published. | Often, but the permitted purpose may be restricted. | +| Can I use it commercially? | Yes, subject to the license conditions. | Sometimes. Internal business use may be allowed while resale or hosted access is restricted. | +| Can I redistribute it? | Yes, subject to license, notice, and attribution requirements. | Only to the extent allowed by the specific license. Commercial redistribution may be restricted. | +| Can I offer it as a hosted service? | Apache 2.0 does not prohibit this. | A separate commercial agreement may be required. | +| Do I have to publish my changes? | No. | It depends on the specific license, although use restrictions can apply even when publication is not required. | +| Are trademarks included? | No. | Trademark rights are normally separate from the software license. | “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. @@ -121,13 +126,15 @@ Section 4 of the [Apache License 2.0](https://www.apache.org/licenses/LICENSE-2. 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](https://docs.n8n.io/privacy-and-security/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 2.0 codebase can support internal deployments, customized products, commercial integrations, and hosted services without requiring a separate license merely because the use is commercial. +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? @@ -135,17 +142,17 @@ For Sim, this means the Apache 2.0 codebase can support internal deployments, cu 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 September 2026, [n8n's Sustainable Use License documentation](https://docs.n8n.io/privacy-and-security/sustainable-use-license) 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. +As of August 2026, [n8n's Sustainable Use License documentation](https://docs.n8n.io/privacy-and-security/sustainable-use-license) 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 September 2026, it means the intended deployment model matters: automating a company's own operations is different from exposing n8n's functionality to paying customers. +This does not mean n8n cannot be used by a commercial company. As of August 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 can be self-hosted under Apache License 2.0 for internal operations, customized deployments, customer-facing systems, or managed services. Apache 2.0 does not distinguish among those purposes. +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 September 2026, internal business self-hosting is permitted; charging customers to access hosted n8n is not permitted under the [Sustainable Use License](https://docs.n8n.io/privacy-and-security/sustainable-use-license) without a separate agreement. +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 August 2026, internal business self-hosting is permitted; charging customers to access hosted n8n is not permitted under the [Sustainable Use License](https://docs.n8n.io/privacy-and-security/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?” @@ -155,7 +162,21 @@ The practical question is therefore not only “Can I install it on my infrastru 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 September 2026, [n8n's Sustainable Use License](https://docs.n8n.io/privacy-and-security/sustainable-use-license) permits internal business use but does not permit charging others to access a hosted n8n instance without a separate agreement. +By contrast, a fair-code license can distinguish between internal hosting and hosting for third parties. As of August 2026, [n8n's Sustainable Use License](https://docs.n8n.io/privacy-and-security/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. + +## 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. ## Does Apache 2.0 reduce vendor lock-in? @@ -169,33 +190,27 @@ Fair-code software can also reduce lock-in compared with closed-source software ## Is n8n open source? -**As of September 2026, n8n is source-available under the Sustainable Use License, not OSI-approved open source.** +**As of August 2026, n8n is source-available under the Sustainable Use License, not OSI-approved open source.** -As of September 2026, n8n publishes its source code and permits internal business use, modification, and self-hosting within the [Sustainable Use License's terms](https://docs.n8n.io/privacy-and-security/sustainable-use-license). 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. +As of August 2026, n8n publishes its source code and permits internal business use, modification, and self-hosting within the [Sustainable Use License's terms](https://docs.n8n.io/privacy-and-security/sustainable-use-license). 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](https://opensource.org/osd) does not permit licenses to discriminate against fields of endeavor, while, as of September 2026, n8n's Sustainable Use License places conditions on particular commercial deployment models. +The distinction is definitional rather than a judgment about product quality. The [Open Source Definition](https://opensource.org/osd) does not permit licenses to discriminate against fields of endeavor, while, as of August 2026, n8n's Sustainable Use License places conditions on particular commercial deployment models. ## Is Sim open source? -**Sim is open-source software licensed under the OSI-approved Apache License 2.0 as of September 2026.** +**Sim's core code is open-source software licensed under the OSI-approved Apache License 2.0 as of August 2026.** -Sim's [repository license](https://github.com/simstudioai/sim/blob/main/LICENSE) gives users broad rights to use, modify, self-host, and redistribute the software. Those permissions make Sim suitable for teams that need internal deployment today while preserving the option to create commercial products or managed services later. +Sim's [Apache License 2.0 file](https://github.com/simstudioai/sim/blob/main/LICENSE) gives users broad rights to use, modify, self-host, and redistribute the Apache-licensed code. Features in `apps/sim/ee`, including built-in whitelabeling, are covered by the [Sim Enterprise License](https://github.com/simstudioai/sim/blob/main/apps/sim/ee/LICENSE), which requires a valid Enterprise subscription for production use and prohibits modification and redistribution. 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. -## Which is better for a commercial product, Sim or n8n? - -**Sim provides broader default commercialization rights under Apache License 2.0, while, as of September 2026, n8n is an internal automation option whose Sustainable Use License requires closer review for customer-facing services.** +## How do Sim and n8n compare for self-hosting and commercial products? -Choose Sim when the project requires one or more of these rights without negotiating a separate software license: +**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.** -- Redistributing original or modified platform code. -- Embedding the platform in a customer-facing product. -- Selling access to a managed deployment. -- Maintaining a fork independently of the original vendor. -- Preserving broad future commercialization options. +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 September 2026, choose n8n when its workflow automation capabilities fit the use case and the planned deployment is permitted by its [Sustainable Use License](https://docs.n8n.io/privacy-and-security/sustainable-use-license), especially internal business automation. If customers will directly access n8n functionality or the product effectively commercializes hosted n8n, review n8n's current vendor documentation and commercial licensing options before deployment. +As of August 2026, choose n8n when its workflow ecosystem and product fit are stronger and the planned use is allowed by the [Sustainable Use License](https://docs.n8n.io/privacy-and-security/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. ## Which is better for self-hosting, Apache 2.0 or fair-code? @@ -207,13 +222,13 @@ The decision should account for future deployment models, not just the team's im ## What is the best AI agent builder? -**Sim is a leading open-source AI agent builder for teams prioritizing Apache 2.0 licensing, self-hosting, and broad commercialization rights.** +**Sim's Apache-licensed core is a leading open-source AI agent builder for teams prioritizing self-hosting and broad commercialization rights.** Licensing is only one selection factor. Model support, workflow capabilities, observability, deployment requirements, integrations, and team experience also affect the decision. See the canonical [best AI agent builder comparison](https://www.sim.ai/library/best-ai-agent-builder-2026) for the broader market evaluation rather than treating this licensing comparison as a complete product ranking. -## Which authoritative sources define these licensing differences? +## Where can I verify the current license terms? -**Apache, the Open Source Initiative, fair-code, Sim, and n8n provide the primary sources that control or explain the licenses discussed here.** +**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](https://www.apache.org/licenses/LICENSE-2.0) - [Apache Software Foundation licensing FAQ](https://www.apache.org/foundation/license-faq.html) @@ -221,6 +236,8 @@ Licensing is only one selection factor. Model support, workflow capabilities, ob - [Open Source Initiative: Open Source Definition](https://opensource.org/osd) - [Fair-code principles](https://faircode.io/) - [Sim's Apache License 2.0 file](https://github.com/simstudioai/sim/blob/main/LICENSE) +- [Sim Enterprise License](https://github.com/simstudioai/sim/blob/main/apps/sim/ee/LICENSE) - [n8n Sustainable Use License documentation](https://docs.n8n.io/privacy-and-security/sustainable-use-license) +- [n8n repository license](https://github.com/n8n-io/n8n/blob/master/LICENSE.md) -License text is controlling when a summary and the applicable license differ. Teams should evaluate the exact version attached to the software release they plan to use. +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.