Giving a team AI looks easy.
You pay for a subscription for everyone and you're done.
Until you ask yourself where the documents they upload end up.
What it is
Open WebUI is an open-source web application that looks a lot like the commercial AI chats, except you install it yourself: on a server, on an office computer, wherever you like.
You connect it to local models (for example via Ollama) or to any compatible API, and your team gets a chat window with history, document uploads, search over those documents, users and permissions.
The interface is the same for everyone. What sits behind it is up to you.
Why I find it interesting
Because of a very simple idea: separating the window from the engine.
When you use a commercial chat, the window and the model come together. If you want to switch models, you switch tools, accounts and habits.
With Open WebUI the window stays and the engine changes. A local model today for sensitive work, a cloud one tomorrow for complex tasks. The team doesn't have to learn anything new.
When the tool and the provider are the same thing, switching providers costs you the tool.
It's a way of thinking I apply to almost everything: don't tie your team's daily work to one specific provider, because providers change prices, terms and sometimes disappear.
Who it makes sense for
- Teams handling sensitive information: contracts, client data, internal documentation.
- Companies that want to try several models without signing up for ten accounts.
- Anyone who wants an internal assistant that answers questions about their own documents.
Who it doesn't: if you're one person and a commercial chat is enough, running a server may be overkill. And if you install it, someone has to maintain it. Updates, backups and access. It doesn't look after itself.
A practical note: before using it for anything commercial, read its licence. It has its own conditions, especially if you wanted to offer it to others under your brand.
What this repository teaches
That the value is often in the layer nobody wants to build. Models are the spectacular part. But what makes a team actually use them is the boring stuff: users, permissions, history and an interface that doesn't scare people off.
It's the least visible part, and the one people appreciate most.
P.S. The question I'd ask any AI tool before giving it to a team isn't "how smart is it?". It's "what happens the day we want to stop using it?".