Open WebUI Enterprise License Explained: The 50-User Branding Clause (2026)

Open WebUI is still free to self-host at any scale with no functional limits, but since version 0.6.6 (19 April 2025) it is no longer under an OSI-approved open-source licence - it uses a modified BSD-3-Clause licence (the "Open WebUI Licence") that prohibits removing or altering the Open WebUI branding once a deployment exceeds 50 end users in any rolling 30-day period, unless you have written permission or an enterprise licence. The code remains open and free to run; the restriction is specifically on stripping the branding at scale. This guide explains, factually and neutrally: what changed and when (it was two separate changes), the exact wording of the clause, what counts as an "end user," what the enterprise licence adds, and the three realistic options for organisations - keep the branding, buy the enterprise licence, or move to an alternative such as an MIT-licensed tool or a governed platform. All facts verified against the official LICENSE file and docs.openwebui.com, June 2026.

Open WebUI is one of the most popular self-hosted AI interfaces in existence - roughly 142,000 GitHub stars and 20,400 forks as of June 2026 (Source), built with a Python FastAPI backend and a Svelte frontend, and described by third-party reviewers as "an open-source, self-hosted platform" with a chat interface, support for multiple LLM runners such as Ollama and OpenAI-compatible APIs, a built-in inference engine for RAG, and tool handling (Source). Its popularity is exactly why the licence question matters: a lot of organisations deployed it when it was MIT-licensed and need to understand what changed.

The confusion is understandable, because there were two separate licence changes, and they are easy to conflate. This guide separates them cleanly and quotes the operative text directly, so you can make an informed decision rather than relying on second-hand summaries. We are vendor-neutral here on purpose: Open WebUI is an excellent project, the licence change is a defensible response to a real problem, and the goal of this article is accuracy, not advocacy.

Open WebUI's licence evolved in two distinct steps. Treating them as one event is the most common mistake people make when discussing this.

Step 1: MIT to BSD-3-Clause (10 January 2025)

Open WebUI began under the permissive MIT licence. On 10 January 2025, the project moved to a clean, still-permissive BSD-3-Clause licence. The stated reason was bad actors impersonating the project - fake crypto schemes, scam services, and fake offerings trading on the Open WebUI name. At this point the team's message was effectively "nothing changes for legitimate users"; BSD-3-Clause is a standard, OSI-approved open-source licence (Source).

Step 2: The branding clause is added (v0.6.6, 19 April 2025)

The consequential change came with version 0.6.6 on 19 April 2025, when Open WebUI added a branding-protection clause on top of the BSD-3-Clause base, creating what the project calls the "Open WebUI Licence." The official documentation states this plainly: the licence is "not an OSI-approved 'open source' license," it is "effective with v0.6.6 (April 19, 2025)," and "the original BSD-3 license continues to apply for all contributions made to the codebase up to and including release v0.6.5" (Source). GitHub's API reflects this by classifying the repository licence as NOASSERTION rather than a recognised SPDX identifier (Source).

So the full history is: MIT (origin) to BSD-3-Clause (10 January 2025) to Open WebUI Licence, which is BSD-3-Clause plus the branding clause (v0.6.6, 19 April 2025). Code at or below v0.6.5 remains under plain BSD-3-Clause, which matters if you are pinned to an older version.

Precision matters here, so this is the operative text, quoted from the official LICENSE file. The clause prohibits "altering, removing, obscuring, or replacing any 'Open WebUI' branding, including but not limited to the name, logo, or any visual, textual, or symbolic identifiers that distinguish the software and its interfaces, in any deployment or distribution," except in three circumstances (Source):

• (i) The small-deployment exemption: deployments where "the total number of end users (defined as individual natural persons with direct access to the application) does not exceed fifty (50) within any rolling thirty (30) day period."
• (ii) Written permission: the licensee "has obtained specific prior written permission from the copyright holder."
• (iii) An enterprise licence: the licensee "has obtained a duly executed enterprise license expressly permitting such modification."

The base of the licence remains standard BSD-3-Clause - the copyright notice reads "Copyright (c) 2023- Open WebUI Inc. [Created by Timothy Jaeryang Baek]," and it keeps the three standard BSD conditions and the "AS IS" disclaimer, then adds the branding clause as a fourth, material condition (Source).

The single most important takeaway: running Open WebUI is free at any scale. The only thing the clause restricts is removing or replacing the branding, and only once you pass the 50-user threshold without an exemption.

It is worth being very concrete about what does and does not trigger the enterprise-licence requirement, because the answer is narrower than many assume.

So the trigger is the combination of two conditions: (1) more than 50 end users in a rolling 30-day window, and (2) altering, removing, obscuring, or replacing the Open WebUI branding. Hit only one and you are fine. The clause is, by the project's own account, aimed at a specific behaviour: entities "stripping out all signs of our branding" and then "market[ing] these rebranded solutions in commercial offerings to customers and organizations" while leaning on the original developers for support without contributing back (Source). The team's framing is that it "chose to protect just the branding, to keep the project honest and sustainable; the code itself remains as open as you'd expect."

One practical nuance: "end users" is defined as "individual natural persons with direct access to the application." That is a usage measure, not a licensing seat count, and the window is rolling rather than calendar-based, so a deployment that briefly spikes above 50 users is, on a plain reading, within scope of the threshold. If your situation is close to the line, read the clause yourself and, where the stakes are material, take your own legal advice - this article is informational, not legal counsel.

