Open WebUI or an AI platform: when is the interface enough?
Open WebUI is enough when a team with its own experience in servers and security runs AI for a manageable group, for example in research or for a trial. If AI is to run across the whole organisation with sensitive data, tasks arise that the interface does not take on: running models, security updates, connecting specialist systems with each person's permissions, evidence and support. A ready-made platform is then often the alternative.
What is Open WebUI, and what does it include?
Open WebUI is a web interface for AI models that an organisation installs itself. It connects to models running locally or to providers that offer an OpenAI-compatible interface. According to the documentation, the features available without licence costs include sign-in via OIDC and LDAP, roles and groups, models restricted to certain groups, search in uploaded documents, web search and extensions. The publisher is Open WebUI, Inc. in San Francisco. New versions are released in quick succession.
That is a lot for free software. The objection “We will use Open WebUI and save the licence” is therefore justified and deserves an honest look.
Where is Open WebUI enough?
| Use | Open WebUI is usually enough | It gets tight |
|---|---|---|
| Trial with one department | yes, for a few weeks | when the trial quietly becomes permanent operation |
| Research group with its own team | yes, if the team looks after servers and security itself | when patient data or personnel data are to go in |
| AI for the whole organisation | possible with your own operations team | when specialist systems are to be connected with each person’s permissions |
| Sensitive data (patients, citizens, social data) | possible with your own evidence | when data protection and the staff council ask for documents nobody writes |
The yardstick is not the interface but who carries the rest.
What must an organisation organise itself alongside the interface?
- Running models: servers with GPUs, software that runs the model, choosing the model and testing new models.
- Security updates: vulnerabilities in Open WebUI have repeatedly been published and fixed. Whoever runs it follows the advisories and applies updates without delay, as well as for the model software, database and operating system. More on this in the guide Security updates for a self-built AI stack.
- Connection: connections to document repositories, email and specialist applications in which each person sees only what they are allowed to see in the target system.
- Logs and evidence: data protection impact assessment, record of processing activities, a description of permissions and logs for the staff council or works council.
- Support and cover: who helps when something goes wrong, and who takes over during holidays? See bus factor.
Which questions settle the decision?
- How many people are to use the AI, and with which data?
- Is there a team that looks after servers, models and security updates permanently, with cover?
- Which systems are to be connected, and who builds and maintains these connections?
- Which evidence do data protection, information security and staff representatives require?
- Should the AI appear under your own name? Then, with Open WebUI, the Enterprise licence applies from 50 people in 30 days.
If the answers to 2 and 3 are “yes, we have that”, Open WebUI is a viable choice. The guide TCO comparison: run AI yourself or buy a platform? works through the costs of both routes.
What does Open WebUI itself offer businesses?
Open WebUI sells an Enterprise licence for organisations. According to the documentation, it allows your own brand and white label and includes support by agreement; Open WebUI quotes prices only on request. Operation, model and evidence remain the responsibility of the organisation or a service provider even with this licence.
How does this work with basebox?
basebox is a ready-made AI platform with licence, support and updates, in our cloud or on a server in your own organisation. Permissions come from your directory service, connectors use the person’s own access, and the audit log records who did what and when. The DPA, TOMs and the agreement under § 203 StGB (German Criminal Code, professional secrecy) are on /sicherheit. You can keep using existing hardware. The comparison with all features is at basebox and Open WebUI compared.
Note: Information on Open WebUI according to the project’s documentation, as of 11 October 2026. Features and licence may change with new versions.
Frequently asked questions
Is Open WebUI free of charge?
For use within your own organisation with the name and logo unchanged, yes. Anyone who wants to use Open WebUI under their own name and serves more than 50 people in 30 days needs an Enterprise licence; Open WebUI quotes its price on request.
Can Open WebUI serve as a trial and be replaced later?
Yes, it is commonly used as a trial. Plan the switch from the start: which knowledge collections, instructions and settings can be carried over, and who maintains the trial while it runs?
Does basebox run on the same hardware as our Open WebUI?
If you have a server with GPUs, basebox runs on it, provided it has enough capacity for your number of people. We check beforehand, free of charge, whether the hardware is sufficient.
Sources
This article was created with the help of AI, based on the sources listed. Responsible for the content: basebox GmbH. Not legal advice, no liability. Research as of 11 October 2026.