Félix Malfait
a9d996ff7e
## What - `twenty-sdk`, `twenty-client-sdk`, `create-twenty-app`, `twenty-shared` and `twenty-ui` are now MIT (package.json + LICENSE files). The SDKs are bundled into third-party applications and app front components import twenty-ui, so these need a permissive license for apps to be licensable by their authors. `twenty-shared` is included because both SDKs inline it at build time; an MIT SDK bundling AGPL code would defeat the purpose. Apps under `packages/twenty-apps` were already MIT. - Added a "Twenty Application Exception" to LICENSE (additional permission under AGPLv3 section 7): applications that interact with Twenty through the app platform interfaces (APIs, manifests, logic functions, front components, SDKs) are not subject to copyleft and can be licensed freely by their authors. Modifying Twenty itself remains fully AGPL, including the network clause. - Rewrote the LICENSE intro to describe the three licensing zones (AGPL, Enterprise-marked files, MIT packages) and fixed the intro incorrectly saying "GPL". - Added TRADEMARK.md: what anyone can do without asking (self-host, "built on Twenty", forks under their own name) and what requires permission (using the name or logo for a product, domain, or hosted offering). ## Why Gives app developers and partners legal certainty that building on the platform does not pull their apps under AGPL, while the core stays AGPL. The exception and trademark wording should get a legal review before being announced.
2.2 KiB
Twenty Trademark Policy
"Twenty", the Twenty logo, and twenty.com are trademarks of Twenty.com, PBC ("Twenty"), whether registered or unregistered. The source code of Twenty is open source under the licenses described in LICENSE; those licenses do not grant any rights to use our trademarks.
The goal of this policy is simple: anyone should be able to say truthfully that they use, build on, or contribute to Twenty, and nobody should suggest an affiliation with or endorsement by Twenty that does not exist, or confuse users about what comes from us.
You can, without asking
- Use and self-host Twenty, modified or not, for yourself or your organization, and say that you do.
- Make truthful statements such as "built on Twenty", "compatible with Twenty", "powered by Twenty", or "we host Twenty for our clients".
- Name an application or integration "X for Twenty" or "Twenty integration for X", as long as your own brand is the dominant element and you do not use our logo as your own.
- Use the name "Twenty" to refer to the project in articles, talks, tutorials, courses, and comparisons.
- Link to twenty.com and use unmodified screenshots of the product.
You need our written permission to
- Use "Twenty" or a confusingly similar name in the name of your company, product, service, domain name, social media account, or app store listing (for example "TwentyCloud" or "twenty-hosting.com").
- Market a hosted, managed, or modified version of Twenty in a way that suggests it is an official Twenty offering, or is endorsed by or affiliated with Twenty.
- Use the Twenty logo as, or as part of, your own logo or branding.
- Sell merchandise bearing the Twenty name or logo.
Forks
You may maintain and distribute forks of the source code under the terms of the applicable licenses. If you distribute or operate a fork publicly, give it its own name and branding. You may state truthfully that it is "a fork of Twenty", but do not use the Twenty name or logo in a way that suggests your fork is the original project.
Questions
If you are unsure whether your use is allowed, or want to request permission, open an issue on GitHub or contact us through twenty.com.