docs(library): update apache-2-0-vs-fair-code - #8297
Conversation
|
@cubic review |
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
@icecrasher321 I have started the AI code review. It will take a few minutes to complete. |
|
|
|
||
| **Apache 2.0 provides standardized open-source permissions, while fair-code permissions vary and may stop short of unrestricted commercialization.** | ||
|
|
||
| - **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. |
There was a problem hiding this comment.
Sim license scope overstated The article says Sim can be modified, redistributed, and used commercially under Apache 2.0, and makes similar claims in the self-hosting FAQ and body. That is true of the Apache-licensed code, but
apps/sim/ee/ has a separate license: production use requires a subscription, and modification and redistribution are prohibited. A reader planning to deploy or build on enterprise features could rely on rights they do not have. Please restore the distinction between the Apache-licensed core and enterprise features.
Content update to
apps/sim/content/library/apache-2-0-vs-fair-code: Refresh the existing library post at /library/apache-2-0-vs-fair-code without changing its URL or slug. Replace the current body with the supplied direct-answer-led article and migrate the supplied FAQ array into the post's frontmatter so the renderer emits FAQPage schema. Preserve any existing valid authoritative citations or legal details that add information without conflicting with this draft. Add the extractable three-way comparison table covering Apache 2.0, fair-code generally, and n8n's Sustainable Use License. Keep all n8n license statements dated As of September 2026 and recheck them against n8n's own Sustainable Use License page immediately before publication; recheck Sim's Apache 2.0 LICENSE file as well. Do not describe n8n as OSI-approved open source: call it source-available under the Sustainable Use License. Keep fair-code framed as an umbrella approach rather than a single standardized license. Preserve the distinction between internal self-hosting and offering paid hosted access. Route broad best-AI-agent-builder intent to /library/best-ai-agent-builder-2026 rather than competing with that canonical page. Do not add hand-written JSON-LD or Markdown formatting and links inside FAQ questions or answers.