khanh.pndc/open-webui-docs
1
0
Fork 0
mirror of https://github.com/open-webui/docs.git synced 2025-12-12 07:29:49 +07:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #849 from open-webui/main

Browse Source
This commit is contained in:
Classic298
2025-11-26 10:12:17 +01:00
committed by GitHub
parent 452b5fd9a6 ef117cfebf
commit 652eee1dd3
2 changed files with 9 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
docs/enterprise/index.mdx
View File

@@ -63,11 +63,11 @@ If you are a **consulting agency**, **AI services provider**, **solutions provid
Please understand: Please understand:
- We proactively select partners who align with our mission, vision, and values. - We proactively select partners who **align with our mission, vision, and values**.
- Being on our waitlist does not guarantee a response. If we feel there’s a strong fit, you’ll hear from us. - Being on our waitlist **does not guarantee a response**. If we feel there’s a strong fit, you’ll hear from us.
- We receive a high volume of requests and cannot respond to every inquiry. Please do not follow up or send additional messages. - We receive **a high volume of requests** and cannot respond to every inquiry. Please **do not follow up** or send additional messages.
- We prioritize mature organizations, companies less than 5 years old are not eligible, except in truly exceptional cases. - We prioritize mature organizations, companies **less than 5 years old are not eligible**, except in truly exceptional cases.
- Our program is currently at full capacity. We will reach out at our discretion should an opportunity arise. - Our program is currently at **full capacity**. We will reach out at our discretion should an opportunity arise.
<details> <details>
<summary>**If you have an end-client** who is ready to move forward with us and is committed to purchasing a rebrand (enterprise) license immediately...</summary> <summary>**If you have an end-client** who is ready to move forward with us and is committed to purchasing a rebrand (enterprise) license immediately...</summary>

6
docs/license.mdx
View File

@@ -53,7 +53,7 @@ Open WebUI’s license now:
- **You may NOT alter, remove, or obscure any “Open WebUI” branding** (name, logo, UI marks, etc.) in any deployment or distribution, except in the circumstances below. - **You may NOT alter, remove, or obscure any “Open WebUI” branding** (name, logo, UI marks, etc.) in any deployment or distribution, except in the circumstances below.
- Branding must remain clearly visible, unless: - Branding must remain clearly visible, unless:
1. **You have 50 or fewer users** in a 30-day period; 1. **You have 50 or fewer users** in a 30-day period;
2. **You are a substantive contributor**, and have gotten written permission from us for an internal deployment; 2. **You qualify as a substantive contributor [^1]**, meaning someone who has maintained at least a full year or more of consistent, non-trivial weekly contributions to the project, and have gotten written permission from us for an internal deployment;
3. **You’ve secured an enterprise license** from us which explicitly allows branding changes. 3. **You’ve secured an enterprise license** from us which explicitly allows branding changes.
- **CLA required for new contributions** after v0.6.5 (v0.6.6+) under the updated license. - **CLA required for new contributions** after v0.6.5 (v0.6.6+) under the updated license.
@@ -73,11 +73,13 @@ This is not legal advice, refer to the full [LICENSE](https://github.com/open-we
**Absolutely.** You can change, extend, and customize the code or the user interface for your organization’s needs, but you’re required to keep “Open WebUI” branding visible *unless*: **Absolutely.** You can change, extend, and customize the code or the user interface for your organization’s needs, but you’re required to keep “Open WebUI” branding visible *unless*:
- Your deployment is for **50 or fewer users in any 30-day window**; or - Your deployment is for **50 or fewer users in any 30-day window**; or
- You’re a substantive project contributor **and** have received written permission to adjust branding for an internal deployment; or - You qualify as a substantive project contributor [^1] **and** have received written permission to adjust branding for an internal deployment; or
- You’ve secured an **enterprise license** with us that explicitly allows branding changes. - You’ve secured an **enterprise license** with us that explicitly allows branding changes.
If you remove or modify branding without meeting these criteria, that’s a material breach of the license. If you remove or modify branding without meeting these criteria, that’s a material breach of the license.
[^1]: “Substantive contributor” refers to individuals who have demonstrated **long-term, high-quality, non-trivial weekly contributions for a minimum of a full year or more**, with further criteria determined by our internal policy. As external contributions often introduce more overhead than value, this status **applies only in exceptional cases and is evaluated individually**.
### 3. Aren’t these clauses contradictory? BSD-3 says you can’t use your name to promote forks, but also requires branding?! ### 3. Aren’t these clauses contradictory? BSD-3 says you can’t use your name to promote forks, but also requires branding?!
**Good question!** Our branding requirement means you **mayn’t falsely promote** your fork as “endorsed by” or “officially part of” Open WebUI (BSD-3-Clause, section 3), but it *must* still acknowledge its origins for transparency. **Good question!** Our branding requirement means you **mayn’t falsely promote** your fork as “endorsed by” or “officially part of” Open WebUI (BSD-3-Clause, section 3), but it *must* still acknowledge its origins for transparency.