Open WebUI
Very popular chat interface for local and remote models.
Building on it: what may you do?
Short answers based on the licence, for the version in the catalog.
- B1 Change the code for internal use in your company Yes, with conditions Probably, but read the licence.
- B2 Build your own product or service on top and offer it to customers as SaaS Yes, with conditions This product has its own terms here. See the licence analysis (sign in) and verify.
- B3 Make a closed-source derivative and sell or distribute it Unclear – verify Unclear: custom licence. Verify with a lawyer.
- B4 Use the project's name and trademark No No, not without permission. The licence covers the code, not the name or logo.
This is guidance, not legal advice. Check with a lawyer before deciding.
Verify with a lawyer. Not verified: check the following in the product's own documentation before deciding: licence-thresholds.
The licence in brief
Open WebUI License (LicenseRef-Open-WebUI)
Custom licence (BSD-3 plus a branding clause): the 'Open WebUI' branding may not be removed, with some exceptions. Read the licence.
What does LicenseRef-Open-WebUI mean?
This is guidance, not legal advice (inte juridisk rådgivning). Check with a lawyer before deciding.
Facts
- Licence
- LicenseRef-Open-WebUI
- Licence type
- Custom licence
- Open core
- No
- GitHub stars
- 154k
- Latest activity
- Deployment
- Docker
- Login/SSO
- Unknown
- API
- Unknown
- Multi-tenant
- Unknown
- EU vendor
- No
- Source code
- github.com/open-webui/open-webui
- Source
- GitHub API, fetched 2026-10-03
Licence analysis per use case
Sign in to see what the licence means for eight use cases – from internal self-hosting to offering the tool as a service.
Sign in