The enterprise licence is not only a way to legally remove the branding - it is positioned as a broader commercial package. According to Open WebUI's enterprise documentation, it includes (Source):

• White-labelling: "white-label the interface to match your brand identity" - the sanctioned path to remove or replace the branding above the threshold.
• Custom theming and UX: deeper customisation of the interface and workflows.
• Dedicated support and SLAs: a support track structured to the organisation.
• Deployment options: on-premise and air-gapped deployment, with full data-pipeline control.
• High availability: multi-node HA configurations.
• Model integration: connecting proprietary, third-party, or local models.
• Compliance support: assistance with SOC 2, HIPAA, GDPR, FedRAMP, and ISO 27001.

To obtain it, organisations contact Open WebUI's sales team (the docs direct enquiries to sales@openwebui.com) (Source). Pricing is not published; it is a sales-led commercial arrangement. Note that some of these benefits - particularly compliance support and dedicated SLAs - are gated behind the enterprise licence rather than included in the free community build, which is a relevant point when you compare total cost across options.

If your organisation runs or is evaluating Open WebUI at scale, you have three honest paths. Each is legitimate; the right one depends on your priorities.

Option 1: Comply with the community licence (keep the branding)

The simplest path. Run Open WebUI unmodified at whatever scale you need, keeping the Open WebUI branding intact, and pay nothing. This is fully permitted and, for many internal deployments where branding is irrelevant, entirely sufficient. The cost is purely cosmetic - your users see Open WebUI branding - and you still self-manage everything (patching, security, scaling) since the community build has no support SLA.

Option 2: Buy the enterprise licence

If you need your own branding above 50 users, or you want the bundled white-labelling, SLAs, HA, and compliance support, the enterprise licence is the sanctioned route. This makes sense for organisations committed to Open WebUI as their interface and willing to enter a commercial relationship for the brand and support guarantees. The trade-off is cost (sales-led, unpublished) and that you are now in a paid relationship - which changes the "free open source" calculus that may have driven the original choice.

Option 3: Move to an alternative

If licence freedom is a priority - for example, you specifically want to white-label at scale without a commercial conversation, or you prefer a strictly OSI-approved licence - an MIT-licensed alternative avoids the branding constraint entirely. AnythingLLM and LibreChat are both MIT-licensed and impose no branding restriction (compare them in AnythingLLM vs LibreChat and AnythingLLM vs Open WebUI). The trade-off is migration effort and that you may give up specific Open WebUI features you rely on. Be honest with yourself about which features are genuinely load-bearing versus nice-to-have before switching.

There is a more important point that the licence debate tends to obscure, and it applies to every option above: none of these tools, in their free build, is an AI governance platform. Whether you keep Open WebUI's branding, buy its enterprise licence, or switch to an MIT-licensed alternative, the open-source interface still does not ship real-time DLP, immutable auditor-grade audit logs, a runtime data-flow policy engine, pre-built compliance evidence, or shadow AI detection. Open WebUI's enterprise licence advertises compliance support, but that is assistance, not a built-in DLP-and-policy engine.

For a regulated organisation, the licence question and the governance question are separate, and the governance question is usually the bigger one. If you are choosing an AI interface and you carry SOC 2, HIPAA, GDPR, or EU AI Act obligations, solving the branding licence does not solve the audit, DLP, and policy requirements your assessors will examine - those remain a layer you build or buy. We cover the realistic cost of building that layer in our DIY open-source comparison.

In the interest of full transparency: Areebi is a governed enterprise platform built on the MIT-licensed AnythingLLM project, and we contribute back to it. We chose AnythingLLM partly for exactly the licence freedom discussed here - MIT lets us build a branded, governed product without the constraints of Open WebUI's modified licence - and partly because the workspace model fits enterprise segmentation. Areebi adds the governance layer (DLP, immutable audit, policy engine, enforced SSO/SAML/MFA, compliance templates, shadow AI blocking, a hardened build, and a support SLA) that no open-source interface ships. If your interest in the Open WebUI licence is ultimately about deploying governed AI in a regulated environment, see the Areebi platform and private LLM deployment options. If it is purely about branding for an internal tool, Option 1 or 2 above may be all you need.

The Open WebUI licence change is narrower and more reasonable than the "Open WebUI is no longer open source" headlines suggest. You can still run it free at any scale; the only restriction is removing the Open WebUI branding once you pass 50 end users in a rolling 30-day period, unless you have written permission or an enterprise licence. The enterprise licence bundles white-labelling, support SLAs, HA, and compliance assistance for organisations that want them.

Your three options are clear: comply by keeping the branding (free), buy the enterprise licence (your branding plus support), or move to an MIT-licensed alternative if licence freedom is paramount. But whichever you choose, remember the separate and usually larger question: an open-source interface is not a governance platform. If you operate in a regulated environment, the licence is a footnote next to the DLP, audit, and policy controls you will need either way - which is exactly the gap a governed platform built on an open foundation is designed to close.

Further reading: AnythingLLM vs Open WebUI for the feature and licence comparison, the AnythingLLM enterprise guide for the MIT-licensed alternative, and LibreChat for business for another MIT-licensed option.