Open WebUI Enterprise License: Branding Terms, Pricing and What It Adds (2026)

An Open WebUI enterprise license is a paid agreement with Open WebUI Inc. that lets you remove or replace the Open WebUI branding and run enterprise-only components such as Terminals in production. You do not need one to deploy Open WebUI internally for any number of users if the branding stays intact. Open WebUI publishes no price; its sales form asks how many end users you expect.

Open WebUI changed its licence twice in 2025. The second change added the clause that procurement teams now ask about: once a deployment passes 50 users, the Open WebUI name and logo have to stay unless you hold a licence or written permission. This guide is built from the LICENSE file and its Git history, the release notes, and Open WebUI’s licence, enterprise and identity documentation, all checked on 14 October 2026. It is general information, not legal advice, so have counsel read the licence in the release you actually deploy.

If you are still choosing a chat interface, our side-by-side review of Open WebUI, LibreChat and AnythingLLM compares features, sign-in and logging. Whether to assemble a chat stack at all is a separate decision, covered in our guide to the routes to an internal ChatGPT.

What the Open WebUI license says

The current licence is called the Open WebUI License. Its first three clauses are the familiar BSD-3-Clause conditions: keep the copyright notice in source and binary redistributions, and do not use the project’s or its contributors’ names to endorse your product. Clause 4 is the addition, and the licence makes it a material condition of the whole grant.

Clause 4 prohibits altering, removing, obscuring or replacing the Open WebUI branding in any deployment or distribution. Branding covers the name, the logo and any other visual, textual or symbolic identifier of the software and its interfaces. Three exceptions apply:

1. Small deployments. No more than 50 end users in any rolling 30-day period. The licence defines end users as “individual natural persons with direct access to the application”.
2. Written permission. Specific prior written permission from the copyright holder, Open WebUI Inc.
3. Enterprise licence. An executed enterprise agreement whose terms explicitly allow the change.

Any other removal or alteration of the branding is a material breach. The rest of the file is short. Materials under earlier licences keep those terms, as recorded in a LICENSE_HISTORY file; contributions fall under a Contributor License Agreement that lets Open WebUI Inc. relicense and commercialise them; and the usual warranty disclaimer follows.

Two consequences matter for buyers. The clause restricts branding, not usage: nothing in it caps how many people may use an unmodified deployment, and Open WebUI’s licence page says you may even charge for access. And because of the branding condition, that same page states that releases from v0.6.6 onward are not under an OSI-approved open-source licence, which matters if your software policy only admits OSI-approved code.

How the licence changed, and which releases it covers

The branding clause was committed on 18 April 2025, and Open WebUI’s licence page gives 19 April 2025 as its effective date; the first release to carry it, v0.6.6, is dated 5 May 2025 in the changelog. In December 2025 the copyright line moved from Timothy Jaeryang Baek, the project’s creator, to Open WebUI Inc.

A rewording committed on 14 April 2026 and first released in v0.9.0 changed the second exception. It used to cover only official contributors who had a substantive change merged and had also obtained written permission. It now covers any licensee with specific prior written permission. The licence page still describes the older contributor-based exception, so treat the LICENSE file in your release as the authority.

Nothing was relicensed backwards. LICENSE_HISTORY keeps code written before the April 2025 change under BSD-3-Clause and code written before the January 2025 change under MIT. The licence page invites anyone who disagrees with the clause to fork v0.6.5, which has no branding condition. The price of that route is everything released since. The GitHub advisory for CVE-2025-64496, a high-severity code-injection flaw, lists every release up to 0.6.34 as affected, so a v0.6.5 fork would need that fix, and each one after it, backported by hand.

Does your deployment trigger the branding clause?

Work through four questions in order.

1. Are you changing the branding at all? If the Open WebUI name and logo stay where they are, the clause does not apply, whatever your user count. Open WebUI’s licence guidance lists changes it accepts without a licence: a small, visually secondary banner naming your organisation as the operator, an extra legal or contact link in the About dialog, a subordinate footer link to your company, and any backend, monitoring or sign-in integration.
2. What counts as a change? According to that guidance, replacing the logo, recolouring it, renaming the product, moving or shrinking the branding, and keeping only a small credit line while hiding the native branding all count. Putting your logo next to Open WebUI’s at similar prominence is co-branding, which the guidance reserves for enterprise licensees. The software follows the same logic: if you override the WEBUI_NAME setting, Open WebUI appends its own name in brackets.
3. How many end users do you have? Count individual people with direct access over any rolling 30-day window, not concurrent sessions. The group assignment in your identity provider, or the user list in the admin panel, is the practical source. At 50 or fewer you may rebrand. Some cases are not spelled out: service accounts, people who reach Open WebUI only through another application calling its API, and contractors from a partner organisation. Get Open WebUI’s answer on those in writing.
4. Do you redistribute or resell? A public fork or a paid hosted service may keep the branding, provided it states prominently that it is a fork and not the official release; the licence page supplies example wording. Removing the branding for resale or white-labelling needs an enterprise or proprietary licence. Consultancies have their own channel: Open WebUI asks agencies and resellers to apply to its partner programme instead of contacting sales, says companies under five years old are generally not eligible, and lets an agency introduce a client that is ready to buy an enterprise licence.

One narrow exemption remains. Researchers at non-profit or academic institutions may ask permission to remove the branding for a specific, time-limited study, such as a one-semester classroom trial. Ongoing departmental use does not qualify.

What an Open WebUI enterprise license adds

Open WebUI’s enterprise page splits use into two categories. Standard use, meaning internal use with the original branding exactly intact, is free. Enterprise use covers white-labelling, rebranding and other changes to the branding, plus enterprise-exclusive offerings, with Terminals named as the example. In practice the licence buys four things.

