{ "id": "conv_20251104_121115_492", "title": "openwebui是开源的吗？可以商用吗？", "created_at": "2025-11-04T12:11:15.492573", "updated_at": "2025-11-04T12:20:57.058842", "messages": [ { "role": "user", "content": "openwebui是开源的吗？可以商用吗？", "timestamp": "2025-11-04T12:11:34.561845" }, { "role": "assistant", "content": "我来帮您查询一下OpenWebUI的开源许可和商用相关信息。", "timestamp": "2025-11-04T12:11:36.550136" }, { "role": "assistant", "content": "", "timestamp": "2025-11-04T12:11:36.553503", "tool_calls": [ { "id": "web_search:0", "index": 0, "type": "function", "function": { "name": "web_search", "arguments": "{\"query\": \"OpenWebUI open source license commercial use GitHub\", \"max_results\": 5}" } } ] }, { "role": "tool", "content": "{\"success\": true, \"summary\": \"🔍 搜索查询: OpenWebUI open source license commercial use GitHub\\n📅 搜索时间: 2025-11-04T12:11:40.234429\\n🎯 过滤条件: Topic: general\\n\\n📝 AI摘要:\\nOpen WebUI is permissively licensed for any use, but commercial use requires compliance with specific terms. The project allows modifications and redistributions, provided branding is respected. For commercial use, fees may apply.\\n\\n---\\n\\n📊 搜索结果:\\n\\n1. Change of license to non-commercial use #6506 - GitHub\\n 🔗 https://github.com/open-webui/open-webui/discussions/6506\\n 📄 | Open-Webui should move to a free for non-commercial use license. MIT License is OK for starter projects. Perhaps: CC BY-NC-SA 4.0 Attribution-NonCommercial-ShareAlike 4.0 International Add a c...\\n\\n2. Open WebUI changed license from BSD-3 ...\\n 🔗 https://news.ycombinator.com/item?id=43901575\\n 📄 class=\\\"commtext c00\\\">The license is still open source. There's only a branding requirement added. Not much unlike \\\"you must retain this notice\\\" in other open-source licenses, like the Apache license.<...\\n\\n3. ️ Open WebUI License\\n 🔗 https://openwebui.com/license/\\n 📄 ⚖️ Open WebUI License | Open WebUI\\n\\nSkip to main content\\n\\nImage 1 Open WebUIBlog\\n\\nGitHubDiscord\\n\\nImage 2: Open WebUI\\n\\nThe top banner spot is reserved for Emerald+ Enterprise sponsors\\n\\n 🏡 Home\\n 🚀 G...\\n\\n4. Tell me your opinions about the license change! #13458\\n 🔗 https://github.com/open-webui/open-webui/discussions/13458\\n 📄 everything. My personal verdict is: this doesn't make Open WebUI any less free to use nor any less open source, and it prevents those Open WebUI imitations that claim this to be their work and even c...\\n\\n5. Open WebUI: Home\\n 🔗 https://docs.openwebui.com/\\n 📄 Skip to main content\\n\\n# Open WebUI\\n\\nOpen WebUI is an extensible, feature-rich, and user-friendly self-hosted AI platform designed to operate entirely offline. It supports various LLM runners like Olla...\", \"filters\": {\"topic\": \"general\"}, \"query\": \"OpenWebUI open source license commercial use GitHub\", \"results\": [{\"index\": 1, \"title\": \"Change of license to non-commercial use #6506 - GitHub\", \"url\": \"https://github.com/open-webui/open-webui/discussions/6506\", \"content\": \"| Open-Webui should move to a free for non-commercial use license. MIT License is OK for starter projects. Perhaps: CC BY-NC-SA 4.0 Attribution-NonCommercial-ShareAlike 4.0 International Add a commercial use agreement along with the CC BY-NC-SA 4.0 |\\n\\nBeta Was this translation helpful? Give feedback.\\n\\nYou must be logged in to vote\\n\\nAll reactions \\n\\n 👎 2\\n\\n## Replies: 1 comment\\n\\nComment options\\n\\n### Uh oh!\\n\\nThere was an error while loading. Please reload this page.\\n\\n### Uh oh! [...] Skip to content \\n\\n## Navigation Menu\\n\\nSign in \\n\\nAppearance settings\\n\\n# Search code, repositories, users, issues, pull requests...\\n\\nSearch syntax tips\\n\\nSign in\\n\\n Sign up \\n\\nAppearance settings\\n\\nYou signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert\\n\\n{{ message }}\\n\\nopen-webui / open-webui Public\\n\\n ### Uh oh! [...] from Licensor. Commercial use includes: Selling the Software, either as is or as part of a larger software package. Using the Software as an interface or component of a service where customers pay to use it. Incorporating the Software, in part or in whole, into a commercial operation where people pay to use the resulting product or service. The fees for commercial use are set forth on Licensor's website at [INSERT URL]. RESTRICTIONS. Licensee shall not: Use, modify, or distribute the Software\", \"score\": 0.76554126, \"published_date\": \"\"}, {\"index\": 2, \"title\": \"Open WebUI changed license from BSD-3 ...\", \"url\": \"https://news.ycombinator.com/item?id=43901575\", \"content\": \"class=\\\"commtext c00\\\">The license is still open source. There's only a branding requirement added. Not much unlike \\\"you must retain this notice\\\" in other open-source licenses, like the Apache license.

I frankly find LGPL more useful in cases like that, but it apparently does not work for some parties. Open-source + commercial licensing also looks like a good balance between keeping the community-developed code accessible to everyone, while allowing the parties who don't want to share to pay [...] people not understand the implications choosing an open source license.in the first place? There are a million licenses, in fact you can just make your own one up! But when you choose a class of license the specifically allows commercial exploitation... you don't get to act wronged when it happens.

reply

If the project is controlled by a commercial entity, you just have to understand it will likely change in a way you disagree with.

reply

_“This project is a customized fork of [Open WebUI](https://github.com/open-webui/open-webui). This release is not affiliated with or maintained by the official Open WebUI team.”_\\n\\nDisplay this message—prominently—in the About section, landing page, or equivalent location. **Transparency is required.**\\n\\n* * *\\n\\nProprietary License / Enterprise Branding[​](https://openwebui.com/license/#proprietary-license--enterprise-branding \\\"Direct link to Proprietary License / Enterprise Branding\\\")\\n--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------\\n\\nIf you are a business that needs private or custom branding, advanced white-label deployments, or tailored features for mission-critical use cases, **we offer proprietary and enterprise licenses**. We’ll work with you to ensure your needs and your branding are fully addressed, with a world-class support and engineering team backing your deployment.\\n\\n**[Click here](https://docs.openwebui.com/enterprise) for more information about commercial options.**\\n\\n* * *\\n\\nBranding, Attribution, and Customization Guidelines: What’s Allowed (and What’s Not)[​](https://openwebui.com/license/#branding-attribution-and-customization-guidelines-whats-allowed-and-whats-not \\\"Direct link to Branding, Attribution, and Customization Guidelines: What’s Allowed (and What’s Not)\\\")\\n-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------\\n\\nWe want to make it as straightforward as possible for everyone, users, businesses, integrators, and contributors, to follow Open WebUI’s fair-use branding policy. **Transparency is key.** Here’s a simple, practical guide:\\n\\n* The Open WebUI NAME and LOGO must remain in their original, prominent locations throughout the application and user interface, including, but not limited to, the site header, sidebar, login screens, about page, and any other area where Open WebUI branding appears by default.\\n* ALL visual “Open WebUI” elements, logos, wordmarks, “About”/“Help” links, and any system/credits screens, must remain unmodified and fully visible.\\n* You must NOT obscure, overlay, or minimize Open WebUI branding in any way that de-emphasizes its identity, or suggests your build is the “official” one when it isn’t.\\n* Side-by-side branding: If, with approval, you add your own logo next to “Open WebUI,” the Open WebUI logo must always appear first (left or top), be fully visible, and your logo must be smaller and secondary. This is rarely allowed without a commercial license.\\n\\n### **What is (Typically) ALLOWED Without a License**[​](https://openwebui.com/license/#what-is-typically-allowed-without-a-license \\\"Direct link to what-is-typically-allowed-without-a-license\\\")\\n\\n| Scenario | Allowed Without License? | Guidance / Notes |\\n| --- | --- | --- |\\n| **Use Open WebUI “as is” with branding** | ✅ | Just use the software as provided; no changes to logo, name, or identity. Easiest option! |\\n| **Add custom features, UI extensions, plugins while keeping Open WebUI branding fully intact** | ✅ | Absolutely encouraged! You can add new buttons, workflows, extensions, etc.—just don’t remove or alter Open WebUI’s own name and logo. |\\n| **Deploy to any number of internal users within your own organization (with all official branding kept)** | ✅ | Scale however you like! No per-user limits for internal/staff/company-wide use as long as Open WebUI branding is always present and prominent. |\\n| **Integrate Open WebUI with internal tools, scripts, or enterprise authentication** | ✅ | SSO, LDAP, custom backends—all welcomed! Integration is wide open, provided branding remains. |\\n| **Add a small, unobtrusive info banner at top, bottom, or side (e.g., “Managed by YourOrg”)** | ✅ | Banner must be visually secondary/subordinate (footer, bottom-right, etc.), not obscuring or distracting from Open WebUI’s branding. |\\n| **Add a legal or company link/notice in the About modal/dialog** | ✅ | Feel free to provide an additional legal link, team contact, or credits section—just never replace or remove Open WebUI credits. |\\n| **Add monitoring, analytics, or custom backend features** | ✅ | Backend integrations and observability are totally permitted. No restrictions if branding/UI is untouched. |\\n| **Create and maintain your own public fork (with all branding, plus “fork disclosure” notice)** | ✅ | As long as you keep branding as required and clearly state it’s “a fork of Open WebUI, not official.” |\\n| **Link to your company/project/github in the footer or About box** | ✅ | No problem if subordinate—must not give impression of replacing or rebranding the app. |\\n| **For deployments ≤50 users/rolling 30-day period** | ✅ | “Small scale” deployments may remove Open WebUI branding, but only under the explicit user count threshold—see policy for details. |\\n\\n### **What is NOT ALLOWED Without an Enterprise/Proprietary License**[​](https://openwebui.com/license/#what-is-not-allowed-without-an-enterpriseproprietary-license \\\"Direct link to what-is-not-allowed-without-an-enterpriseproprietary-license\\\")\\n\\n| Scenario | Allowed Without License? | Why NOT Allowed/Details |\\n| --- | --- | --- |\\n| Removing **ANY** Open WebUI logo/name from the UI | ❌ | This is a clear violation, even if you add “Powered by Open WebUI” somewhere else. |\\n| Modifying/changing the Open WebUI logo or color scheme to your branding | ❌ | The identity must remain clear and intact. No recoloring or swaps. |\\n| Adding your logo side-by-side/equal in size or priority (**Co-branding**) | ❌ | Co-branding of any kind is strictly forbidden. Your logo must NOT appear next to, be the same size as, or in comparable proximity or prominence to Open WebUI’s logo or name under any circumstances. |\\n| Calling your fork “Open WebUI Enterprise” or misleadingly similar | ❌ | Don’t use our project’s name or branding in a way that could confuse users about source or official status. |\\n| Major UI modifications that move, minimize, or obscure original Open WebUI branding | ❌ | Moving the logo, shrinking it, hiding it, or pushing it offscreen violates the terms. |\\n| White-labelling for your business/SaaS | ❌ | You MUST get an enterprise or proprietary license before removing our branding for mass redistribution or resale. |\\n| “Powered by Open WebUI” credit ONLY (if all native branding is hidden/removed) | ❌ | This is NOT enough and does not meet license terms. |\\n\\n### **How to Add Custom Branding Responsibly**[​](https://openwebui.com/license/#how-to-add-custom-branding-responsibly \\\"Direct link to how-to-add-custom-branding-responsibly\\\")\\n\\n* **DO NOT remove, shrink, relocate, or recolor Open WebUI branding.**\\n* **Co-branding is not allowed at all.** You may NOT display your branding/logo adjacent to or alongside Open WebUI’s logo/name, nor may you display your branding in a manner that creates visual equivalence or confusion.\\n* **If you want to add a “Managed by Company X” banner**, it must remain clearly distinct, unobtrusive, and subordinate to Open WebUI’s own visual hierarchy.\\n* **Don’t “co-brand” or sandwich your logo next to ours** without explicit written approval. For nearly all non-trivial cases, you will need a commercial or custom license.\\n* **Always show us a screenshot before launch!** If in doubt, email [hello@openwebui.com](mailto:hello@openwebui.com)—we’re happy to review and advise.\\n\\n### **Still Unsure?**[​](https://openwebui.com/license/#still-unsure \\\"Direct link to still-unsure\\\")\\n\\nIf you’re ever unsure, please feel free to contact us and share your planned deployment (even just a screenshot or Figma mockup) before launching. Our goal is to work with everyone and support honest, respectful uses—we’re always happy to offer guidance or help you with the right license if needed. Openness and fairness for all is important to us, so let’s collaborate to make it work for everyone.\\n\\n* * *\\n\\n_This page is provided for informational purposes only and does not constitute legal advice. For exact and legally binding terms, refer to the full text of the [LICENSE](https://github.com/open-webui/open-webui/blob/main/LICENSE)._\\n\\n**Thank you for respecting the Open WebUI community, our contributors, and our project’s future.**\\n\\n[Edit this page](https://github.com/open-webui/docs/blob/main/docs/license.mdx)\\n\\n[Previous 🎨 Design Guidelines](https://openwebui.com/brand)[Next 🏢 Open WebUI for Enterprises](https://openwebui.com/enterprise/)\\n\\n* [Keeping Open WebUI Free, Fair, and Sustainable](https://openwebui.com/license/#keeping-open-webui-free-fair-and-sustainable)\\n* [Open WebUI License: Explained](https://openwebui.com/license/#open-webui-license-explained)\\n* [Frequently Asked Questions (FAQ)](https://openwebui.com/license/#frequently-asked-questions-faq)\\n * [**1. Can I still use Open WebUI freely for personal projects, businesses, or teaching?**](https://openwebui.com/license/#1-can-i-still-use-open-webui-freely-for-personal-projects-businesses-or-teaching)\\n * [**2. I want to fork Open WebUI and change the UI to fit my use case. Is that allowed?**](https://openwebui.com/license/#2-i-want-to-fork-open-webui-and-change-the-ui-to-fit-my-use-case-is-that-allowed)\\n * [**3. Aren’t these clauses contradictory? BSD-3 says you can’t use your name to promote forks, but also requires branding?!**](https://openwebui.com/license/#3-arent-these-clauses-contradictory-bsd-3-says-you-cant-use-your-name-to-promote-forks-but-also-requires-branding)\\n * [**4. Why did you add this clause? Isn’t open source supposed to be fully free?**](https://openwebui.com/license/#4-why-did-you-add-this-clause-isnt-open-source-supposed-to-be-fully-free)\\n * [**5. I’m a real contributor. Do these restrictions limit my rights?**](https://openwebui.com/license/#5-im-a-real-contributor-do-these-restrictions-limit-my-rights)\\n * [**6. Does this mean Open WebUI is “no longer open source”?**](https://openwebui.com/license/#6-does-this-mean-open-webui-is-no-longer-open-source)\\n * [**7. What if I want to white-label or deeply customize Open WebUI for my enterprise?**](https://openwebui.com/license/#7-what-if-i-want-to-white-label-or-deeply-customize-open-webui-for-my-enterprise)\\n * [**8. What if I already deployed Open WebUI before v0.6.6?**](https://openwebui.com/license/#8-what-if-i-already-deployed-open-webui-before-v066)\\n * [**9. What about forks? Can I start one and remove all Open WebUI mentions?**](https://openwebui.com/license/#9-what-about-forks-can-i-start-one-and-remove-all-open-webui-mentions)\\n * [**10. I’m an individual academic/non-profit researcher. Can I customize or remove branding for a research study?**](https://openwebui.com/license/#10-im-an-individual-academicnon-profit-researcher-can-i-customize-or-remove-branding-for-a-research-study)\\n\\n* [Proprietary License / Enterprise Branding](https://openwebui.com/license/#proprietary-license--enterprise-branding)\\n* [Branding, Attribution, and Customization Guidelines: What’s Allowed (and What’s Not)](https://openwebui.com/license/#branding-attribution-and-customization-guidelines-whats-allowed-and-whats-not)\\n * [**What is (Typically) ALLOWED Without a License**](https://openwebui.com/license/#what-is-typically-allowed-without-a-license)\\n * [**What is NOT ALLOWED Without an Enterprise/Proprietary License**](https://openwebui.com/license/#what-is-not-allowed-without-an-enterpriseproprietary-license)\\n * [**How to Add Custom Branding Responsibly**](https://openwebui.com/license/#how-to-add-custom-branding-responsibly)\\n * [**Still Unsure?**](https://openwebui.com/license/#still-unsure)\\n\\nDocs\\n\\n* [Getting Started](https://openwebui.com/getting-started)\\n* [FAQ](https://openwebui.com/faq)\\n* [Help Improve The Docs](https://github.com/open-webui/docs)\\n\\nCommunity\\n\\n* [GitHub](https://github.com/open-webui/open-webui)\\n* [Discord](https://discord.gg/5rJgQTnV4s)\\n* [Reddit](https://www.reddit.com/r/OpenWebUI/)\\n* [𝕏](https://x.com/OpenWebUI)\\n\\nMore\\n\\n* [Release Notes](https://github.com/open-webui/open-webui/blob/main/CHANGELOG.md)\\n* [About](https://openwebui.com/)\\n* [Report a Vulnerability / Responsible Disclosure](https://openwebui.com/)\\n\\n![Image 6](https://openwebui.com/images/logo-dark.png)\\n==================================================\"}", "timestamp": "2025-11-04T12:11:45.982651", "tool_call_id": "extract_webpage:1", "name": "extract_webpage" }, { "role": "assistant", "content": "基于我查到的信息，我来为您详细解答OpenWebUI的开源和商用情况：\n\n## OpenWebUI的开源状态\n\n**是的，OpenWebUI是开源的**，但需要注意一些重要的许可变化：\n\n### 许可证变化历史\n- **2025年4月之前（v0.6.5及更早版本）**：使用非常宽松的BSD-3-Clause许可证\n- **2025年4月起（v0.6.6+）**：采用了新的许可证，增加了品牌保护条款\n\n### 当前许可证特点\n\n**✅ 仍然免费和相对开放：**\n- 可以继续免费使用、修改和分发\n- 源代码完全公开\n- 可以商业使用\n- 可以构建商业产品和服务\n\n**⚠️ 新增的限制：**\n- **品牌保护要求**：不能移除或修改\"OpenWebUI\"的品牌标识\n- 必须保留OpenWebUI的logo和名称在界面中\n- 除非满足特定条件，否则不能进行白标（white-label）部署\n\n## 商用许可\n\n**可以商用，但有条件：**\n\n### 免费商用的情况\n1. **小规模使用**：30天内用户数≤50人的部署可以移除品牌\n2. **内部使用**：企业内部使用，保留OpenWebUI品牌标识\n3. **个人项目**：个人或小型团队的项目\n\n### 需要商业许可的情况\n1. **大规模商业部署**：用户数超过50人\n2. **白标/定制品牌**：需要移除或替换OpenWebUI品牌\n3. **SaaS服务**：作为付费服务提供给客户\n4. **OEM集成**：将OpenWebUI集成到商业产品中\n\n### 企业许可选项\nOpenWebUI提供专门的企业许可证，包括：\n- 完全的品牌定制权限\n- 优先技术支持\n- 定制功能开发\n- 专业服务保障\n\n## 实际应用建议\n\n**对于个人用户和小团队：**\n- 完全可以免费使用\n- 可以添加功能扩展，只要保留原始品牌\n\n**对于企业用户：**\n- 内部使用：免费，保留品牌\n- 商业产品：建议联系官方获取企业许可\n\n**对于开发者：**\n- 可以基于OpenWebUI开发新功能\n- 如果要fork并大规模修改品牌，需要考虑许可要求\n\n总的来说，OpenWebUI仍然是一个相对开放的项目，只是在品牌保护方面增加了一些限制，以防止不良行为者滥用。对于大多数正当使用场景，它仍然是免费和开放的。", "timestamp": "2025-11-04T12:11:58.227221" } ], "todo_list": null, "metadata": { "project_path": "/opt/agent/agents/users/jojo/project", "project_relative_path": "users/jojo/project", "thinking_mode": true, "total_messages": 8, "total_tools": 4, "status": "active" }, "token_statistics": { "total_input_tokens": 43409, "total_output_tokens": 968, "updated_at": "2025-11-04T12:20:57.059027" } }