Which license fits your rollout: Open WebUI vs LibreChat license terms
If you are deciding whether a staff chat rollout or a customer-facing deployment triggers the Open WebUI branding clause, the short answer is this: since v0.6.6 (April 19, 2025), Open WebUI code is under the Open WebUI License, which forbids altering or removing Open WebUI branding once a deployment exceeds 50 users in any rolling 30-day period, unless you hold an enterprise license or the copyright holder grants written permission. LibreChat is MIT licensed, so its license imposes no comparable branding condition. Whether the clause reaches you depends on three things: your active user count in a rolling 30-day window, whether you intend to change or remove branding, and whether the deployment is internal or facing customers. Have counsel read the license text against your own facts before you commit.
Start by counting. Pull the active user count for a rolling 30-day window from your identity provider or Open WebUI's admin data, not from licensed seat totals, and confirm with counsel how the 50-user threshold applies to contractors, partners and customers who log in through a shared portal. If you plan to keep Open WebUI branding untouched, the threshold matters less. If you plan to white-label the interface for customers, the clause applies at any user count that exceeds the limit, and the route is an enterprise license or written permission. Ask Open WebUI's enterprise sales team how a quote is built from an expected seat count, since pricing is not published.
Confirm the license facts from primary sources, not from summaries. Read the Open WebUI License documentation and the LICENSE file in the repository, and record which version you will deploy. Code through v0.6.5 remains BSD-3-Clause, so a version pinning decision also changes the license terms. Check LibreChat's license in its repository and note that ClickHouse's acquisition announcement says existing deployments continue unchanged, which you should verify against the current license file and your own counsel's view of ownership changes.
How each license treats branding, users and enterprise terms
This table compares how the Open WebUI License and LibreChat's MIT license treat branding, user counts, rebranding, enterprise terms and ownership. Read the Open WebUI column against your expected end-user count and whether those users are staff or customers. The main takeaway is that the branding clause and its 50-user threshold decide Open WebUI's terms, while LibreChat's MIT license carries no user threshold.
| Term | Open WebUI | LibreChat |
|---|---|---|
| License identity | Open WebUI License from v0.6.6 (April 19, 2025). Code through v0.6.5 remains BSD-3-Clause. | MIT License across the repository. |
| Latest release status | v0.12.3, published October 16, 2026, distributed under the Open WebUI License. | Latest tagged release v0.8.8 (October 1, 2026) is marked pre-release. Confirm a stable tag before production. |
| Branding rule | Altering or removing Open WebUI branding is restricted by the branding clause in the LICENSE file. | MIT keeps the copyright and license notice with copies. Confirm any project trademark or branding terms with the maintainers. |
| User threshold | Branding clause applies above 50 end users in any rolling 30-day period. | No user threshold in the MIT license. |
| Rebranding permission | Allowed at 50 or fewer users in 30 days, with written permission from the copyright holder, or with an enterprise license. | Permitted under MIT terms. Confirm trademark use separately. |
| Internal versus customer-facing use | The threshold counts end users, so customer-facing deployments reach it sooner. Count users per the license definition. | MIT draws no internal versus customer distinction. |
| Enterprise license path | Enterprise licenses allow white-labeling and custom branding. Pricing is quoted after contacting sales with an expected seat count. | No license tier is needed for the MIT code. Ask whether any paid offering carries separate terms. |
| Ownership change | No ownership change is reported in the supplied sources. Confirm the current copyright holder named in the LICENSE file before procurement review. | ClickHouse announced on November 4, 2025 that it acquired LibreChat and that existing deployments continue unchanged. |
What the Open WebUI branding clause actually restricts
The Open WebUI License does not restrict whether you can run Open WebUI. It restricts altering or removing Open WebUI branding, meaning the names, logos and visible attribution the project ships in its interface. Changing the logo, swapping in your company name across the login screen and navigation, or stripping the attribution are the actions the clause covers. Installing the software, using it internally, connecting it to your models and modifying its code for your own purposes are a separate question. Read the Open WebUI License documentation and the LICENSE file together before you decide how far your rebranding plans go.
The threshold is where internal rollouts most often trip the clause. The branding restriction applies to deployments with more than 50 users in any rolling 30-day period, so a pilot of 40 staff can be rebranded freely while a company-wide rollout of several hundred people cannot, unless one of the exceptions applies. Count active end users, not licensed seats or accounts created, and confirm with your deployment's own user metrics how the count is measured over a rolling window. A team that starts small and expands later should plan the rebranding decision before the rollout grows past the threshold, not after staff have already seen the unbranded interface.
There are three ways to lift the restriction: keep the deployment at no more than 50 end users in a rolling 30-day period, obtain written permission from the copyright holder, or hold an enterprise license. Each route has a different cost and a different paper trail, so ask your legal and procurement teams to confirm which applies to your plans. Interpretation of the clause, including how "end user" and "altering branding" apply to your specific setup, should be confirmed with counsel rather than settled by this summary. DeployOpen can help you document the deployment's user counts and configuration, but it does not give legal opinions on license terms.
How internal, customer-facing and rebranded use change the license result
Internal use by a single staff group is the simplest case. The Open WebUI branding clause applies only to deployments that exceed 50 end users in any rolling 30-day period, so a group below that count can keep the interface branding as shipped and can change branding without needing an enterprise license. The count reflects active end users in each window, so a pilot that grows quietly can cross the line. Illustrative example: a 35-person legal team using one instance stays under the threshold in every 30-day window, while the same instance serving 120 active users in one month does not.
- Count active end users: Track sign-ins for each rolling 30-day window, since a pilot can cross the threshold without anyone noticing.
- Keep branding intact: Below the threshold the clause does not restrict branding changes, but leaving logos and names in place avoids later disputes and costs nothing.
- LibreChat terms: The MIT license has no user-count threshold, so the same 35 users raise no threshold question, though you still keep the copyright and license notice that the MIT text requires.
- Keep dated usage records: Export usage data for each deployment so you can show the figures to counsel or an auditor.
Confirm with counsel how the Open WebUI License defines an end user, and whether service accounts, API integrations or automation identities count toward the total.
Customer-facing deployments count external users toward the same threshold. Staff and customer access add to one end-user figure, so a support portal that serves clients alongside an internal team can reach 50 faster than either group alone. Illustrative example: 30 staff members and 25 customers active in the same rolling 30-day window total 55 end users, which is above the threshold even though neither group is large on its own.
- Combined count: Staff and customer accounts inside one instance add together under the branding clause.
- Customer-visible branding: Once the count exceeds 50, changing or removing Open WebUI branding in the customer view requires one of the permitted routes.
- Several deployments: Ask counsel how the end-user count applies when one organization runs more than one deployment, because splitting users across instances does not settle the question on its own.
- LibreChat customer use: The MIT license places no user-count condition on commercial use, but you still need to keep its notices and confirm any customer-facing terms you add to your agreement.
Confirm the expected external user count per month with the business owner before launch, and recount each quarter as the customer base changes.
Rebranding a chat product for resale or for a customer's own brand is the case the branding clause targets most directly. Above 50 end users, altering or removing Open WebUI branding requires an enterprise license, written permission from the copyright holder, or a deployment that stays under the threshold. The Open WebUI License documentation sets out these conditions, and the enterprise route is the one the vendor describes for white-labeling and custom branding. Pricing is not published, so the figure comes from a written quote.
- Enterprise license: The vendor describes white-labeling and custom branding with dedicated support as enterprise features. Request the scope, the basis of the seat count and the term in writing.
- Written permission: Permission from the copyright holder is a separate route. Get it in writing and name the exact branding elements it covers.
- Resale terms: The license does not answer every question about reselling a hosted service, so ask counsel whether your customer contract needs its own terms.
- LibreChat rebranding: The MIT license permits modification, but confirm which notices and attribution it requires you to keep before you rename a LibreChat-based product.
Ask the Open WebUI vendor for the enterprise license terms in writing before you commit to a customer-visible brand.
Several internal departments sharing one instance is still internal use, but for license purposes every person who signs in as an end user counts. Teams add to the same count, so four departments of 15 users each (illustrative) reach 60 end users in a 30-day window and cross the threshold. Crossing the threshold changes the branding terms only, so departments may keep using the software while the rollout team decides how to handle the license.
- Shared count: Departments in one deployment share one total, so plan the threshold across the whole organization rather than team by team.
- Per-team deployments: Separate instances per team may still need a combined count, so confirm with counsel before assuming each team is independent.
- Enterprise license scope: Ask whether an enterprise license covers all departments and how the quoted price relates to the expected seat count.
- LibreChat ownership change: ClickHouse said in its announcement that existing LibreChat deployments continue unchanged, but confirm the license text of any release you plan to adopt.
Set an alert below 50 end users so the rollout team can decide before a rolling window crosses the threshold, and confirm how the definition applies to contractors and service accounts.
Factors that change the license outcome in practice
Open WebUI's branding clause turns on a few operational facts: how many people actually use the deployment, whether customers see the interface, and which release you run. LibreChat's MIT license has no equivalent trigger, so the questions below matter mainly for the Open WebUI side of the decision.
Active end users in 30 days
The branding restriction applies only above 50 end users in any rolling 30-day period. Count distinct people who log in or use the front end over that window, not seats purchased or accounts created. A deployment that sits just under the threshold can cross it during a seasonal peak or a pilot expansion. Ask your team to track active users per rolling window from day one, and confirm how your identity provider groups accounts before you rely on the count.
Branding visible to customers
The clause is about altering or removing Open WebUI branding, so the question is whether the interface your users see is the one your customers see. Internal staff tools generally sit in a different position from a portal that clients, patients or citizens log into. If an external audience can reach the front end, review the license text with counsel before you change any logo, name or footer.
Rebranding goals
Decide whether you need to change the logo, product name, color scheme or footer. Light theming that keeps the Open WebUI identity may be treated differently from removing it. Once the goal is written down, you can test it against the license. If the answer is full white-labeling, the enterprise license is the path the license itself names, and that cost has to be quoted separately from the free deployment.
Contributor permission status
The branding clause lets the copyright holder grant written permission as an alternative to an enterprise license. That permission is a named, documented agreement, not a verbal assurance from a community member. If you plan to rely on it, ask the copyright holder for written terms covering your deployment, your user count and the branding changes you intend. Keep that letter with your license records.
Deployed release version
The Open WebUI License applies from v0.6.6, released April 19, 2025. Code through v0.6.5 stays BSD-3-Clause, so the release tag in your running container decides which terms apply to that copy. Check the image tag in your deployment manifests, including any staging or disaster recovery environments. Upgrades that cross v0.6.6 change the terms you operate under, so record the version and the date you adopted it.
Whether to fork from v0.6.5
Some teams consider staying on BSD-3-Clause code through v0.6.5 and maintaining it themselves. That path avoids the branding clause, but it means you own security patches, dependency updates and compatibility with newer features. Ask a security engineer to estimate the patch workload for the release line you would carry, and ask counsel to confirm that the BSD-3-Clause terms cover your intended use. Compare that ongoing work against the license fee and the cost of moving to LibreChat.
What MIT licensing and ClickHouse ownership mean for LibreChat
LibreChat is licensed under the MIT license, which permits use, modification, redistribution and rebranding, including for customer-facing deployments, with only the license notice to keep. The supplied facts do not describe a branding clause or user threshold for LibreChat, so the practical question for your team is whether the current LICENSE file in the LibreChat repository contains any such terms. Check it on the tag you plan to deploy, not only on the main branch, and have counsel confirm that nothing in the UI or bundled assets adds a restriction the license file does not state.
ClickHouse announced on November 4, 2025 that it had acquired LibreChat and said existing LibreChat deployments continue unchanged, with ongoing investment in the open-source project, according to the ClickHouse announcement. An acquisition does not change the license of code already published under MIT, but it can change the roadmap, the maintainers and whether commercial add-ons appear later. Ask ClickHouse directly whether any hosted, enterprise or support offerings exist, what they include, and whether they would ever be licensed differently from the open-source core. Record the answers in your architecture file so the decision is traceable.
The latest tagged release on GitHub is v0.8.8, published on October 1, 2026 and marked as a pre-release after release candidates in September 2026. For a company-wide rollout, plan to pin a specific tag, test upgrades in staging and confirm which release line your security team has reviewed. Treat a pre-release as a version to validate, not as a stable baseline, and confirm with the maintainers which tag they recommend for production.
How to confirm license fit in your own environment
This sequence turns the license question into written evidence: a measured user count, a record of where Open WebUI branding appears, a documented rebranding decision, confirmed enterprise terms and a counsel review before you commit to either platform.
Count distinct end users per rolling window
Pull login and session records from your identity provider or Open WebUI's own user list, then count distinct end users active in any rolling 30-day period. Include contractors and service accounts that a person uses interactively. Count users, not seats purchased or groups assigned. The output is a dated table showing the highest distinct-user count observed, which tells you whether the 50-user threshold in the Open WebUI License applies to your deployment at all. Confirm the method against the Open WebUI License documentation before you rely on the number.
Document every place Open WebUI branding appears
Walk through the deployed instance, its login page, emails, exported files, footers, favicon, API responses and any internal portal that embeds it, and record each location where Open WebUI names or logos appear. Compare the instance against the LICENSE file in the open-webui repository so you read the branding clause in its own words. The output is a screenshot-backed inventory with a location, a file or setting name and an owner for each item.
Decide whether rebranding is needed
Using the user count and the branding inventory, decide with the product owner and communications lead whether you intend to alter or remove any Open WebUI branding. If you do not, the branding clause does not change your plan. If you do, you need one of the routes the license names: a deployment within the threshold, written permission from the copyright holder, or an enterprise license. Record the decision and its reason in your architecture or license register, dated and signed by the accountable owner.
Request enterprise license terms in writing
If rebranding or white-labeling is required above the threshold, ask Open WebUI for enterprise license terms in writing. Provide the expected seat count, the branding changes you want, the support model and the term you need. Pricing is not published and is quoted after contacting enterprise sales, so the quote should state what is licensed, what is excluded and what recurs. The output is a signed or accepted written quote with the license scope that your counsel can review.
Check LibreChat's license file and pinned version
For the LibreChat side, open the LICENSE file in the LibreChat repository at the exact tag you plan to deploy, not the main branch, and confirm the MIT terms apply to that version. Record the tag, the commit hash and the release status. The latest tagged release on GitHub is a pre-release, so decide whether your pinned version is acceptable for production and document that choice. Also note that ClickHouse acquired LibreChat and stated that existing deployments continue unchanged, and confirm any changes to licensing or hosted offerings with the project before you rely on them.
Confirm licensing for every bundled and added component
List every component your deployment pulls in, including the database, search service, RAG service, vector store and any model connector, and check each component's license separately. Chat front ends often ship with supporting services under different terms, so the license review must cover the full stack. The output is a component license table tied to the exact versions you will deploy.
Have counsel review the evidence package
Give counsel the user count method and results, the branding inventory, the rebranding decision, the written enterprise terms if any, the pinned LibreChat license record and the component table. Ask counsel to confirm how the Open WebUI License applies to your facts, whether any written permission is needed from the copyright holder and whether your internal and customer-facing uses fall within the terms. Counsel's written sign-off is the closing record. DeployOpen can help prepare the evidence package, but it does not provide legal advice.
When an Open WebUI enterprise license is worth requesting
Request an Open WebUI enterprise license when the branding clause is the real constraint. Above 50 users in any rolling 30-day period, the Open WebUI License forbids altering or removing Open WebUI branding unless you hold an enterprise license or the copyright holder gives written permission. If your staff-facing portal must carry your own name and logo, or customers will see the interface, white-labeling is the feature that matters, and the enterprise license is the documented route to it. Internal use above 50 users with the default branding does not, on its own, require that license. Confirm your user count method against the 30-day window before deciding, and check whether the rebranding you want is covered by the permission you would receive. Pricing is not published. Open WebUI's Enterprise documentation says a quote follows from contacting enterprise sales with an expected seat count, so the seat estimate you give will shape the number. Ask the vendor to itemize seat count and how seats are counted, what support scope is included (response channels, hours and whether upgrades are covered), the term length, the renewal mechanics and any price change at renewal, and whether the license is perpetual or tied to a subscription period. These are recurring costs, and they grow with headcount, so model a growth scenario alongside the current one. Confirm all terms in writing; DeployOpen does not set vendor license prices. The alternative is to stay on code through v0.6.5, which remains BSD-3-Clause, and maintain your own fork. That avoids the branding clause but freezes you on pre-v0.6.6 code, so security fixes and features from later releases, such as v0.12.3, must be ported or re-applied by your team. Budget for that engineering time, for merge conflicts on every upgrade, and for the security patching you would own. A fork makes sense for a small, capable platform team with a narrow feature need. For most organizations, comparing the recurring license quote with the ongoing cost of carrying a fork is the decision to document.
Common license questions before a rollout
Does internal staff use trigger the Open WebUI branding clause?
Yes, it can. The Open WebUI License threshold counts end users in any rolling 30-day period, so employees who sign in to the deployment count toward it. At or below 50 end users in that window, you can alter or remove Open WebUI branding. Above 50, you need an enterprise license or written permission from the copyright holder before changing the branding. Because the count includes every user, a company-wide rollout crosses the threshold quickly. Track the number of distinct users per 30-day window from the start, and have your legal team confirm how the license defines an end user before you finalize the rollout plan. The Open WebUI License documentation is the starting point for that review.
What does an Open WebUI enterprise license cost and who quotes it?
Open WebUI does not publish enterprise pricing. You contact its enterprise sales team with an expected seat count, and they quote from that input. The enterprise license allows white-labeling and custom branding and comes with dedicated support options. The main cost drivers are the seat count, the support level you choose and the contract term. Before you accept a quote, ask what the license covers in writing: which branding changes are allowed, which versions and upgrades are included, what the support levels contain, how renewals and seat increases are priced, and whether the license changes if your user count drops. Ask for these terms in the same document as the price, so you can compare the quote with a LibreChat rollout that has no equivalent branding fee under its MIT license.
Can we rebrand LibreChat freely under its license?
LibreChat is MIT licensed, and the MIT license permits modification, redistribution and use, provided the copyright notice and license text are kept with the software. The supplied license facts do not include a branding-protection clause for LibreChat like the one in the Open WebUI License, so you do not face a user-count threshold for changing the interface. Still, confirm the details before you publish a rebranded build. Check the repository for any separately licensed assets, review your own trademark position if you use the LibreChat name, and ask your legal team to confirm how the notice requirement applies to your distribution method. Keep a record of the upstream version you forked and the changes you made, because that record will matter at each upgrade.
Does ClickHouse ownership change LibreChat's license?
The license facts do not show a change. ClickHouse announced on November 4, 2025 that it had acquired LibreChat and said existing LibreChat deployments continue unchanged, with ongoing investment in the open-source project. The repository remains MIT licensed, and the latest tagged release, v0.8.8, was published on October 1, 2026 and marked as a pre-release. An acquisition does not rewrite the license of code already released under MIT, but future versions could change direction, so the risk is about the roadmap rather than the current terms. Pin the version you deploy, read the LICENSE file and release notes before each upgrade, and ask ClickHouse for written statements on licensing and project governance if your review board needs them. The ClickHouse announcement is the primary source to cite.
Can we run Open WebUI and LibreChat side by side?
Yes. They are separate applications with separate data stores, so you can run both on the same platform. Each one needs its own services: LibreChat's reference Docker Compose file runs the app with MongoDB, Meilisearch for search and a separate RAG API service. Open WebUI with multiple replicas needs PostgreSQL, Redis and shared file storage. Running both doubles the work in several areas: two identity configurations, two sets of user records, two license reviews and two upgrade cycles. Each platform also counts users separately, so a shared employee base may cross the Open WebUI threshold while LibreChat faces no equivalent limit. Most teams that run both use one as the default for staff and the other for a specific group, and they document which group uses which tool before rollout.
How much effort does license compliance take for a chat platform?
The effort is mostly recurring governance rather than a one-time task. For Open WebUI, the main work is counting distinct end users in every rolling 30-day window, recording any enterprise license or written permission, keeping the branding intact where required and reviewing the LICENSE file at each upgrade. The count gets harder as the user base grows, so the effort rises with headcount. For LibreChat, the MIT license needs less ongoing tracking, but you still keep the notice in every distribution, review the license when the project changes hands or changes release policy, and document your own modifications. Ask your internal team to estimate the hours for each control, since no supplied figure covers this. Assign an owner for the license register and agree on a review step in the upgrade process before go-live.
Can DeployOpen handle the license work for us?
DeployOpen can take on the technical work that supports license compliance, but it cannot give you a legal opinion or issue compliance certifications. DeployOpen plans, implements, customizes, integrates, documents and supports self-hosted open-source platforms inside your own infrastructure. For this comparison, that could include deploying the chosen platform, configuring identity and access controls, documenting the deployment and setting up reporting that supports your user-count records. Most engagements are fixed-scope, with scope, deliverables and timelines agreed in writing before work starts, and DeployOpen does not publish a price list, so a quote follows from that written scope. Your legal counsel should own the license interpretation, and independent auditors own any attestations. Ask DeployOpen to state in the scope which compliance tasks it covers and which remain with your team.
How DeployOpen helps you choose and deploy within license terms
DeployOpen plans, implements, customizes, integrates, hardens, documents and supports self-hosted open-source platforms inside your own cloud accounts, data centers or air-gapped networks. For Open WebUI vs LibreChat license, we start by confirming how your users, branding and deployment model fit each license, then build and document the deployment to match the terms you choose.
How we scope
- We confirm your expected end-user count and how it is measured over any rolling 30-day period.
- We record whether staff will see a rebranded interface and who holds the written permission or license that covers it.
- Engagements are fixed-scope, with deliverables and timelines agreed in writing before any work starts.
How we build
- We deploy the chosen platform in your infrastructure, with its model providers and identity integration configured to your policy.
- We test branding, licensing-relevant settings and access controls against the scope agreed for your rollout.
- We document the license position, configuration and evidence so your legal and compliance reviewers can check it.
How we hand over
- You receive written documentation of the deployment, its configuration and the license conditions it was built against.
- We walk your operators through upgrade, backup and restore steps for the version you run.
- We confirm with you, in writing, what remains your responsibility, such as license decisions and vendor contract terms.
How we support
- Ongoing support, upgrades and continuous testing are available as retainers when you want them.
- We can review license-relevant changes when you move to a new release, so your position stays current.
- Before any change that affects branding or user counts, we agree the scope and effect in writing first.