• Branding rights. Permission to replace the name, logo and theme, which the licence page describes as fully custom branding.
• Enterprise-only software. Terminals is the orchestrator that gives every Open WebUI user an isolated Open Terminal workspace with separate files, processes, resource limits and a network boundary. Its repository carries the Open WebUI Enterprise License: production use needs a valid licence covering the correct number of user seats, while development and testing do not. Open Terminal itself and oikb, the knowledge-base sync tool, are MIT-licensed. Enterprise builds read a licence key from the LICENSE_KEY environment variable.
• Support. A dedicated account manager, office hours with core engineers, dedicated support channels and scheduled consulting hours. The support page says the relationship is documented and structured with service-level agreements, and also that Open WebUI gives guidance rather than implementation services, so hands-on work stays with your team or an integrator.
• A contract with the vendor. Enterprise licences are sold only to registered organisations, not to individuals.

Clarify one point in writing. When the branding clause arrived, the v0.6.6 release notes listed long-term support versions among the enterprise benefits. The enterprise and support pages checked in October 2026 do not mention a long-term support release line.

Open WebUI enterprise pricing

Open WebUI does not publish a price for its enterprise licence, either in its documentation or on openwebui.com (checked 14 October 2026). The route is a sales form. It asks for a work email address and your expected number of end users, which Open WebUI calls seats, and warns that enquiries from personal email domains will not receive a response.

Two details hint at how a quote is built: the form asks for the end-user count up front, and the Terminals licence ties production use to user seats. Neither is a price, so ask for the full model in writing.

Do not confuse the licence with Open WebUI Computer, a separate product on openwebui.com that puts your own machine’s files, terminal and coding agents behind a browser. It is free to use, offers a Supporter tier at $60 per seat per year, and lists Enterprise at a custom price. None of that is the Open WebUI enterprise licence.

When you budget, the licence is rarely the largest line. Model serving, GPUs, upgrades and the people who operate the service usually cost more. If Open WebUI will sit in front of Ollama for a team, our guide to running Ollama for many users covers the model-server side.

SSO, LDAP, SCIM and RBAC come without a licence

Enterprise identity features are not what the licence sells. The free release already includes them:

• OAuth and OpenID Connect. Google, Microsoft and GitHub are built in; Microsoft sign-in is limited to a single Entra tenant. Any other OIDC provider works through the generic OIDC settings, one provider at a time.
• Trusted-header sign-in behind an authenticating reverse proxy.
• LDAP and Active Directory.
• SCIM 2.0 provisioning of users and groups from identity providers such as Okta, Microsoft Entra ID and Google Workspace.
• Roles and groups. Three system roles (admin, user and pending), groups that can be nested, and permissions that only add up: no group can take away what another grants.
• Audit logging, off by default and switched on with AUDIT_LOG_LEVEL.

Open WebUI documents no AWS-specific sign-in, but Amazon Cognito user pools act as OpenID Connect issuers, so the generic OIDC settings cover them:

ENABLE_OAUTH_SIGNUP=true
OAUTH_PROVIDER_NAME=AWS
OAUTH_CLIENT_ID=<cognito-app-client-id>
OAUTH_CLIENT_SECRET=<cognito-app-client-secret>
OPENID_PROVIDER_URL=https://cognito-idp.<region>.amazonaws.com/<user-pool-id>/.well-known/openid-configuration
OAUTH_SCOPES=openid email profile

1. Register https://<your-open-webui-host>/oauth/oidc/callback as the redirect URI for the Cognito app client.
2. Keep the email claim in the token: Open WebUI requires it, and openid plus email are mandatory scopes.
3. Set ENABLE_OAUTH_SIGNUP so people get an account the first time they sign in; it is off by default.
4. Once sign-in works, ENABLE_LOGIN_FORM=false hides the password form. Configure SSO or LDAP first, otherwise no one will be able to sign in.

Questions to ask Open WebUI’s sales team

1. How is the licence priced: per end user, per deployment or as a flat fee, and is there a minimum term or seat count?
2. How do you count end users: every account, people active in a rolling 30 days, or something else? Do service accounts and API-only consumers count?
3. Which branding changes does the licence permit: logo, product name, colours, login page, emails, the About dialog?
4. Is Terminals included, or priced separately, and for how many seats?
5. What support is included: response times, channels, named contacts, and the service-level terms in the contract?
6. Is there a long-term support release line, and for how long is each version patched?
7. How are security advisories communicated to licensees, and how early?
8. Does one licence cover production, staging, a disaster-recovery copy and air-gapped sites?
9. What happens at renewal or termination: must the original branding return, and how quickly?
10. If an integrator deploys for you, who signs the licence and who is the supported party?

Ask for the answers in the order form or the licence itself, not only in an email thread. This checklist is a starting point for that negotiation and is not legal advice.

How VDF AI fits

Open WebUI is a capable interface when a team wants chat in front of its own models and can run the service itself. Companies tend to look further when an assistant must honour source-system permissions, keep an audit trail for every answer, and govern agents and tools as well as chat.

VDF AI is a self-hosted enterprise AI platform built for that case: chat, governed agents and workflows, and private RAG that carries document permissions over from the source systems, with audit logs, and role-based access control on every plan. On-premises it has native Microsoft Entra ID single sign-on that maps Entra security groups to roles; Okta, Keycloak and other SAML or OIDC providers connect through an SSO-aware reverse proxy.

Sector-specific deployments are covered in our private GPT guides by industry, and replacing a public assistant in our page on a self-hosted assistant for ChatGPT users. If model licences are part of the same review, read our checklist for open-weight model licences. On-premises licences are sold in seat bundles; see current pricing.